Outbound Workers (2)

Last updated Apr 21, 2026 Outbound Workers sit between your customer's Workers and the public Internet. They give you visibility into all outgoing fetch() requests from user Workers.

Outbound Workers diagram information

General Use Cases

Outbound Workers can be used to:

  • Log all subrequests to identify malicious domains or usage patterns.
  • Create, allow, or block lists for hostnames requested by user Workers.
  • Configure authentication to your APIs behind the scenes (without end developers needing to set credentials).

Note

When an Outbound Worker is enabled, your customer's Worker will no longer be able to use the connect() API to create outbound TCP Sockets. This is to ensure all outbound communication goes through the Outbound Worker's fetch method.

Use Outbound Workers

To use Outbound Workers:

  1. Create a Worker intended to serve as your Outbound Worker.
  2. Outbound Worker can be specified as an optional parameter in the dispatch namespaces binding in a project's Wrangler configuration file. Optionally, to pass data from your dynamic dispatch Worker to the Outbound Worker, the variable names can be specified under parameters.

Make sure that you have wrangler@3.3.0 or later installed.

{
    "dispatch_namespaces": [
        {
            "binding": "dispatcher",
            "namespace": "<NAMESPACE_NAME>",
            "outbound": {
                "service": "<SERVICE_NAME>",
                "parameters": [
                    "params_object"
                ]
            }
        }
    ]
}

[[dispatch_namespaces]]
binding = "dispatcher"
namespace = "<NAMESPACE_NAME>"

  [dispatch_namespaces.outbound]
  service = "<SERVICE_NAME>"
  parameters = [ "params_object" ]
  1. Edit your dynamic dispatch Worker to call the Outbound Worker and declare variables to pass on dispatcher.get().
export default {
    async fetch(request, env) {
        try {
            // parse the URL, read the subdomain
            let workerName = new URL(request.url).host.split(".")[0];

            let context_from_dispatcher = {
                customer_name: workerName,
                url: request.url,
            };

            let userWorker = env.dispatcher.get(
                workerName,
                {},
                {
                    // outbound arguments. object name must match parameters in the binding
                    outbound: {
                        params_object: context_from_dispatcher,
                    },
                },
            );
            return await userWorker.fetch(request);
        } catch (e) {
            if (e.message.startsWith("Worker not found")) {
                // we tried to get a worker that doesn't exist in our dispatch namespace
                return new Response("", { status: 404 });
            }
            return new Response(e.message, { status: 500 });
        }
    },
};
  1. The Outbound Worker will now be invoked on any fetch() requests from a user Worker. The user Worker will trigger a FetchEvent on the Outbound Worker. The variables declared in the binding can be accessed in the Outbound Worker through env.<VAR_NAME>.

The following is an example of an Outbound Worker that logs the fetch request from user Worker and creates a JWT if the fetch request matches api.example.com.

export default {
    // this event is fired when the dispatched Workers make a subrequest
    async fetch(request, env, ctx) {
        // env contains the values we set in `dispatcher.get()`
        const customer_name = env.customer_name;
        const original_url = env.url;

        // log the request
        ctx.waitUntil(
            fetch("https://logs.example.com", {
                method: "POST",
                body: JSON.stringify({
                    customer_name,
                    original_url,
                }),
            }),
        );

        const url = new URL(original_url);
        if (url.host === "api.example.com") {
            // pre-auth requests to our API
            const jwt = make_jwt_for_customer(customer_name);

            let headers = new Headers(request.headers);
            headers.set("Authorization", `Bearer ${jwt}`);

            // clone the request to set new headers using existing body
            let new_request = new Request(request, { headers });

            return fetch(new_request);
        }

        return fetch(request);
    },
};

Note

Outbound Workers do not intercept fetch requests made from Durable Objects or mTLS certificate bindings.

Was this helpful?

YesNo

On this page

Outbound Workers (2) - 图2Docs

{"@context":"https://schema.org","@type":"TechArticle","@id":"https://developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/configuration/outbound-workers/#page","headline":"Outbound Workers","description":"Intercept and control outgoing fetch requests from user Workers using Outbound Workers in Workers for Platforms.","url":"https://developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/configuration/outbound-workers/","inLanguage":"en","image":"https://developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/configuration/outbound-workers/og.png?v=8282a664312c90f1","dateModified":"2026-04-21","publisher":{"@type":"Organization","name":"Cloudflare","description":"One platform for your apps, agents, and workforce. Build, secure, and scale without managing infrastructure","url":"https://www.cloudflare.com/","sameAs":["https://github.com/cloudflare","https://www.linkedin.com/company/cloudflare","https://x.com/cloudflare"],"logo":{"@type":"ImageObject","url":"https://developers.cloudflare.com/logo.svg"},"address":{"@type":"PostalAddress","streetAddress":"101 Townsend St","addressLocality":"San Francisco","addressRegion":"CA","postalCode":"94107","addressCountry":"US"},"contactPoint":[{"@type":"ContactPoint","contactType":"Customer Support","url":"https://support.cloudflare.com/","availableLanguage":["English"]},{"@type":"ContactPoint","contactType":"Sales","url":"https://www.cloudflare.com/contact/","availableLanguage":["English"]}]},"isPartOf":{"@type":"WebSite","@id":"https://developers.cloudflare.com/#website","name":"Cloudflare Docs","url":"https://developers.cloudflare.com/"}}

description: Host static assets on Cloudflare's global network and deliver faster load times worldwide with Workers for Platforms. title: Static assets image: https://developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/configuration/static-assets/og.png?v=b813047aea49bf67

Skip to content

Documentation Index
Fetch the complete documentation index at: https://developers.cloudflare.com/cloudflare-for-platforms/llms.txt
Use this file to discover all available pages before exploring further.