Developer Tools · Integration
Cloudflare
Add Cloudflare to your product for your customers, and give your AI agents governed access to it.
Cloudflare's API at api.cloudflare.com/client/v4 is organised under accounts and zones, and that split decides everything: DNS records, page rules and WAF settings hang off a zone ID, while Workers scripts, R2 buckets and Pages projects hang off an account ID, so the first job of any integration is working out which identifier a given call needs. Scoped API tokens are bound to a named permission set and a resource list, so a token that can read zones answers a Workers call with a 403 and a populated errors array rather than a 401, while the legacy global API key sent with X-Auth-Email still works and grants everything, which is why it should not be the credential you ask customers for. Every response uses the same envelope of success, errors, messages and result, and a request can return HTTP 200 with success set to false, so status codes on their own are not a safe check. Of the available catalogue categories Developer Tools is the closest fit because the deployment-shaped objects here are Workers and Pages builds, although most integrations spend their time on DNS records and zone settings instead. fastn holds each customer's scoped token, keeps calls pinned to the right account or zone and tracks permission changes.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Cloudflare account so your product can create the DNS records a custom domain needs
Verify and provision certificates for customer vanity domains without a support ticket
Purge cache for specific URLs when a customer publishes content in your application
Read zone settings and firewall rules so your onboarding checks can tell a customer what is misconfigured
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent to list DNS records pointing at a decommissioned host across a customer's zones, with every zone read audited per tenant
Have an agent create a CNAME for a new customer subdomain within a whitelisted zone and nothing else
Let an agent summarise which zones have development mode still switched on
Example prompt
Which of our Cloudflare zones still have DNS records pointing at the old load balancer?
Set up Cloudflare in 4 steps
- 01Enable the Cloudflare connector from your fastn dashboard.
- 02Have each customer authorise their own Cloudflare account, so calls run under their credentials rather than a shared key.
- 03Decide which services, builds and deployments your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Cloudflare integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Cloudflare integration without building it. Your customers connect their own Cloudflare account inside your product and work their services, builds and deployments there, with no per-customer code on your side.
- Handle the part that actually costs time: these systems emit a lot of webhooks, and replay after downtime has to be handled. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Cloudflare update is not your on-call problem.
- One integration serves your product and your agents. The same governed Cloudflare connection powers in-product features and gives AI agents scoped, audited access, so you connect engineering activity to the rest of the business without wiring it twice.
Used by these teams
Compare with
GitHub
Azure DevOps
Google CloudOften used alongside
Tools the same teams tend to run next to Cloudflare, across other categories.
Slack
Snowflake
Airtable
PostgreSQLCloudflare integration FAQ
How do I add a Cloudflare integration to my product?
Enable the Cloudflare connector in your fastn dashboard, then let each customer authenticate their own Cloudflare account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Cloudflare client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Cloudflare account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Cloudflare account and only ever sees their own services, builds and deployments. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Cloudflare integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Ask an agent to list DNS records pointing at a decommissioned host across a customer's zones, with every zone read audited per tenant
Who maintains the Cloudflare integration?
fastn does. When Cloudflare changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can I react to Cloudflare events in real time?
Yes, through event triggers. Events are delivered per tenant and can be replayed after an outage, so a webhook missed during downtime is not silently lost.
Can an agent open or update items in Cloudflare?
Yes, within scoped permissions, and every action is audited so an agent's changes are attributable.
What can I build with the Cloudflare integration?
A common starting point: let a customer connect their own Cloudflare account so your product can create the DNS records a custom domain needs. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Cloudflare integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Cloudflare does not change your per-connector cost. You can start free with 3 connected accounts.
Add Cloudflare to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.