Get started Dashboard
← All integrations
Cloudflare

Cloudflare integration: connect Workers, Pages, R2 and D1 to Polylane

Connect Cloudflare Workers, Pages, R2 and D1 to Polylane with a read-only token. Follow bindings and deployment changes to investigate edge failures.

Why Polylane for Cloudflare

Get started for free

How to set up Cloudflare

The flow validates the pasted token before connection. No measured end-to-end setup duration is published; allow for token creation and initial resource discovery.

  1. In Polylane, choose Cloudflare under Settings → Cloud accounts and open Create API token.
  2. Select the Cloudflare account. Creating an account-owned token requires Super Administrator; full resource discovery requires the Workers Paid plan.
  3. Keep the pre-filled read-only permissions, create the token and paste it into the connection form. Wait for validation, then connect.

Permissions and access

The current console requests an account-owned read-only token, not a full-access token. Its template includes Workers scripts, content and metadata reads; Workers observability and tail; Pages, KV, R2 Storage, D1, Queues, Hyperdrive, Vectorize, AI Gateway, DNS, zone settings, Access, tunnels, analytics and other account resource reads. Edit grants are converted to Read; action-only Run, Send and Purge grants are dropped. R2 object permissions are excluded. The complete template key list is available below. No full-access option is offered by this connection form.

Discovery, refresh and the connected view

A scheduled check runs every 15 minutes and requests a resource sync when account changes warrant one; it is not an unconditional full scan every 15 minutes. Workers, bindings, Pages, Durable Objects, databases, storage, queues, zones and the supported resources below appear as linked nodes with configuration and change history.

Disconnect and revoke access

Disconnect the account in Polylane to stop syncing, then revoke the account API token in Cloudflare. An account-owned token survives the departure of its creator until it is revoked.

Provider credentials and Polylane’s access mode are separate. Where write-capable tools exist, the connected account’s Settings page offers a Read-only switch. Turning it off permits writes subject to review and confirmation, but cannot add permissions to the provider credential. Agent-connected Kubernetes clusters stay read-only.

Exact Cloudflare token template permissions

Every key below uses type read, except the two Workers keys marked only. The current console does not request the full-access template.

  • access:read
  • access_acct:read
  • access_app:read
  • access_audit_log:read
  • access_certificate:read
  • access_custom_page:read
  • access_device_posture:read
  • access_group:read
  • access_idp:read
  • access_key:read
  • access_org:read
  • access_policy:read
  • access_policy_test:read
  • access_population:read
  • access_saml_certificate:read
  • access_scim_log:read
  • access_service_token:read
  • access_ssh_auditing:read
  • access_tag:read
  • access_users:read
  • account_abuse_protection_pii:read
  • account_analytics:read
  • account_api_gateway:read
  • account_api_tokens:read
  • account_custom_asset:read
  • account_custom_error_rules:read
  • account_custom_pages:read
  • account_disable_esc:read
  • account_dns_settings:read
  • account_firewall_access_rules:read
  • account_logs:read
  • account_rule_lists:read
  • account_rule_policies:read
  • account_rulesets:read
  • account_security_center_insights:read
  • account_settings:read
  • account_ssl_and_certificates:read
  • account_waf:read
  • account_waiting_rooms:read
  • address_maps:read
  • agw:read
  • ai:read
  • ai_search:read
  • ai_search_metadata:read
  • aiaudit:read
  • aig:read
  • analytics:read
  • api_gateway:read
  • argotunnel:read
  • artifacts:read
  • billing:read
  • bot_management:read
  • bot_management_feedback:read
  • browser_rendering:read
  • cache_settings:read
  • calls:read
  • casb:read
  • cf_agents:read
  • challenge_widgets:read
  • chinanetwork_steering:read
  • cloud_connector:read
  • cloud_email_security:read
  • cloudchamber:read
  • cloudforce_one:read
  • config_settings:read
  • connectivity_directory:read
  • constellation:read
  • containers:read
  • custom_errors:read
  • custom_pages:read
  • d1:read
  • d1_metadata:read
  • ddos_botnet_feed:read
  • ddos_protection:read
  • dls:read
  • dns:read
  • dns_firewall:read
  • dns_view:read
  • domain_page_shield:read
  • dynamic_redirect:read
  • email_routing_address:read
  • email_routing_rule:read
  • email_routing_suppression:read
  • email_security_dmarcreports:read
  • email_sending:read
  • fbm:read
  • firewall_for_ai:read
  • firewall_services:read
  • flagship:read
  • fraud_detection:read
  • healthcheck:read
  • http_applications:read
  • http_ddos_managed_ruleset:read
  • images:read
  • images_metadata:read
  • intel:read
  • iot:read
  • ip_prefix:read
  • ip_prefix_bgp_on_demand:read
  • l4_ddos_managed_ruleset:read
  • load_balancers:read
  • load_balancers_account:read
  • load_balancing_monitors_and_pools:read
  • logs:read
  • magic_firewall:read
  • magic_transit:read
  • magic_wan:read
  • managed_headers:read
  • mass_url_redirects:read
  • mcp_portals:read
  • moq:read
  • notifications:read
  • oauth_client:read
  • origin:read
  • page:read
  • page_rules:read
  • page_shield:read
  • pcaps_api:read
  • pipelines:read
  • pubsub:read
  • query_cache:read
  • queues:read
  • queues_metadata:read
  • r2_catalog:read
  • r2_catalog_sql:read
  • radar:read
  • rag:read
  • realtime:read
  • registrar_domains:read
  • reports_application_security_report:read
  • request_tracer:read
  • resource_library:read
  • resource_sharing:read
  • response_compression:read
  • sanitize:read
  • secrets_store:read
  • select_configuration:read
  • snippets:read
  • ssl_and_certificates:read
  • sso_connector:read
  • stream:read
  • stream_metadata:read
  • tag:read
  • teams:read
  • teams_cds_compute_account:read
  • teams_connector_cloudflared:read
  • teams_connector_warp:read
  • teams_connectors:read
  • teams_dex:read
  • teams_networks:read
  • teams_pii:read
  • teams_resilience:read
  • transform_rules:read
  • trust_and_safety:read
  • url_scanner:read
  • vectorize:read
  • waiting_rooms:read
  • web3_hostnames:read
  • workers_ci:read
  • workers_kv_storage:read
  • workers_kv_storage_metadata:read
  • workers_observability:read
  • workers_r2:read
  • workers_r2_metadata:read
  • workers_routes:read
  • workers_scripts:read
  • workers_tail:read
  • zaraz:read
  • zone:read
  • zone_access:read
  • zone_custom_asset:read
  • zone_disable_esc:read
  • zone_dns_settings:read
  • zone_security_center_insights:read
  • zone_settings:read
  • zone_transform_rules:read
  • zone_versioning:read
  • zone_waf:read
  • workers_content_read:only
  • workers_metadata_read:only

In the graph.

Every Cloudflare resource Polylane picks up sits in the graph with its connections, config and history.

Cloudflare Worker
AI Gateway
Cloudflare Container
Durable Object
D1 Database
Hyperdrive
Cloudflare KV
Cloudflare Pipeline
Pipeline Stream
Pipeline Sink
R2 Bucket
R2 Domain
Cloudflare Queue
Secret Store
Cloudflare Secret
Cloudflare Pages
Domain
AI
Analytics Engine
Browser Rendering
Vectorize
Cloudflare Workflow
Cloudflare Zone
Worker Route
Worker Domain
Dispatch Namespace
Tenant Worker
Snippet
mTLS Certificate
Cloudflare Tunnel
Access Application
Spectrum App
Turnstile Widget
Waiting Room
Health Check
Load Balancer
Load Balancer Pool
Load Balancer Monitor
Logpush Job
SSL Certificate
Email Address
Stream Live Input
Cloudflare Images
Calls App
AutoRAG
R2 Data Catalog
Artifacts Namespace

Tools for the investigation.

What Polylane can do with Cloudflare while it investigates. Every call is recorded in the transcript.

Cloudflare Polylane MCP
  • cloudflareListTelemetryKeys List available Cloudflare telemetry data keys
  • cloudflareListTelemetryValues List values for a Cloudflare telemetry key
  • cloudflareRunTelemetryQuery Query Cloudflare Workers / container logs, traces, and AI Gateway request logs
  • cloudflareTraces Read Cloudflare traces (list summaries, get full span tree)
  • cloudflareRunGraphqlQuery Execute a GraphQL query against the Cloudflare Analytics API
  • cloudflareGraphqlSchemaSearch Search the Cloudflare GraphQL schema for matching types, fields, args, and enum values
  • cloudflareGraphqlSchemaOverview Fetch a paginated overview of all Cloudflare GraphQL types
  • cloudflareGraphqlTypeDetails Fetch fields, args, and enum values for one Cloudflare GraphQL type
  • cloudflareGraphqlCompleteSchema Fetch the Cloudflare GraphQL schema with optional root-type details
  • cloudflareAiGatewayLogs List Cloudflare AI Gateway logs, or fetch one log's full detail
  • cloudflareAccessApplicationLogs List Cloudflare Access authentication events for an Access application
  • cloudflareWorkflowInstances List or get Cloudflare Workflows instances
  • cloudflareApi Call any Cloudflare REST API endpoint that lacks a dedicated tool
  • cloudflareDeployments List Cloudflare Worker/Pages deployments or Worker versions

Cloudflare setup and troubleshooting

All guides for Cloudflare

Docker context deadline exceeded

Common questions.

How does Polylane connect to my Cloudflare account?

In Polylane, choose Cloudflare under Settings → Cloud accounts and open Create API token. Select the Cloudflare account. Creating an account-owned token requires Super Administrator; full resource discovery requires the Workers Paid plan. Keep the pre-filled read-only permissions, create the token and paste it into the connection form. Wait for validation, then connect.

What Cloudflare resources does Polylane sync?

A scheduled check runs every 15 minutes and requests a resource sync when account changes warrant one; it is not an unconditional full scan every 15 minutes. Workers, bindings, Pages, Durable Objects, databases, storage, queues, zones and the supported resources below appear as linked nodes with configuration and change history.

Connect it once. Then get back to shipping.