Skip to main content
Telara

Integrations / Cloudflare

Cloudflare logo

Cloudflare

Cloudflare API for DNS, zones, Workers, Pages, WAF, audit logs, and Zero Trust Access/Tunnel operations.

OAuth 2.0
Indexes
Actions
Events

What Telara does

Capability matrix

Before you connect

Prerequisites

A Cloudflare account you can administer.

Vendor setup

Get the credential

1
Prefer a scoped API token
In Cloudflare, open My Profile → API Tokens. Create a token limited to the accounts and zones Telara should see.
2
Paste in Telara
Settings → Integrations → Cloudflare. Prefer the token path. Connect is available when your account can use the hosted button.

In Telara

Connect in Telara

OAuth 2.0

Cloudflare OAuth client for account, zone, DNS, Workers, Zero Trust, and audit-log access. Scope IDs are selected from Cloudflare's OAuth scope catalog during app setup; Telara requests broad app scopes and enforces tenant/user policy internally.

In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.

Bearer token

Scoped Cloudflare API token. Prefer account/zone-scoped tokens with least privilege.

In Telara, open Settings → Integrations, choose this connector, and paste the bearer token into the field Telara shows.

Fields Telara asks for
  • API token

Knowledge

What gets indexed

ResourceCoverage
ZonePartial — not every record the vendor holds is synced

Sync

Freshness & sync

ResourceLagDeletions
ZoneUp to 1 dayRemoved records disappear on the next full sync

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

Excluded from semantic search: Zone.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

Global API keys are broader than Telara needs. A scoped token is the usual setup.
The token’s account/zone filter is the usual reason a zone list is empty.