Cloudflare
Cloudflare's REST API returns zones, DNS records, firewall events, Workers usage and account audit logs. Security, platform and web teams each care about a different part. In the Lake, firewall events can be grouped by rule and country, DNS changes traced through audit logs, and Workers usage set against the bill.
- Category
- Cloud & Data Platforms
- Type
- CDN & edge
- Interface
- REST API
- Built with
- Connect Any API
- Credentials
- Access token, API key
02Data
What you can sync.
- Zones
- Dns records
- Firewall events
- Workers usage
- Audit logs
Load Cloudflare zones into your Lake and model it in the Warehouse with the rest of your stack.
Need more? Name any other Cloudflare data the API returns, and the AI adds it to the connector.
03Credentials
Credentials you will need.
- An access token
- An API key
Cloudflare uses an access token or an API key. You add the credentials once, when the AI asks for them, and it tells you where to create them in Cloudflare if you need help.
04Questions
Questions you can answer.
Once Cloudflare data is in your Lake, ask an AI Mind in plain words or build the answer in DataPrism BI.
- Which WAF rules blocked the most requests last week, and from which countries?
- Who changed DNS records on production zones this month?
- How many Workers requests did each script handle per day?
- Which zones still have DNS records for hosts we have decommissioned?
05How it works
How it works in DataMind.
-
Pick Cloudflare.
Open Lake, pick Cloudflare in the source picker and name the connection. Connect Any API opens with a ready prompt that points the AI at the Cloudflare API docs.
-
Answer a few questions.
The AI reads the Cloudflare documentation, then asks which credentials you will use, which data to sync (for example zones and dns records), whether you want a one-time load or a recurring sync, and which accounts or filters apply.
-
Your data lands in Lake.
It builds the connector, tests it and shows you sample rows. Then Cloudflare data loads into your Lake on your schedule, ready for the Warehouse, DataPrism BI and AI Minds.
06Write back
Write data back to Cloudflare.
Send users, block senders and content list entries from your Lake and Warehouse to Cloudflare, on a schedule or when you run it. The AI reads the Cloudflare API docs, asks you a few questions and builds the destination with you.
Write Anything
What you can send.
- Users
- Block senders
- Content list entries
- Impersonation registries
- Indexes
- Indicator feeds
- List items
- Lists
A sync can create Cloudflare records from your rows and update the ones it finds by a key you choose.
Once you turn deletes on, it can also mark or delete the records whose rows left the source.
Keep Cloudflare users current from your own models, on the schedule you set.
Credentials
Credentials for writes.
- An API key
- An access token
Cloudflare takes an API key or an access token for writes. You add the credentials once, when the AI asks for them, and it tells you where to create them in Cloudflare if you need help.
-
Add Cloudflare in Writeback.
Open Writeback, click Add destination, choose Write Anything and name the destination. Then tell the AI it sends to Cloudflare and point it at the Cloudflare API docs.
-
Answer a few questions.
The AI reads the Cloudflare documentation, then asks which credentials you will use, which Cloudflare objects to fill (for example users and block senders) and whether to create, update or delete records.
-
Preview, test, then send.
The AI writes a Python destination for Cloudflare and builds it in a sandbox. Preview what it would send, send one test record, approve the first run, and the sync runs on your schedule.
07Pairs
Works well with Cloudflare.
Sources teams join with Cloudflare in the Warehouse, each one connected the same way.