Resources · n8n integration

Cloudflare n8n integrationAutomate Cloudflare with n8n.

Your zone certificates should not live in a folder nobody opens. The Cloudflare n8n integration exposes 4 operations on a single resource, Zone Certificate, so a workflow can list them, read one, upload a new one or remove an old one. Useful when renewals still happen by hand.

Try the Cloudflare integration on n8nSee the 4 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Cloudflare n8n integration actually do?

The Cloudflare n8n integration drives one resource of the Cloudflare API from a workflow: Zone Certificate. Four operations sit behind it, Get Many, Get, Upload and Delete, each scoped to a zone you pick from a dropdown or pass as an ID. The node comes bundled with n8n, so there is nothing to install and nothing extra to pay on the n8n side, whether you run n8n Cloud or a self-hosted instance.

Start with the inventory, because it is the cheapest win. A Schedule Trigger fires every Monday, Get Many pulls the custom certificates of a zone, and the Status filter narrows the list to the ones marked expired or pending. Rows land in Google Sheets for the people who want a table, and a short message goes to Slack for the person on call. Nobody has to remember to open a dashboard.

The second job is the renewal itself. When a new certificate has been issued, Upload sends the leaf certificate and its private key to the right zone in one step. Teams that keep their certificate material in a repository often chain it after a GitHub step, so the workflow reads what was just merged and pushes it without a copy and paste round trip.

Third comes the cleanup that usually gets skipped. Get reads a single certificate by its ID and confirms you are looking at the right one, then Delete removes the superseded entry. Writing the ID and the timestamp of that deletion into Postgres gives you a trail you can query later, which beats reconstructing a history from memory.

Anything outside those 4 operations is not a dead end. The HTTP Request node calls any endpoint of the Cloudflare API and reuses the same credential through predefined authentication, so a workflow can mix dedicated Cloudflare steps with raw calls and keep one token to manage. That is the pattern to reach for as soon as your need leaves the Zone Certificate resource.

One structural point to plan around: this tool has no trigger node in n8n. A Cloudflare workflow always starts somewhere else, usually a Schedule Trigger on a fixed interval, an n8n Webhook (a URL another service calls) or the trigger of another tool in the chain. If you are weighing the platform before building, the n8n review goes into the hosting and cost side in more depth.

Connect

How do you connect Cloudflare to n8n?

  1. 01

    Set up the Cloudflare side first

    Two prerequisites, in this order. Create a Cloudflare account, then add a domain to it. Zone certificates are attached to a zone, and a zone is what adding a domain creates, so an account with no domain gives the node nothing to point at. Do this before touching n8n and the rest of the setup takes a couple of minutes.

  2. 02

    Create an API token

    The Cloudflare node authenticates with an API token, which is the only supported method. Generate it from the Cloudflare dashboard following their token creation flow, then copy the value straight away. A token is shown once, and the fix for a lost one is to issue a new one rather than to hunt for the old value in a browser tab.

  3. 03

    Save the credential in n8n

    In n8n, open the Credentials menu, create a Cloudflare credential and paste the API token into it. A credential is created once and reused across every workflow, so the second and third Cloudflare workflow cost you nothing to connect. Back in the node, the credential shows up in its dropdown and the connection is done.

Actions

What can the Cloudflare node do?

The Cloudflare node exposes 4 operations across 1 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceGetDeleteGet ManyUpload
Zone Certificate✓✓✓✓

Zone Certificate

4 operations
01

Delete a certificate

zoneCertificate.delete

What you see in n8n

Notes & use cases

Removes one custom certificate from a zone. The rest of the zone's certificates stay untouched, and the workflow carries on with whatever comes next.

Key parameters

  • Zone Name or ID: the zone the certificate belongs to, picked from the list n8n loads from your account, or passed as an ID through an expression when an earlier node decides which zone to act on.
  • Certificate ID: the identifier of the certificate itself, not its hostname. Read it with Get Many first so the workflow deletes the entry you meant.
Use cases
once a replacement certificate is in place, clear the superseded one so the zone stops carrying an entry nobody can account for.
02

Get a certificate

zoneCertificate.get

What you see in n8n

Notes & use cases

Reads a single certificate from a zone and returns its record, which the following nodes can then test or log.

Key parameters

  • Zone Name or ID: the zone to read from, chosen in the dropdown or given as an ID by expression.
  • Certificate ID: which certificate to fetch. This is the value Get Many returns for each item, so the natural pattern is a list step feeding a read step.
Use cases
before a delete or a replacement, fetch the record and let an IF node confirm the workflow is about to touch the right certificate rather than its neighbour on the same zone.
03

Get many certificates

zoneCertificate.getMany

What you see in n8n

Notes & use cases

Lists the custom certificates attached to a zone, one item per certificate, which makes it the starting point of most Cloudflare workflows.

Key parameters

  • Zone Name or ID: the zone to inventory.
  • Return All: switched on, n8n walks the API pages and brings back every certificate of the zone. Switched off, Limit caps how many items come out.
  • Status, in Filters: keeps only the certificates in one state, active, expired, deleted or pending.
Use cases
a weekly audit that filters on expired and writes what it finds into a spreadsheet the whole team can read.
04

Upload a certificate

zoneCertificate.upload

What you see in n8n

Notes & use cases

Sends a certificate and its key to a zone, so a renewal ends inside a workflow instead of in a browser tab.

Key parameters

  • Zone Name or ID: the zone receiving the certificate.
  • Certificate Content: the zone's leaf certificate, pasted in or, more often, read from a previous node with an expression.
  • Private Key: the matching key. Since this field is required, an empty value stops the node, which is the behaviour you want here rather than a half-finished upload.
Use cases
push a freshly issued certificate to the zone, then hand the result to the step that records the change.
Need help

Need help automating Cloudflare with n8n?

A person reads every message.

FAQ

Cloudflare and n8n, the usual questions

01Is the Cloudflare integration free in n8n?
Yes on the n8n side. The Cloudflare node ships with n8n, so there is nothing to install and no add-on to buy, and it behaves the same on n8n Cloud, the hosted offer run by n8n, as on an instance you host yourself with Docker or npm. A workflow built on one runs on the other without changes. What a Cloudflare account itself costs is a separate question and depends on your plan there, which is between you and Cloudflare. The only other budget line is the time it takes to create the API token and the credential, which you do once and reuse everywhere.
02What credentials do you need for the Cloudflare node?
An API token, which is the authentication method the Cloudflare node supports. Two things have to exist before it is useful: a Cloudflare account, and a domain added to that account, because the operations here work at zone level. Once the token is generated on the Cloudflare side, you paste it into a Cloudflare credential in the n8n Credentials menu. That credential is then picked from a dropdown by every node that needs it, including the HTTP Request node when it calls the Cloudflare API through predefined authentication. One token, one credential, as many workflows as you want.
03What are the limits of the Cloudflare n8n integration?
The node drives one resource, Zone Certificate, with 4 operations: Get Many, Get, Upload and Delete. Anything your workflow needs beyond those operations goes through the HTTP Request node, which calls any endpoint of the Cloudflare API and reuses the same credential, so you are not blocked and you are not juggling a second token. On the listing side, plan for Return All: leave it off and Limit caps the number of certificates returned, turn it on and n8n follows the API pages until the zone is fully listed. Required fields behave strictly, an empty one stops the node.
04Does Cloudflare trigger a workflow in real time?
No, because this tool has no trigger node in n8n. A Cloudflare workflow starts from another source, and there are three common ones. A Schedule Trigger runs the workflow on a fixed interval, which fits audits and periodic checks of a zone's certificates. An n8n Webhook gives you a URL that a third-party service calls, so another system in your chain decides when the workflow runs. Or the trigger of another tool starts it, for example a message or a repository event that leads to a certificate upload. Pick based on what should decide the timing, a clock or an outside event.
05n8n or Make for Cloudflare?
It depends on four criteria, and they have nothing to do with the Cloudflare operations themselves. Hosting: n8n can run on your own servers with Docker or npm, or on n8n Cloud; Make is hosted only. Data control follows from that, since a self-hosted instance keeps certificate material inside your perimeter. Cost model: Make bills per operation, which you should map against how many certificate checks your workflows will run. Visual logic: both are visual editors, and the choice there is mostly about which one your team reads faster. Try the same small workflow on each and compare.
Same platform

Other docs you might need on this stack.

Browse all integrations