Resources · Make integration

Unbounce Make integrationAutomate Unbounce with Make.

Every Unbounce form submission can start an automation on its own. The Unbounce Make integration gives you 19 modules: 1 instant trigger, 7 actions and 11 searches. This guide is for marketers who run landing pages, from the connection to a first live scenario.

Try the Unbounce integration on Make See the 19 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Unbounce Make integration let you automate?

The Unbounce Make integration links your Unbounce account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules. Each module is one brick. Here you get a trigger that reacts to forms, plus actions and searches that read your accounts, pages and leads. You pick the bricks, Make runs them.

New leads land in your tools right away. Watch Form Submissions fires as soon as a visitor sends a form, and the next module passes that lead to your CRM, a chat channel or an Airtable base (the Airtable Make integration shows that side).

A clean inventory of your landing pages. List Pages, List Domain Pages and List Pages in Page Group return your pages as bundles, one bundle per page, ready to write into a report that stays current.

Visibility across clients. If you manage clients in sub-accounts, List Sub-Accounts and List Sub-Account Pages show what lives where, without clicking through each workspace.

What Make does not give you is complete documentation. Make states that public information on Unbounce is too thin for a full guide, so this page sticks to what the module catalog shows. To weigh tools first, read n8n vs Make; for a guided start, look at the Make training.

Connect

How do you connect your Unbounce account to Make?

01
Add an Unbounce module
Open your scenario, click the + and search for Unbounce. Pick any module, Watch Form Submissions for example, then click Create a connection. A connection is your Unbounce account linked to Make once, and every Unbounce module reuses it.
02
Name the connection
Give it a name you will recognize later, like the client or the account it belongs to. The name is optional, but it saves confusion once you juggle several Unbounce accounts in the same Make workspace.
03
Authorize Make and save
A window opens: sign in to Unbounce and authorize Make, or paste the key Unbounce gives you if that is what the window asks for. Click Save, and your modules can now read accounts, pages and leads.

First scenario

Your first scenario: find out which page produced each lead

GoalWhen a visitor submits a form on an Unbounce page, Make fetches that page so you know where the lead came from.

01
Create the scenario
On the Scenarios page, create a new scenario and click the + in the middle of the editor. This first slot holds the module that starts everything else.
02
Add the form trigger
Search for Unbounce, pick Watch Form Submissions and select your connection. It is an instant trigger: Unbounce calls Make through a webhook as soon as a form is sent.
03
Add Get Page
Click the + on the right of the trigger and add Get Page. Choose the page from the list Make shows, or map it from the trigger's data if your test shows the bundle carries it.
04
Test with Run once
Click Run once, then submit a test form on your Unbounce page. Read the bundles each module received and check that the lead and the page match what you sent.
05
Switch it on
With one more +, add the tool that should receive the lead, then switch the scenario on. Each new submission starts it, and every module run counts as one operation on your plan.

Triggers

What starts an Unbounce scenario?

1 module starts a scenario when something happens in Unbounce. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Unbounce as soon as it happens.

Unbounce1Watch Form Submissions

Watch Form Submissions

Instant trigger

In Make“Triggers when new form is submitted.”

You get every new Unbounce form submission handed to Make the moment it happens, so a lead never sits in a dashboard waiting for someone to export it. It is the only trigger of the app, and the one most Unbounce scenarios start with.

How it fires

instant: Unbounce calls Make through a webhook as soon as a form is submitted, with no polling interval to wait for.

When to use it

a demo request page where sales wants each new contact in the CRM while the prospect still remembers filling it in.

Watch out

Make's documentation for Unbounce is limited, so run one real submission with Run once before you trust your mapping.

Modules

What can each Unbounce module do?

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

Unbounce1

Delete Page Lead

Action

In Make“Deletes a single Lead. Only available to the account owner.”

A lead you no longer want disappears from Unbounce, removed straight from your scenario instead of by hand. Keep in mind that a delete cannot be taken back.

When to use it

a contact asks to have their data erased, and your scenario carries out the request in Unbounce too.

Watch out

only the account owner can run it, so the connection has to belong to that owner.

Unbounce2

Get Account

Action

In Make“Retrieves the details of a single account.”

The details of one Unbounce account come back as a single bundle, handy when a later module needs to know which account it is working in.

When to use it

you run several accounts and want each report or alert to carry the account it came from.

Watch out

it reads one account you already know; to discover the accounts your connection can reach, start with List Accounts.

Unbounce3

Get Domain

Action

In Make“Retrieves a custom domain that has been registered with Unbounce.”

One custom domain registered with Unbounce is returned with its details, so your scenario knows exactly which domain it is dealing with.

When to use it

before sharing a list of pages per domain, you want the domain's own record sitting next to them.

Watch out

it handles a single domain; when you need every domain of a sub-account, List Sub-Account Domains fits better.

Unbounce4

Get Page

Action

In Make“Retrieves a single page.”

Everything Unbounce holds about one landing page arrives in a single bundle you can map into the next module. Think of it as the page's ID card inside your scenario.

When to use it

a lead arrives and you want to know which page converted before you log it anywhere.

Watch out

it needs one precise page; to browse many at once, pick one of the List modules instead.

Unbounce5

Get Page Lead

Action

In Make“Gets info of single Lead.”

The full record of one lead is pulled back from Unbounce whenever your scenario needs to look at it again, so you re-read the source instead of trusting an old copy.

When to use it

a sales rep flags a contact, and the scenario fetches that lead's info to attach it to a follow-up task.

Watch out

it targets a single lead; to pull every lead of a page, List Page Leads does the job.

Unbounce6

Get Sub-Account

Action

In Make“Retrieves the details of a single sub-account.”

In one step, the details of a sub-account land in your scenario, which helps when your Unbounce setup keeps brands or clients apart. You read one sub-account, identified beforehand.

When to use it

an agency scenario labels each alert with the client sub-account it concerns.

Watch out

to find out which sub-accounts exist, run List Sub-Accounts first and feed its result here.

Unbounce7

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Any endpoint of the Unbounce API becomes reachable from Make, even when no listed module covers it, and the call reuses the connection you already created.

When to use it

you need an Unbounce feature that none of the other modules offers, and you know which endpoint handles it.

Watch out

you shape the request yourself, which asks for more care than a ready-made module; test it with Run once and read the bundle it returns.

Unbounce8

List Account Pages

In Make“Retrieves a list of all pages for the specified account.”

Every page of a given account shows up as its own bundle, so the whole catalog of that account flows through your scenario in one pass. Like any search, it can return zero, one or many results.

When to use it

you build an inventory of one account's pages in a sheet the marketing team can read.

Watch out

each page returned runs the next modules once, and every one of those runs counts as an operation.

Unbounce9

List Accounts

In Make“Retrieves the accounts collection.”

You see which Unbounce accounts your connection can reach, each one as a bundle. It is the usual starting point before a Get Account or List Account Pages step.

When to use it

a scenario goes through all your accounts to compile one overview of what you manage.

Watch out

with a single account you rarely need it; pick that account directly in the next module.

Unbounce10

List Domain Pages

In Make“Retrieves a list of all pages based on the domain.”

All the pages published under one domain come back together, so a site-by-site view takes one module instead of a manual sort in Unbounce.

When to use it

you plan to retire a domain and want the list of pages it still serves before you touch anything.

Watch out

the list shows pages only; add Get Domain when you also need the domain's own details.

Unbounce11

List Page Form Fields

In Make“Retrieves a full list of all form fields across all page variants of a specific page.”

You get the full map of form fields on a page, across every variant of it, which tells you what a submission can carry before you map anything.

When to use it

before sending submissions to your CRM, you check which fields exist so no answer gets lost on the way.

Watch out

one variant can hold fields the others lack, so read the whole list rather than the first bundles.

Unbounce12

List Page Leads

In Make“Retrieves a list of all leads for a given page.”

Every lead a given page has collected comes back as bundles you can send to a sheet or a CRM in one go. It covers the history, where Watch Form Submissions only sees new ones.

When to use it

you connect Make after the campaign started and want the leads already captured too.

Watch out

a busy page means many bundles, and every later module runs once per lead.

Unbounce13

List Pages

In Make“Retrieves a list of all pages for the specified account.”

Your pages for the account you choose arrive as a list you can filter and pass along to the next module. Make describes it in the same words as List Account Pages.

When to use it

you want a quick list of pages to check which ones a campaign relies on.

Watch out

since both descriptions match, test the two modules on your account and keep the one whose output suits your scenario.

Unbounce14

List Pages in Page Group

In Make“Retrieves a list of all pages that belong to a given page group.”

The pages filed under one page group come back together, which spares you the sorting when your groups mirror campaigns or clients.

When to use it

a product launch lives in its own group and you want a status sheet of just those pages.

Watch out

you need the group first; List Sub-Account Page Groups gives you the groups to choose from.

Unbounce15

List Sub-Account Domains

In Make“Retrieves a list of all custom domains belonging to a given sub-account.”

Each custom domain attached to a sub-account appears as a separate bundle, a fast way to know which domains a client uses without asking them.

When to use it

while onboarding a new client, you document their domains in a shared sheet for the team.

Watch out

it covers one sub-account per run; start from List Sub-Accounts to go through all of them.

Unbounce16

List Sub-Account Page Groups

In Make“Retrieves a list of all page groups for a given sub-account.”

A sub-account's page groups are laid out for you, so you can see how its pages are organized before digging deeper.

When to use it

before building a report per campaign, you need the group names to pick from.

Watch out

it returns groups, not pages; chain List Pages in Page Group to reach the pages inside each one.

Unbounce17

List Sub-Account Pages

In Make“Retrieves a list of all pages for a given sub-account.”

All the pages of a single sub-account show up in one list, which is ideal when each client lives in their own sub-account.

When to use it

a client asks what is live on their side, and the scenario writes the answer into a sheet you can share.

Watch out

unlike List Account Pages, it stays inside the sub-account you pick, so double-check that choice before running it.

Unbounce18

List Sub-Accounts

In Make“Retrieves all sub-accounts for the specified account.”

Your sub-accounts come back one bundle each, the natural first step of any scenario that has to walk through every client.

When to use it

you loop over all sub-accounts to gather their pages or domains into one report.

Watch out

a search can return zero results, so check the output with Run once before relying on the modules that follow.

Need help

Need help automating Unbounce with Make?

A person reads every message.

FAQ

Unbounce and Make: common questions

01Is the Unbounce Make integration free?

Yes, Unbounce is a standard app in Make, so you can use it on the Free plan. That plan lets you keep 2 active scenarios, with at least 15 minutes between two scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, lift the cap on active scenarios and allow 40 minutes per run. Make counts usage in credits, one operation per module run. Your Unbounce subscription is a separate matter.

02What do you need to connect Unbounce to Make?

Just an Unbounce account and a Make account; Make's documentation lists no other prerequisite. Add any Unbounce module, click Create a connection, name it if you like, then authorize Make on the Unbounce page or paste the key it provides, and click Save. One detail matters: Delete Page Lead only works for the account owner, so if deleting leads is part of the plan, connect with the owner's login. Every other Unbounce module then reuses that same connection.

03Does the Unbounce trigger in Make work in real time?

Yes. Watch Form Submissions is an instant trigger: Unbounce calls Make through a webhook as soon as a visitor submits a form, so the scenario starts right away instead of waiting for an interval. The 7 actions and 11 searches never start a scenario on their own. If you want a regular sweep instead, for example to pull the leads of a page, put List Page Leads first and set its schedule; a new scenario runs every 15 minutes by default.

04What if an Unbounce module is missing in Make?

Make an API Call fills the gap. It reaches any endpoint of the Unbounce API with the connection you already have, so it covers what the 19 listed modules leave out. Keep in mind that Make calls its Unbounce documentation limited, because public information about the app is thin: test each request with Run once and read the bundles it returns. If the need sits outside Unbounce entirely, add a module from another app with the + after your Unbounce step.

05Should you use Make or n8n for Unbounce?

It depends on your criteria rather than on a winner. On Make, Unbounce comes with 19 ready modules, including an instant form trigger, inside a visual editor where you test with Run once. n8n often has a node for the same app, so check whether Unbounce is covered there before you decide. Weigh what matters to your team: the modules you actually need, the way you like to test, and the tool your colleagues already use.

Add an Unbounce module

Name the connection

Authorize Make and save

Create the scenario

Add the form trigger

Add Get Page

Test with Run once

Switch it on

Need help automating Unbounce with Make?