Cloudflare
Cloudflare DNS and cache control
Cloudflare on Tiny Command is the operations-side connector for DNS and edge cache management — the things that turn into Slack pages at 2am when something is broken. Six actions, no triggers: List Zones (one per domain on the account), Create DNS Record, Update DNS Record, Delete DNS Record, List DNS Records (with filtering by type, name, or content), and Purge Cache (full-zone or by URL/tag/host). The connection uses a scoped API token (preferred over the legacy global API key — create one at My Profile → API Tokens with the specific zone and resource permissions the workflows need). DNS record changes propagate in under a minute on Cloudflare's edge; the response includes the record ID for round-tripping back into Update Delete. Purge Cache supports three modes: full zone purge (nuclear option, only on Pro+ plans without rate limits), purge by URL (up to 30 URLs per call), and purge by cache-tag (requires Enterprise). Most app-deploy workflows do URL-based purges scoped to the changed assets to avoid edge-cache stampedes.
Do anything Cloudflare can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Create DNS Record | Creates an A, AAAA, CNAME, TXT, MX, or other DNS record on a Cloudflare zone with optional proxied flag for routing through Cloudflare's edge. For "deploy created new subdomain → auto-create DNS record" infrastructure-as-workflow patterns. |
| Delete DNS Record | Removes a specific DNS record by ID. Irreversible. For "service decommissioned → clean up the DNS record" workflows or for deploy-rollback automation that removes records added by a failed deploy. |
| List DNS Records | Returns paginated DNS records on a zone with filters by type, name, content. Useful for DNS audits, for "find the IP this CNAME points to" lookups, or for backup workflows that snapshot DNS state daily. |
| List Zones | Returns every zone (each Cloudflare-managed domain) with name, status, plan. Useful for multi-domain organisations running cross-zone operations (e.g., "purge cache on all production zones simultaneously"). |
| Purge Cloudflare Cache | Purges cached content by URL (up to 30 per call), by tag (Enterprise tier), or by hostname. Most app-deploy workflows do URL-based purges scoped to the changed assets to avoid edge-cache stampedes on a full purge. |
| Update DNS Record | Updates a DNS record's content, TTL, or proxied flag. Useful for "service migrated to new IP → update A record" deploy automation or for failover-routing workflows that toggle DNS pointing. |
Pre-built Cloudflare workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Cloudflare once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Cloudflare field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Cloudflare integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Cloudflare to Tiny Command?
What Cloudflare triggers does Tiny Command support?
What Cloudflare actions can I run from a workflow?
Is the Cloudflare integration real-time?
Do I need to write code to use Cloudflare with Tiny Command?
How much does the Cloudflare integration cost?
More developer tools apps people connect.
Same category as Cloudflare, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Cloudflare.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
