Resources · Make integration

Cloudflare Make integrationAutomate Cloudflare with Make.

Can Make handle your Cloudflare DNS chores for you? The Cloudflare Make integration brings 17 modules: 3 scheduled triggers, 12 actions and 2 searches. Below, you connect your account and build a first scenario, no code needed.

Try the Cloudflare integration on MakeSee the 17 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Cloudflare Make integration do for you?

The Cloudflare Make integration links your Cloudflare account to Make, a visual tool where you build a scenario: a chain of modules that runs on its own. Each module is one brick. It watches your zones, edits a DNS record or lists certificates, so routine domain work happens without anyone opening the dashboard.

A DNS change log. Watch DNS Records spots records that were added or modified in a zone, and Export DNS Records saves the zone as a BIND config file. Chain the two and every edit leaves a snapshot you can file in storage, for example with the AWS S3 Make integration.

A security switch for incidents. When your monitoring tool raises an alert, Change a Zone's Security Level tightens the zone from the same scenario. A second scenario can set it back once the alert is closed.

Client domains set up in one pass. A web agency can go from a signed order to a configured zone: Create a Zone, then Create a DNS Record for each entry, then Change a Zone's SSL Setting.

What Make does not do here: the three triggers are scheduled, so nothing reacts the second a record changes. The certificate modules and Watch User Billings only accept a Global API Key, not an API Token. Anything missing from the list goes through Make an API Call. Cloudflare also has an n8n node, described on the Cloudflare n8n integration page, and n8n vs Make lays out how the two tools differ.

Connect

How do you connect Cloudflare to Make?

  1. 01

    Add a Cloudflare module

    Open your scenario, click the +, type Cloudflare and pick any module. Since no connection exists yet, Make shows a Create a connection button. A connection is your Cloudflare account linked to Make once, then reused by every Cloudflare module.

  2. 02

    Name it and paste your key

    Give the connection a name you will recognize later, such as the client or account it belongs to. Then paste the credential Cloudflare gives you. The module descriptions mention two kinds: an API Token carrying the permission each module asks for, and the Global API Key.

  3. 03

    Save and check

    Click Save. Make takes you back to the module with the connection selected. If a module later refuses to run, compare your token's permissions with the one listed in that module's note below.

First scenario

Your first scenario: give every new zone its default DNS record

GoalWhen a zone is created in Cloudflare, Make adds the DNS record you want on every domain.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario. An empty canvas opens with a large + in the middle, which is where the first module goes.

  2. 02

    Add Watch Zones

    Search for Cloudflare, choose Watch Zones and select your connection. This trigger is scheduled: at each run, Make picks up the zones created or modified since the last check and hands them on, one by one.

  3. 03

    Add Create a DNS Record

    Click the + on the right of the trigger and add Create a DNS Record. Map the zone that comes from Watch Zones, then fill in the record every new domain of yours should get.

  4. 04

    Test with Run once

    Add a test domain in Cloudflare, then click Run once. Each module shows a bubble with the bundles it received (a bundle is one item passing to the next module). Check the record in the new zone.

  5. 05

    Schedule and switch on

    Open the clock on the first module: every 15 minutes by default, the shortest interval on the Free plan. Modified zones come through too, so put List DNS Records in between if duplicates worry you. Then switch it on.

Triggers

What can start a Cloudflare scenario?

3 modules start a scenario when something happens in Cloudflare. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Cloudflare as soon as it happens.

Cloudflare1Watch DNS Records

Watch DNS Records

Scheduled trigger

In Make“Trigger when DNS records of a zone are added or modified. Permission "Zone > DNS > Read" is required for API token authentication.”

Watch DNS Records hands your scenario the records that appeared or changed in one zone since the last check. Edits made by several people turn into data Make can archive, compare or report on.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, so a change shows up at the next run rather than instantly.
When to use it
a shared zone where developers and marketing both touch records and someone needs a copy of each change.
Watch out
with an API Token, the token needs the Zone > DNS > Read permission.
Cloudflare2Watch User Billings

Watch User Billings

Scheduled trigger

In Make“Triggers when the authorized user billed by Cloudflare. This module only works with Global API Key but not API Token.”

This trigger starts a scenario when Cloudflare bills the account behind your connection. Instead of digging through the dashboard, you get each billing item as data you can send to a spreadsheet or an accounting tool.

How it fires
scheduled. Make checks the app on the scenario's schedule, so a new charge arrives at the next run after it happens.
When to use it
finance wants every Cloudflare charge logged next to other supplier costs without anyone forwarding invoices.
Watch out
API Tokens are refused here. It only runs with a connection built on the Global API Key.
Cloudflare3Watch Zones

Watch Zones

Scheduled trigger

In Make“Triggers when zones are created or modified. Permission "Zone > Zone > Read" is required for API token authentication.”

Think of a zone as one domain managed in Cloudflare. Watch Zones notices zones that were created or modified on your account and passes them to the rest of the scenario.

How it fires
scheduled. Make checks the app on the scenario's schedule, not at the moment the zone changes, so a zone added between two runs appears at the next one.
When to use it
an agency that adds client domains by hand and wants the rest of the setup, like default records, to follow.
Watch out
an API Token must carry Zone > Zone > Read for this trigger to read your zones.
Modules

What can Make do in Cloudflare?

Cloudflare gives you 14 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Cloudflare1

Change a Zone's Security Level

Action

In Make“Changes the security level of a zone. Permission "Zone > Zone Settings > Edit" is required for API token authentication.”

Changes the security level applied to one zone, straight from a scenario. Nobody has to log in to the dashboard in the middle of an incident to react.

When to use it
an alert from your monitoring app lands and the zone should tighten up right away.
Watch out
the level stays where you set it, so plan a second scenario that brings it back. With an API Token, grant Zone > Zone Settings > Edit.
Cloudflare2

Change a Zone's SSL Setting

Action

In Make“Changes the SSL setting of a zone. Permission "Zone > Zone Settings > Edit" is required for API token authentication.”

Switches the SSL setting of a zone without a trip to the dashboard. The payoff is consistency: every new domain gets exactly the same choice as the ones before it.

When to use it
right after Create a Zone in an onboarding scenario for a new client site.
Watch out
a token needs Zone > Zone Settings > Edit, the same permission as the security level module. Try the value on a test zone first.
Cloudflare3

Create a Certificate

Action

In Make“Creates an Origin CA certificate. This module only works with Global API Key but not API Token.”

Issues an Origin CA certificate from inside a scenario. The result is passed to the next module, ready to be stored or sent to whoever manages the server.

When to use it
a new origin server is being prepared and you want its certificate produced the same way every single time.
Watch out
API Tokens are rejected by this module. Use a connection built on the Global API Key instead.
Cloudflare4

Create a DNS Record

Action

In Make“Creates a DNS Record of a zone. Permission "Zone > DNS > Edit" is required for API token authentication.”

Adds a new record to a zone, the most common move in any Cloudflare scenario. Each bundle that reaches it can become one record, so a list of subdomains turns into a list of entries.

When to use it
a form or a spreadsheet row requests a new subdomain, and nobody should retype it by hand.
Watch out
Create always adds. To change a record that exists, Patch a DNS Record is the right module. Token permission: Zone > DNS > Edit.
Cloudflare5

Create a Zone

Action

In Make“Creates a new zone by its domain name. Permission "Zone > Zone > Edit" is required for API token authentication.”

Adds a new zone to your Cloudflare account from its domain name alone. It is the first link of any onboarding chain: once the zone exists, the DNS and SSL modules can work on it.

When to use it
a client signs, their domain lands in your CRM, and the zone should be ready before the kickoff call.
Watch out
an API Token needs Zone > Zone > Edit for this one.
Cloudflare6

Delete a DNS Record

Action

In Make“Removes DNS record of a zone by its ID. Permission "Zone > DNS > Edit" is required for API token authentication.”

Removes one record from a zone, identified by its ID. It pairs naturally with List DNS Records, which finds that ID for you.

When to use it
a campaign subdomain is retired and its record should disappear with it.
Watch out
a deleted record does not come back through Make. Export the zone first and test with Run once on a throwaway record. Token permission: Zone > DNS > Edit.
Cloudflare7

Export DNS Records

Action

In Make“Exports DNS records of a zone to a BIND config file. Permission "Zone > DNS > Read" is required for API token authentication.”

Produces a BIND config file with the records of a zone. That file is a readable snapshot you can archive, compare with an older one or load into another zone.

When to use it
before a risky change, or as the second step of a scenario that archives the zone after each edit.
Watch out
add a storage module after it so the file lands somewhere you can find it. Read access is enough: Zone > DNS > Read.
Cloudflare8

Import DNS Records

Action

In Make“Imports DNS Records of a zone from a BIND config file. Permission "Zone > DNS > Edit" is required for API token authentication.”

Loads records into a zone from a BIND config file. It mirrors Export DNS Records and spares you one Create a DNS Record per entry when a whole set has to move.

When to use it
migrating a domain from another DNS host that hands you a BIND export.
Watch out
this writes to the zone, so a token needs Zone > DNS > Edit. Try it on a test zone before a live one.
Cloudflare9

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call sends any request you want to the Cloudflare API, using the connection you already set up. It covers whatever the listed modules leave out.

When to use it
you found the Cloudflare endpoint you need in the API reference and no dedicated module exists for it.
Watch out
you build the request yourself, so this is the one module where keeping Cloudflare's API reference open is part of the job.
Cloudflare10

Patch a DNS Record

Action

In Make“Patches DNS Record of a zone by its ID. Permission "Zone > DNS > Edit" is required for API token authentication.”

Updates an existing record, found by its ID, without recreating it. Pointing a subdomain at a new server becomes a single module in your scenario.

When to use it
a server moves and its address has to follow in Cloudflare when your deployment tool reports the switch.
Watch out
you need the record ID, and List DNS Records helps you find it. Token permission: Zone > DNS > Edit.
Cloudflare11

Revoke a Certificate

Action

In Make“Revokes existing Origin CA certificate by its ID. This module only works with Global API Key but not API Token.”

Revokes an Origin CA certificate by its ID. It closes the loop on certificates you created with Make or by hand in the dashboard.

When to use it
a server is decommissioned and its certificate should go away with it.
Watch out
this module works with the Global API Key only. Find the ID first with List Certificates.
Cloudflare12

Turn a Zone into Development Mode

Action

In Make“Modifies development mode setting of a zone. Permission "Zone > Zone Settings > Edit" is required for API token authentication.”

Switches development mode on or off for a zone from a scenario, so the people working on the site do not need dashboard access to flip it.

When to use it
a redesign goes to staging, the task moves to In progress in your project tool, and the zone follows.
Watch out
plan the reverse step for when work ends, or the setting stays as you left it. Token permission: Zone > Zone Settings > Edit.
Cloudflare13

List Certificates

Search

In Make“Lists Origin CA certificates of a zone. This module only works with Global API Key but not API Token.”

Returns the Origin CA certificates of a zone. Like any search module, it can send back zero, one or several bundles.

When to use it
an inventory before a clean-up, or fetching the ID that Revoke a Certificate asks for.
Watch out
it only works with the Global API Key. An empty result is normal for a zone without certificates, so decide what the scenario does then.
Cloudflare14

List DNS Records

Search

In Make“Searches DNS Records of a zone by criteria. Permission "Zone > DNS > Read" is required for API token authentication.”

Searches the records of a zone with the criteria you set and returns what matches. It is how a scenario finds the ID that Patch or Delete needs.

When to use it
checking whether a subdomain already exists before creating it, to avoid duplicates.
Watch out
the answer can hold zero, one or several records, so decide what the next module does in each case. Token permission: Zone > DNS > Read.
Need help

Need help automating Cloudflare with Make?

A person reads every message.

FAQ

Cloudflare and Make: common questions

01Is the Cloudflare Make integration free?
Yes. Cloudflare is a standard app in Make, so it works from the Free plan. That plan gives you 2 active scenarios, at least 15 minutes between scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Each module run on one bundle counts as one operation, and operations are what your plan measures. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Your Cloudflare subscription is a separate matter.
02What do you need to connect Cloudflare to Make?
A Cloudflare account and a credential to paste into Make. The module descriptions mention two: an API Token, which must carry the permission each module asks for, such as Zone > DNS > Edit to write records, and the Global API Key. Four modules accept only the Global API Key: the three certificate modules and Watch User Billings. Every other module works with a token. You create the connection once from the first module, and every Cloudflare module in your scenarios reuses it.
03Do Cloudflare triggers in Make react in real time?
No. All three Cloudflare triggers are scheduled: Make checks your account each time the scenario runs. A new scenario runs every 15 minutes by default, which is the shortest interval on the Free plan, while paid plans go down to 1 minute. A DNS change or a new zone therefore shows up at the next run, not the second it happens. Make has no instant trigger for Cloudflare. If you need a faster reaction, lower the interval on a paid plan.
04What if the Cloudflare module you need is missing?
Use Make an API Call. It reaches any endpoint of the Cloudflare API with the same connection, so whatever the 17 modules do not cover stays within reach. You write the request yourself, based on Cloudflare's API reference. The Make documentation for this app lists no numeric limits, so the only caps to plan around are those of your Make plan. If a module fails, check the token permission or the Global API Key requirement before anything else.
05Make or n8n for Cloudflare?
It depends on where the rest of your automations live. Make offers 17 Cloudflare modules, including 3 scheduled triggers and Make an API Call, and runs from its Free plan with 2 active scenarios. n8n also has a Cloudflare node, covered on its own page on this site. Neither tool is ranked here. Compare the modules you actually need on both sides, then keep Cloudflare in the tool where your other scenarios already run, so one team maintains one place.
Same platform

Other docs you might need on this stack.

Browse all integrations