Cloudflare Zones
Beta Feature
This input is currently in beta. If you run into any issues, please reach out to product@monad.com.
Retrieves zone data from Cloudflare for DNS and domain mapping. This input collects information about all zones (domains) associated with your Cloudflare account, including their status, DNS servers, configuration, and plan details.
Sync Type: Full Synchronisation
Requirements
- A Cloudflare account with API access
- An API Token with
Zone:Readpermission
Creating an API Token
- Log in to your Cloudflare dashboard
- Navigate to My Profile > API Tokens
- Click Create Token
- Use the Create Custom Token option
- Configure the token:
- Token name: Give it a descriptive name (e.g., "Monad Zones")
- Permissions: Add
Zone>Zone>Read - Zone Resources: Select the specific zone(s) or "All zones"
- Click Continue to summary and then Create Token
- Copy the token value (you won't be able to see it again)
Details
Monad uses the cron field to run this input on specific intervals and returns all zones, performing a full sync of data each time. The input retrieves comprehensive zone information including:
- Zone status and configuration
- DNS server information (both Cloudflare and original nameservers)
- Zone type (full setup, nameserver only, or partial setup)
- Associated plan and account information
- Zone metadata and permissions
The input uses paginated API requests with up to 50 zones per page to efficiently retrieve all zone data.
Configuration
The following configuration defines the input parameters. Each field's specifications, such as type, requirements, and descriptions, are detailed below.
Settings
| Setting | Type | Required | Default | Description |
|---|---|---|---|---|
cron | string (cron) | Yes | 0 * * * * | Cron string for scheduling the ingest of your input. eg: 0 0 * * * - Daily at midnight, or */15 * * * * - Every 15 minutes. Defaults to an hour. |
use_synthetic_data | bool | No | false | Generate synthetic data for testing, instead of connecting to a real data source. Defaults to an hourly cron schedule for cron-based inputs. |
rate_limit | object | No | - | Maximum outbound source-API request rate. A blank or zero value falls back to the connector's default rate-limiting behavior. Maximum 4 requests per second. See API Rate Limiting for the field format. |
Secrets
| Secret | Type | Required | Description |
|---|---|---|---|
api_token | secret | Yes | Your Cloudflare API token with Zone |
Rate Limits
| Scope | Limit | Window | Notes |
|---|---|---|---|
| API Requests | 1,200 | per 5 minutes | Standard rate limit across Cloudflare API |
Headers: X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset
Source: Cloudflare API Rate Limits
Related Articles
Sample Record
Code
Sync frequency
This input runs on a cron schedule (default hourly, 0 * * * *), which you can configure on the pipeline.
See Input Sync Frequency for details.
Community transforms
The Monad Transforms Repository has ready-made transforms for this input. Import one into your organization, then add it to a pipeline after this input.
| Format | Transform |
|---|---|
| OCSF v1.9.0 | Cloudflare Zones to OCSF v1.9.0 |
| ECS v9.5.0 | Cloudflare Zones to ECS v9.5.0 |
| CEF | Cloudflare Zones to CEF |
CEF transforms emit an intermediate record; add the CEF Serializer transform after one to produce the CEF:0 string.