Skip to main content
Cloudflare Workers deployment details referenced in an Interfere investigation.Cloudflare Workers deployment details referenced in an Interfere investigation.
Connect Cloudflare to track Worker versions and associate deployments with releases.

​
Connect Cloudflare

Open Cloudflare settings and authorize the connection. Map the Worker to its Interfere surface. If your account can access multiple Cloudflare accounts, the integration connects the first accessible account. Check that the expected Workers appear before mapping a surface.

​
Tag deployments with the commit

Pass the source commit SHA as the deployment tag:
GitHub Actions provides GITHUB_SHA. In another CI system, supply its commit SHA instead. Use a raw commit SHA of 7 to 40 hexadecimal characters. Tags such as release-abc123 and v1.2.3 do not identify a source commit for Interfere.

​
Verify the release

After deploying, open the surface’s releases and check that the Worker version links to the expected commit. Untagged deployments still appear as releases, but have no source commit link. The deployment connection tracks versions. Install an SDK in your app separately to capture application telemetry.

​
Permissions and reconnection

Interfere requests memberships.read to list accessible accounts and workers-scripts.read to list Workers. offline_access keeps the connection authenticated between visits. If access expires or is revoked, reconnect in Integrations.