Skip to main content

Make Waves ’26 Step into AI’s glass box. Prague, 19–20 Oct.

Register now (opens in a new tab)
Cloudflare
Facebook Lead Ads

Connect Cloudflare and Facebook Lead Ads

Explore ready-made Cloudflare and Facebook Lead Ads templates and start automating in minutes.

Get started free

Create a custom workflow

Integrate Cloudflare with Facebook Lead Ads and automate the work that moves between them — no code required.

Create a custom workflow

Every automation starts with a trigger and an action. Select one from each app to generate a workflow tailored to your needs.

Cloudflare
Trigger: Watch DNS Records
Facebook Lead Ads
Action: Select an action
1. Select a trigger

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

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

  • Triggers when zones are created or modified. Permission "Zone > Zone > Read" is required for API token authentication.

2. Select an action

  • Returns information about the form.

  • Returns the information that the user filled in, in the lead generation form. Use this action after the New Lead trigger.

  • The action unsubscribes a selected page from the connection to Make.

Select a trigger and an action

Create workflow (opens in a new tab)

Triggers and actions

Explore what you can automate between Cloudflare and Facebook Lead Ads.

Change a Zone's Security Level
Changes the security level of a zone. Permission "Zone > Zone Settings > Edit" is required for API token authentication.
Action
Change a Zone's SSL Setting
Changes the SSL setting of a zone. Permission "Zone > Zone Settings > Edit" is required for API token authentication.
Action
Create a Certificate
Creates an Origin CA certificate. This module only works with Global API Key but not API Token.
Action
Create a DNS Record
Creates a DNS Record of a zone. Permission "Zone > DNS > Edit" is required for API token authentication.
Action
Create a Zone
Creates a new zone by its domain name. Permission "Zone > Zone > Edit" is required for API token authentication.
Action
Delete a DNS Record
Removes DNS record of a zone by its ID. Permission "Zone > DNS > Edit" is required for API token authentication.
Action
Export DNS Records
Exports DNS records of a zone to a BIND config file. Permission "Zone > DNS > Read" is required for API token authentication.
Action
Get a Form
Returns information about the form.
Action
Get Lead Details
Returns the information that the user filled in, in the lead generation form. Use this action after the New Lead trigger.
Action
Load more

Support

FAQs

Everything you need to know about Make. Can't find the answer you're looking for? Please chat to our team.

Start by registering for Make. As a new Make user, you’ll automatically be assigned a free account. Once your account is set up, you can start creating your first scenarios. We recommend starting with our step-by-step video tutorial.

A scenario represents a workflow or a project of your own creation, and it is made up of a series of modules that automate apps and services. Creating a scenario allows you to transfer and transform data between apps and services via these modules to automate anything and improve the way you work.

Modules are the main building blocks of automation in Make. Modules represent actions that Make performs with an app, like creating, updating, or deleting data.

Mapping links the modules in your scenario. When you map an item, you connect the data retrieved by one module to another module to perform the desired action. For example, you can map email addresses and subject lines to create a spreadsheet using this data.