[Beta] 100+ Cloudflare nodes for n8n, full infra stuff baked in (dynamic dropdowns, workers, DNS, security, etc)

This is a large community node pack for n8n that hooks directly into Cloudflare — not just the usual shallow CF stuff most integrations stop at.

It’s big enough that the n8n UI actually struggles with the number of nodes implemented, i also changed my mind and reduced the numbers by merging some nodes in front (side-lists).

Repo:
Automations-Project/n8n-nodes-cloudflare — The most comprehensive Cloudflare integration for n8n

What’s included

You get 100+ nodes covering pretty much the entire Cloudflare product surface:

  • Workers
  • R2
  • D1
  • KV
  • DNS
  • Cache purge
  • SSL
  • Zero Trust
  • WAF
  • Bots
  • Tunnels
  • Stream
  • Images
  • Analytics
  • Radar
  • GraphQL
  • …and more

This isn’t a “hit 2 endpoints and call it a day” integration.

Why it doesn’t suck

Most Cloudflare nodes hardcode fields and make you paste IDs everywhere. This doesn’t.

  • Dynamic dropdowns for accounts, zones, workers, KV namespaces, etc.
  • Resources auto-load from your Cloudflare account
  • No copy-pasting IDs
  • Far fewer config footguns

BTW: You can open issue/feature in repo if there’s any node you want to have ‘x’ dropdown field for it; we believe didn’t cover all string fields to be dropdown.

Goal

Full infra-automation inside n8n.

  • Deploy Workers
  • Manage security rules
  • Update DNS
  • Pull analytics
  • Orchestrate Cloudflare infra from a single workflow

It’s still beta , but already very usable. I’m actively waiting for bug reports and issues to squash fast.

TBH I also published it early to lock down the
n8n-nodes-cloudflare name :folded_hands: i believe we deserve it because we want to give Cloudflare something special for the years they provide to us Free Users Community.

Important note

We already got confirmation from the n8n team that this node will not be accepted on n8n Cloud.

Because of that, it’s built on top of the official Cloudflare TypeScript SDK , not brittle hardcoded endpoints - which should mean significantly fewer errors over time compared to other community nodes. plus since it is not official, we plan to release with them a special node replacing “n8n imap node” with "Cloudflare MailHook " i believe once this one done you will have another reason to use this node package; however it is not released yet but it’s on to-do.

Repo (again):

NPM:
n8n-nodes-cloudflare - npm

Issues/Feature requests:
Issues · Automations-Project/n8n-nodes-cloudflare

3 Likes

115 Nodes, Wowie, Can’t wait to test this out!

1 Like