Cloudflare + Sidebox
Keep Workers and Pages deployments, build status, runtime activity, and Web Analytics traffic beside the product they belong to.
How to connect
Create a user API token in Cloudflare's My Profile → API Tokens. Choose read permissions for the features you use and scope the token to one account.
Choose Cloudflare in Sidebox's Workspace Connections. Enter the user API token and the 32-character Cloudflare Account ID.
Map one to three Workers or Pages projects and, optionally, one Web Analytics site from the same account. At least one Worker or Pages project is required.
Open your project's Deployments and Analytics pages to refresh its first summaries. Missing feature permissions are shown separately, so accessible sections remain usable.
Permissions and why we use them
These are the permissions used by Sidebox's current connection. Review the provider's authorization screen or key settings before granting access.
- Workers Scripts: Read
- Discover Workers and read their current deployment, deployed version IDs, traffic percentages, and recent deployment history. Grant this or Pages Read to connect.
- Pages: Read
- Discover Pages projects and read the serving production deployment, latest attempt, recent deployments, and finished-build statistics. Grant this or Workers Scripts Read to connect.
- Workers Builds Configuration: Read (optional)
- Read the latest Worker build status, branch, commit, and duration when available. The API calls this Workers CI Read. If Cloudflare only offers Edit, omit this optional permission; build status remains unavailable.
- Account Analytics: Read (optional)
- Read Worker requests, runtime errors, CPU percentiles, and Web Analytics traffic, audience breakdowns, and Core Web Vitals. Available datasets depend on your Cloudflare account and permissions.
- Account Settings: Read (optional)
- Discover and verify the optional Web Analytics site. This account permission also permits reading other account settings, although Sidebox only uses the fields needed for the connection and site discovery.
Disconnecting and revoking access
Disconnecting deletes the stored token and removes the connection and its mappings from Sidebox. It does not revoke the token in Cloudflare. Revoke the token in your Cloudflare profile, or replace it in Sidebox with a token for the same account.
Disconnecting does not delete the underlying data in Cloudflare. See our data handling page for Sidebox's retention and deletion behavior.
This provider connection supplies cached data to Sidebox. It is separate from an MCP connection, which shares requested Sidebox records with an external client you authorize.