Cloudflare Gateway can now forward traffic straight to a Worker
A new Forward action in Gateway HTTP policies sends matching traffic to a Worker instead of a separate proxy, with Zero Trust context attached.
Cloudflare Gateway now integrates with Workers, in public beta on all Zero Trust plans from 15 October. A new Forward action in Gateway HTTP policies routes matching traffic to a Worker instead of a separate inspection proxy.
Gateway still handles the proxy connection, TLS decryption and upstream routing itself. It evaluates HTTP request policies first, hands the request to your Worker along with Gateway context, connection metadata, user identity and device posture where available, then inspects the final response before it reaches the user. That’s enough for a Worker to transform requests and responses, serve a coaching page, or run a background task such as a Slack notification or an R2 capture.
Why it matters: teams building custom DLP, logging or coaching flows on top of Zero Trust traffic no longer need to stand up and operate a separate proxy. The logic lives in a Worker, deployed the same way as any other.
The caveat: Gateway inspects the original request body before your Worker sees it, and a body-inspection Block decision can interrupt the Worker before it runs.