Cloudflare Configuration Troubleshooting
Diagnose Cloudflare DNS, firewall, bot, and tunnel configuration from live read-only evidence.
@Aident8,190111Updated Aug 12, 2026
Works with
name: cloudflare-configuration-troubleshooting description: "Diagnose Cloudflare DNS, firewall, bot, and tunnel configuration from live read-only evidence."
Cloudflare Configuration Troubleshooting
Diagnose Cloudflare DNS, firewall, bot, and tunnel configuration from live read-only evidence.
Required Aident Actions
- <action-tag>composio:cloudflare_tools:cloudflare_list_zones</action-tag> (required inputs: inspect the current schema): Lists, searches, sorts, and filters zones in the authenticated account. Use
page/per_pageto paginate; checkresult_info.total_pagesin the response to iterate all pages. Does not return DNS records - extract... - <action-tag>composio:cloudflare_tools:cloudflare_list_dns_records</action-tag> (required inputs: zone_id): Tool to list and search DNS records in a Cloudflare zone. Use when you need to find existing DNS record IDs for update or delete operations, especially after a "record already exists" error during creation. Returns...
- <action-tag>composio:cloudflare_tools:cloudflare_Action · List Zonest firewall rules for a specific DNS zone. Use after confirming the zone ID to retrieve and audit current firewall rules. Does not expose Workers routes or other routing constructs.
- <action-tag>composio:cloudflare_tools:cloudflare_get_bot_management_settings</action-Action · List Dns Recordsiguration (Bot Fight Mode / Super Bot Fight Mode / Enterprise Bot Management). Use after identifying the correct zone_id (e.g., via CLOUDFLARE_LIST_ZONES). This tool is...
- <action-tag>composio:cloudflare_tools:cloudflare_list_tunnels</action-tag> Action · List Firewall Rules account to discover tunnel IDs, names, and statuses. Use when you need to find a tunnel_id before performing tunnel operations like routing, DNS configuration, or...
Use Aident Loadout to read the current Action schema beAction · Get Bot Management Settingsn Action is billable or mutating, run Aident preflight, show the affected target and quoted cost or risk, and wait for explicit user confirmation before execution.
Workflow
- Confirm the requested outcome, source material, destination, audienAction · List Tunnelsance below to create a concrete plan. Resolve ambiguity before invoking an Action.
- Select only the Aident Actions whose documented effect directly advances the requested outcome. Do not invoke every listed Action by default.
- Inspect the current schema and prepare the minimum valid input for each selected Action.
- Preflight each selected Action. Execute it only after any required confirmation, in dependency order, and carry returned IDs or asset URLs into later steps.
- Verify the returned IDs, URLs, statuses, or artifacts against the acceptance criteria. Report partial completion precisely and do not repeat paid or mutating calls blindly.
Source-Derived Guidance
- Resolve one zone and symptom before collecting configuration.
- Identify the evidence-backed fault domain and propose changes without applying them.
Execution Boundaries
- Treat upstream provider-specific commands as background knowledge only. Execute the workflow through the exact Aident Actions above.
- Never request raw credentials in chat. Use Aident Vault connection flows for required accounts.
- Preserve user-provided wording, brand constraints, rights restrictions, and target identifiers. Do not invent authorization.
- Read current state before a mutation, state the exact target, and include a rollback or recovery step in the result.
- Stop when a required integration is disconnected, preflight rejects the input, the target is ambiguous, or the user declines a required confirmation.
Output
Return the execution plan, selected Action names, confirmed targets, Aident result identifiers or asset URLs, verification evidence, and any remaining blocked step.
Attribution
This Skill adapts the reviewed upstream workflow. See for the pinned source and for the preserved license.