Cloudflare Integration

Cloudflare automation

591 operations availableDeveloper Tools

Cloudflare runs a global edge network covering DNS, security, storage, and compute. The NoClick Cloudflare node reaches across that surface: manage DNS records and firewall rules, write to KV and D1, query Vectorize indexes, deploy Worker scripts, handle R2 buckets, and run Workers AI inference. It lets you operate edge infrastructure from inside an automated workflow.

What you can automate with Cloudflare

Pick one to start building it.

Cloudflare Operations

Triggers23

DNS Record5

Zone14

Worker7

KV8

D1 Database10

R2 Bucket18

Pages8

Stream24

Image5

Firewall Rule3

WAF5

Access30

Tunnel9

Email Routing9

Queue11

Workers AI17

Vectorize12

Load Balancer15

SSL2

Workers19

Pipelines5

Secrets Store8

Rulesets11

Page Rules5

Rate Limiting5

Custom Hostnames5

Waiting Rooms8

Logpush8

Audit Logs1

Notifications11

Health Checks5

Spectrum5

Snippets5

Zaraz3

Bot Management8

Speed5

Web Analytics4

Account6

Zero Trust9

SSL / TLS3

DNS10

R2 Storage5

Zones4

Rules Lists10

AI Gateway13

Images9

Zero Trust Gateway17

Page Shield9

Cache8

Fonts2

Security2

API Shield4

Intel23

Magic Transit12

Calls10

Analytics Engine SQL API9

Log Explorer14

Addressing / BYOIP34

Radar AI11

URL Scanner7

R2 Event Notifications4

Templates using Cloudflare

Cloudflare Alert Triage Agent

+1

Turns a Cloudflare alert into one Slack note that separates an origin problem from an attack, backs it with request and error counts from the zone, and names where to look first. Cloudflare pages you about two completely different emergencies in the same flat voice: your origin has stopped answering, and the internet has turned up all at once. This agent reads the alert, counts how many probe locations still pass, pulls the zone's requests, cache split, 5xx and blocked traffic around the window, then posts one short Slack note saying which of those two you actually have. It cannot change a rule, a record or a certificate, so the note is evidence and the decision stays with your team. ## What people use it for - **Attack or outage, decided fast** - A request spike the edge is absorbing and a 5xx spike with uncached traffic flat are opposite problems with opposite responses. The note answers which one it is from the zone's own numbers, before anybody opens a dashboard. - **Certificates on forgotten hostnames** - Renewal failures land on the subdomains nobody has thought about since 2023. The note carries the expiry date, the days left and how much traffic that hostname still serves, which is what decides between renewing it and retiring it. - **Half the world is fine** - Health checks failing from two probe locations while six pass is a routing problem, not a dead origin. Counting the passing locations takes thirty seconds and almost never gets done at three in the morning. - **Nothing at the edge changes** - No firewall rule written, no security mode toggled, no cache purged, no notification silenced. The worst outcome available to it is a Slack note you disagree with, posted where the people who can act are already reading. ## Before you fork **What does it need from Cloudflare?** An API token that can read zone analytics and health checks on the zones you care about, the notification policies you want pointed at this workflow, and a Slack channel. Nothing it does requires edit permission, so a read only token covers the entire job. Your alert rules go in as a variable when you fork it. **Will every notification we have enabled end up in the channel?** Only the ones you route into this workflow, and then only when your alert rules say that kind is worth posting. Cloudflare's own notification policies remain the first filter, exactly as they are today. Start with one zone and the alert types that currently wake somebody up, then widen once you like what it writes. **Can it block the attack while we are asleep?** No. It cannot write a firewall or rate limiting rule, enable a security mode, or change DNS, and that limit is deliberate. Turning traffic away is a decision about which customers you are willing to lose, and it needs somebody who knows which countries are real revenue. What it does instead is hand that person the country and network breakdown they would otherwise spend ten minutes assembling.

41104 nodes

Frequently asked questions

Use Cloudflare as an AI agent tool

Wire Cloudflare into a coding agent and let it use these operations as tools.

Ready to build with Cloudflare?

Start building workflows in minutes with our visual builder. No code required.

Book Demo
Browse all integrations