DNS records, zones, page rules, firewall, Workers, R2 buckets, cache purge
DevOps & Infrastructure 20 actions API token
Start automating CloudflareDrag any of these 20 actions into a process — no code, no API wrangling.
Add a new DNS record
Create a new R2 bucket
Add a new zone to the account
Delete a DNS record
Delete an R2 bucket (must be empty)
Delete a zone
Get a single DNS record
Get the authenticated user's details
Get a Worker script's metadata
Get details of a single zone
List DNS records for a zone
List WAF custom rules for a zone (rulesets entry-point)
List Workers KV namespaces
List page rules for a zone
List R2 storage buckets on the account
List Worker scripts on the account
List zones on the account
Purge the Cloudflare cache for a zone (by URL, tag, host, or purge-everything)
Update an existing DNS record
Verify the supplied API token
Cloudflare uses aPI token. Save the connection once and reuse it across every process.
Drop Cloudflare steps onto the process map alongside desktop, browser, Excel and email steps.
Trigger on a schedule, an email, or a file landing in a folder. Credentials stay encrypted and every run is audited.
Because Cloudflare has an API, Automize talks to it directly in the cloud — no bot needed on a desktop. Where a system has no API, an Automize bot drives its interface instead.
We build one working Cloudflare automation in your business inside a week, at a fixed price.