Integrations · Cloudflare
A Guild agent can manage your Cloudflare accounts and infrastructure on your behalf. Guild stores the API key server-side and injects it as a bearer token, so agent code never sees the credential. Credential policies let you restrict which operations and resources each agent can reach, and every request passes through Guild’s credential proxy before it touches Cloudflare.
Book a demo
See how teams govern agents that use Cloudflare.
Talk to sales
Get access to Guild, then connect Cloudflare to your first agent.
What the Cloudflare integration exposes
The integration is published asguildai~cloudflare-openapi and covers accounts, zones, DNS records, Workers scripts and secrets, Workers KV namespaces, R2 buckets, and Pages projects. Tools follow the cloudflare_openapi_ naming prefix. Use pick() from the SDK tools reference to include only the tools your agent needs.
How it works
1
Open credentials in Guild
Go to Access & setup > Credentials in Guild. The Credentials page lists integrations you can connect at account, workspace, member, or agent scope.
2
Connect the Cloudflare integration
Click Connect, select cloudflare-openapi, and paste your Cloudflare API token into the API Key field. Guild stores it and sends it as a bearer token in the
Authorization header on every request.3
Import tools into your agent
Import
CloudflareOpenapiTools from @guildai-services/guildai~cloudflare-openapi and spread it into your agent’s tools object. Use pick() to select specific tools by their cloudflare_openapi_ prefixed names.Why Cloudflare access needs governing
Cloudflare tools can create or delete accounts, overwrite DNS records, deploy Workers scripts, and modify R2 bucket policies. Guild’s credential proxy enforces credential policies before any request reaches Cloudflare. You write ALLOW and DENY rules scoped to specific operations, agents, or workspaces, so one agent can read DNS records while another is blocked from deleting Workers scripts, all on the same connected credential. Guild injects the API key server-side, so agents never handle the token directly and cannot bypass policy checks. You can scope credentials to a single workspace, a single member, or a single agent using Credentials, keeping shared organization credentials separate from sensitive per-agent access. A deny-all posture takes effect for any request not covered by an explicit ALLOW rule once you remove the default allow-all policy.About the Cloudflare integration
Agents can manage Cloudflare accounts and zones, create and update DNS records, deploy and configure Workers scripts and secrets, administer R2 buckets with storage policies and event notifications, and manage Pages projects and their deployments. The integration isguildai~cloudflare-openapi.
Authentication
- Type: API key
- Header: Guild sends the key as a bearer token in the
Authorizationheader
Setup
1
Connect Cloudflare
In Guild, go to Access & setup > Credentials, click Connect, select cloudflare-openapi, and paste the key into API Key.
Usage
Selecting specific tools
Tools are named with thecloudflare_openapi_ prefix. Use pick() to include only what your agent needs.
Tools
Tools in the latest published version ofguildai~cloudflare-openapi:
All 137 tools
All 137 tools
Frequently asked questions
Does the agent ever see my Cloudflare API key?
Does the agent ever see my Cloudflare API key?
No. Guild stores the key and injects it as a bearer token in the Authorization header server-side. Agent code never receives or handles the credential directly.
Can I stop an agent from deleting DNS records or Workers scripts?
Can I stop an agent from deleting DNS records or Workers scripts?
Yes. Write a DENY rule targeting the relevant operations in a credential policy. DENY rules take precedence over ALLOW rules, and Guild’s proxy enforces them before any request leaves Guild.
Can I give different agents different levels of Cloudflare access?
Can I give different agents different levels of Cloudflare access?
Yes. Credential policy rules accept an agents field, so you can allow one agent to list and read DNS records while blocking another from creating or deleting them, all on the same connected credential.
Does the Cloudflare integration support webhook events from Cloudflare?
Does the Cloudflare integration support webhook events from Cloudflare?
Not yet. The catalog entry for guildai~cloudflare-openapi lists no webhook events, so the integration does not receive inbound event notifications from Cloudflare.
Put a governed agent on Cloudflare this week
Book a demo
See how teams govern agents that use Cloudflare.
Talk to sales
Get access to Guild, then connect Cloudflare to your first agent.