Linking Cloudflare as a source
The Cloudflare connector syncs your Cloudflare configuration data into PostHog, including accounts, zones, and DNS records.
The Cloudflare source is currently in alpha. It syncs configuration data from Cloudflare's v4 REST API. High-volume analytics data from Cloudflare's GraphQL API is not yet supported.
Creating a Cloudflare API token
Before linking Cloudflare, create an API token with the required permissions:
- Go to the Cloudflare dashboard API tokens page.
- Click Create Token.
- Click Create Custom Token > Get started.
- Give your token a descriptive name (e.g. "PostHog Data Warehouse").
- Under Permissions, add the following with Read access:
| Resource | Permission |
|---|---|
| Account Settings | Read |
| Zone | Read |
| DNS | Read |
- Under Account Resources, select the accounts you want to sync.
- Under Zone Resources, select the zones you want to sync. Choose All zones to sync DNS records from every zone.
- Click Continue to summary, then Create Token.
- Copy the token – you won't be able to see it again.
Linking Cloudflare
- In PostHog, go to the Data pipeline page and select the Sources tab.
- Click New source and select Cloudflare by clicking Link.
- Paste your Cloudflare API token.
- Optional: Add a prefix to your table names.
- Click Next.
- Select the tables you want to import.
- Click Import.
PostHog validates your token against Cloudflare's /user/tokens/verify endpoint before starting the sync. If validation fails, check that your token has the required permissions listed above.
The data warehouse then starts syncing your Cloudflare data. You can see details and progress in the data pipeline sources tab.
Available tables
| Table | Description |
|---|---|
accounts | Cloudflare accounts accessible by the API token |
zones | Zones (domains) managed in those accounts |
dns_records | DNS records for each zone, with a _zone_id field linking each record to its parent zone |
DNS records are synced from every zone the token can access. Each DNS record row includes a _zone_id field so you can join it back to the zones table.
Sync modes
Cloudflare tables support full refresh syncing only. Each sync re-imports all records from Cloudflare.
Incremental and append-only syncs aren't available because Cloudflare's v4 REST API doesn't expose updated-since filters for these resources. Since these are small configuration tables, full refresh syncs complete quickly.
Configuration
| Option | Type | Required |
|---|---|---|
API token | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
accounts | A Cloudflare account that the API token can access. | Full refresh | — | — |
zones | A zone — a domain and its DNS/configuration managed in Cloudflare. | Full refresh | — | — |
dns_records | A DNS record belonging to a zone (A, CNAME, MX, TXT, and so on). | Full refresh | — | — |