Cloudflare#

Work with Cloudflare from chat — manage zones, DNS records, workers, rules, firewall settings, and account resources via the Cloudflare API with API token authentication.

This skill uses ClawLink for hosted connection flows and credentials so you do not need to configure Cloudflare API access yourself.

Setup in 3 Steps#

Step 1: InstallStep 2: Pair AccountStep 3: Connect Cloudflare_App-specific connection GIF coming soon_Run the install command in OpenClawSign in and approve the deviceOpen the dashboard and connect Cloudflare

How It Works#

text

┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐
│   OpenClaw      │────▶│   ClawLink   │────▶│ Cloudflare API    │
│   (User Chat)   │     │   (API Token)│     │ (Zones/DNS/APIs) │
└─────────────────┘     └──────────────┘     └──────────────────┘
         │                       │                       │
         │  1. Install Plugin    │                       │
         │  2. Pair Device       │                       │
         │  3. Connect Cloudflare│                       │
         │                       │  4. Secure Token      │
         │                       │  5. Proxy Requests    │
         │                       │                       │
         ▼                       ▼                       ▼
   ┌──────────┐           ┌──────────┐           ┌──────────┐
   │  SKILL   │           │ Dashboard│           │ Cloudflare│
   │  File    │           │ Auth     │           │ Dashboard│
   └──────────┘           └──────────┘           └──────────┘

Install#

Install the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.

bash

openclaw plugins install clawhub:clawlink-plugin
openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json
openclaw gateway restart

Then tell the user: "OpenClaw has been restarted. Send /new as a standalone message to start a fresh chat, then ask for Cloudflare again."

Quick Start#

bash

# List all zones
clawlink_call_tool --tool "cloudflare_list_zones" --params '{}'

# List DNS records in a zone
clawlink_call_tool --tool "cloudflare_list_dns_records" --params '{"zone_id": "ZONE_ID"}'

# List accounts
clawlink_call_tool --tool "cloudflare_list_accounts" --params '{}'

Authentication#

All Cloudflare tool calls are authenticated automatically by ClawLink using the user's connected Cloudflare account.

No API token is required in chat. ClawLink stores the API token securely and injects it into every Cloudflare API request on the user's behalf.

Getting Connected#

1. Install the ClawLink plugin (see Install above).
2. Pair the plugin with clawlink_begin_pairing if it is not configured yet.
3. Open https://claw-link.dev/dashboard?add=cloudflare and connect Cloudflare.
4. Call clawlink_list_integrations to verify the connection is active.

Connection Management#

List Connections#

bash

clawlink_list_integrations

Response: Returns all connected integrations. Look for cloudflare in the list.

Verify Connection#

bash

clawlink_list_tools --integration cloudflare

Response: Returns the live tool catalog for Cloudflare.

Reconnect#

If Cloudflare tools are missing or the connection shows an error:

1. Direct the user to https://claw-link.dev/dashboard?add=cloudflare
2. After they confirm, call clawlink_list_integrations to verify
3. Then call clawlink_list_tools --integration cloudflare

Security & Permissions#

• Access is scoped to the permissions granted by the Cloudflare API token.
• All write operations require explicit user confirmation. Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.
• Destructive actions (delete zone, delete DNS record, delete WAF list) are marked as high-impact and must be confirmed.

Tool Reference#

Zones#

ToolDescriptionModecloudflare_list_zonesList zones in the account with paginationReadcloudflare_create_zoneCreate a new DNS zone (domain)Writecloudflare_update_zoneUpdate zone properties (one field at a time)Writecloudflare_delete_zonePermanently delete a zone and all DNS recordsWrite

DNS Records#

ToolDescriptionModecloudflare_list_dns_recordsList and search DNS records in a zoneReadcloudflare_create_dns_recordCreate a new DNS record in a zoneWritecloudflare_update_dns_recordUpdate an existing DNS recordWritecloudflare_delete_dns_recordPermanently delete a DNS recordWrite

Accounts & Members#

ToolDescriptionModecloudflare_list_accountsList all Cloudflare accounts accessible to the userReadcloudflare_list_account_membersList account members with roles and permissionsRead

Load Balancers#

ToolDescriptionModecloudflare_list_monitorsList load balancer monitorsReadcloudflare_list_poolsList load balancer origin poolsRead

WAF & Rules#

ToolDescriptionModecloudflare_list_firewall_rulesList firewall rules for a zoneReadcloudflare_create_listCreate a WAF custom list (IPs, hostnames, ASNs)Writecloudflare_get_listsList all WAF listsReadcloudflare_update_listUpdate a WAF list descriptionWritecloudflare_delete_listDelete a WAF listWrite

Tunnels#

ToolDescriptionModecloudflare_list_tunnelsList Cloudflare Tunnel tunnelsReadcloudflare_update_tunnel_configurationUpdate tunnel ingress rules (replaces full config)Write

Bot Management#

ToolDescriptionModecloudflare_get_bot_management_settingsGet bot management configuration for a zoneRead

Code Examples#

List zones#

bash

clawlink_call_tool --tool "cloudflare_list_zones" \
  --params '{}'

Create a DNS record#

bash

clawlink_call_tool --tool "cloudflare_create_dns_record" \
  --params '{
    "zone_id": "ZONE_ID",
    "type": "A",
    "name": "api",
    "content": "192.0.2.1",
    "ttl": 3600
  }'

Update a DNS record#

bash

clawlink_call_tool --tool "cloudflare_update_dns_record" \
  --params '{
    "zone_id": "ZONE_ID",
    "dns_record_id": "RECORD_ID",
    "type": "A",
    "name": "api",
    "content": "192.0.2.2",
    "ttl": 1800
  }'

Delete a DNS record#

bash

clawlink_call_tool --tool "cloudflare_delete_dns_record" \
  --params '{
    "zone_id": "ZONE_ID",
    "dns_record_id": "RECORD_ID"
  }'

Discovery Workflow#

1. Call clawlink_list_integrations to confirm Cloudflare is connected.
2. Call clawlink_list_tools --integration cloudflare to see the live catalog.
3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.
4. If the user describes a capability but the exact tool is unclear, call clawlink_search_tools with a short query and integration cloudflare.
5. If no Cloudflare tools appear, direct the user to https://claw-link.dev/dashboard?add=cloudflare.

Execution Workflow#

text

┌─────────────────────────────────────────────────────────────┐
│  READ OPERATIONS (Safe)                                     │
│  list → get → describe → call                              │
│                                                             │
│  Example: List zones → List DNS records → Show results      │
└─────────────────────────────────────────────────────────────┘
                              │
                              ▼
┌─────────────────────────────────────────────────────────────┐
│  WRITE OPERATIONS (Require Confirmation)                     │
│  list → get → describe → preview → confirm → call         │
│                                                             │
│  Example: Describe tool → Preview changes → User approves   │
│           → Execute update                                 │
└─────────────────────────────────────────────────────────────┘

1. For unfamiliar tools, ambiguous requests, or any write action, call clawlink_describe_tool first.
2. Use the returned guidance, schema, whenToUse, askBefore, safeDefaults, examples, and followups to shape the call.
3. Prefer read, list, search, and get operations before writes when that reduces ambiguity.
4. For writes or anything marked as requiring confirmation, call clawlink_preview_tool first.
5. Execute with clawlink_call_tool. Pass confirmation only after the preview matches the user's intent.
6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.

Notes#

• Zone IDs and DNS record IDs are required for all zone-scoped operations — retrieve them via list tools first.
• Pagination: use page and per_page parameters and check result_info.total_pages to iterate all pages.
• Tunnel configuration updates replace the entire configuration — fetch the current config first to avoid losing existing rules.
• WAF lists have plan-based limits (Free: 1 list, Pro/Business: 10 lists, Enterprise: 1000 lists).
• DNS record updates only modify provided fields.

Error Handling#

Status / ErrorMeaningTool not foundThe tool name does not exist in the current catalog. Verify with clawlink_list_tools --integration cloudflare.Missing connectionCloudflare is not connected. Direct the user to https://claw-link.dev/dashboard?add=cloudflare.zone_not_foundZone does not exist or is not accessible.dns_record_not_foundDNS record does not exist.InvalidArgumentInvalid parameter or missing required field. Review the tool schema with clawlink_describe_tool.Write rejectedUser did not confirm a write action. Always confirm before executing writes.

Troubleshooting: Tools Not Visible#

1. Check that the ClawLink plugin is installed: bash

   openclaw plugins list
   
   

2. If the plugin is installed but tools are missing, tell the user to send /new as a standalone message to reload the catalog.

3. If a fresh chat does not help, run: bash

   openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json
   openclaw gateway restart
   
   

4. After restart, tell the user to send /new again and retry.

Troubleshooting: Invalid Tool Call#

1. Ensure the integration slug is exactly cloudflare.
2. Use clawlink_describe_tool to verify parameter names and types before calling.
3. For write operations, always call clawlink_preview_tool first.

Resources#

• Cloudflare API Documentation
• Cloudflare DNS API
• Cloudflare Zones API
• ClawLink: https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=cloudflare-infrastructure
• ClawLink Docs: https://docs.claw-link.dev/openclaw
• ClawLink Verification: https://claw-link.dev/verify

Related Skills#

• AWS — For AWS infrastructure management
• GitHub — For GitHub CI/CD and deployments
• Datadog — For observability and monitoring

---

Powered by ClawLink — an integration hub for OpenClaw