Skip to main content
Connecting Cloudflare lets Interfere follow your Worker deployments and tie each version to a release. Connect it from Settings → Integrations → Cloudflare.

​
What we use it for

  • List the Workers in your account.
  • Track new versions as they’re deployed, so a problem lines up with the version that shipped it.

​
Permissions

Interfere authorizes through Cloudflare with read-only scopes:
ScopeWhy
memberships.readList the Cloudflare accounts you can access.
workers-scripts.readList the Worker scripts in your account.
offline_accessGet a refresh token so the connection stays alive without re-auth.

​
Tag your deploys with the commit SHA

To tie each Worker version back to the code that shipped it, pass the commit SHA when you deploy: 
wrangler deploy --tag $GITHUB_SHA
GitHub Actions sets GITHUB_SHA automatically. Interfere reads this tag from each Worker version and links it to its source commit. Use the raw commit SHA (7–40 hex characters); prefixed tags like release-abc123 or v1.2.3 are ignored.

​
Gotchas

  • One account at a time. If you belong to more than one Cloudflare account, Interfere connects the first one it can access.
  • Reconnect if access lapses. If the connection expires, reconnect it from Settings → Integrations.
  • No tag, no source link. Deploys without a --tag commit SHA still show up as releases, but they won’t be tied to a commit.