Cloudflare Zero Trust Access Requests
Beta Feature
This input is currently in beta. If you run into any issues, please reach out to product@monad.com.
Ingests Cloudflare Zero Trust Access authentication events and access requests. This input collects authentication events that record user access attempts to applications protected by Cloudflare Zero Trust Access, including login/logout actions, identity provider information, and temporary access approvals.
Sync Type: Incremental
Requirements
- A Cloudflare account with Zero Trust Access enabled
- An API Token with the
Access: Audit Logs Readpermission - Your Cloudflare Account ID
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 Zero Trust Access")
- Permissions: Add
Account>Access: Audit Logs>Read - Account Resources: Select the specific account(s) or "All accounts"
- Click Continue to summary and then Create Token
- Copy the token value (you won't be able to see it again)
Finding Your Account ID
- Log in to your Cloudflare dashboard
- Select the account you want to monitor
- The Account ID is displayed in the right sidebar on the overview page
- Alternatively, find it in the URL:
https://dash.cloudflare.com/{account_id}/...
Details
- State Management: Uses ascending cursor-based pagination with timestamp tracking. Monad stores the last processed timestamp to fetch only new events on subsequent runs.
- API Endpoint:
GET /accounts/{account_id}/access/logs/access_requests - Pagination: Time-based pagination with a
sinceparameter and up to 1000 records per page, sorted in ascending order by timestamp. - Rate Limits: 1200 requests per 5 minutes (4 requests per second). The input automatically enforces this limit.
- Deduplication: Uses
ray_id(unique Cloudflare request identifier) to prevent duplicate records.
Configuration
Settings
| Setting | Type | Required | Default | Description |
|---|---|---|---|---|
account_id | string | Yes | - | Cloudflare Account ID |
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. |
backfill_start_time | date | No | - | Date to start fetching data from (RFC3339 format) |
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 | API Token with Access |
Rate Limits
| Limit | Value | Notes |
|---|---|---|
| Requests per 5 minutes | 1,200 | Enforced by Cloudflare |
| Max records per page | 1,000 | Maximum allowed by API |
Source: Cloudflare API Rate Limits
Troubleshooting
Common Issues
Issue: API returned success=false with authentication error
Cause: The API token is invalid, expired, or lacks the required permissions.
Solution: Verify your API token is correct and has the Access: Audit Logs Read permission.
Create a new token if needed.
Issue: Account ID is required validation error
Cause: The Account ID field was left empty.
Solution: Enter your Cloudflare Account ID in the settings. You can find this in your Cloudflare dashboard.
Issue: No data returned despite having access requests Cause: The backfill start time may be set to a future date, or there may not be any access events in the specified time range. If the backfill start time is left empty, the input starts collecting from the time it first runs and does not fetch older events. Solution: Verify the backfill start time is set correctly. To collect older events, set an earlier backfill start time.
Issue: Rate limit exceeded errors Cause: Multiple integrations or manual API calls are consuming the rate limit quota. Solution: The input automatically handles rate limiting. If you see persistent errors, reduce the frequency of other API calls to your Cloudflare account.
Related Articles
- Cloudflare Zero Trust Access API Documentation
- Cloudflare API Tokens
- Cloudflare API Rate Limits
- Zero Trust Access Overview
Sample Record
Code
Sync frequency
By default this input polls approximately every 10 seconds, with each sync beginning after the previous one completes. A cron schedule configured on the pipeline overrides this cadence. 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 Zero Trust Access Requests to OCSF v1.9.0 |
| ECS v9.5.0 | Cloudflare Zero Trust Access Requests to ECS v9.5.0 |
| CEF | Cloudflare Zero Trust Access Requests to CEF |
CEF transforms emit an intermediate record; add the CEF Serializer transform after one to produce the CEF:0 string.