Resources · Make integration

Bubble Make integrationAutomate Bubble with Make.

Your Bubble database can talk to the rest of your tools without a line of backend code. The Bubble Make integration gives you 8 modules: 2 triggers, 5 actions and 1 search. This guide shows how to connect your app, what each module is for, and how to build a first working scenario.

Try the Bubble integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Bubble Make integration do for your app?

The Bubble Make integration links the database of your Bubble app to Make, a no-code tool where you build a scenario (the automation itself) out of modules (one brick each: a trigger, an action or a search). Make can watch your Bubble data, write new records, delete old ones and start backend workflows you already built in Bubble.

Onboard every new signup in your other tools. Say you run a SaaS MVP on Bubble. Watch Data Things spots each new record of the User type, and the next module pushes that person to your email platform or CRM. Nobody copies emails by hand anymore.

Feed Bubble from a spreadsheet or a form. A course platform collecting applications elsewhere can let Create/Update a Data Thing write each one straight into Bubble. For a whole batch, Create the Bulk of New Data Things loads many records in a single operation (one run of one module, the unit Make counts on your plan).

Let Bubble call Make when something matters. With Watch Events, your app posts an event, say when a payment clears, and Make reacts at once: the receipt or the team alert leaves without waiting for the next scheduled check.

What it will not do: there is no generic API call module for Bubble in Make, so you work with these 8 modules only. The doc also expects an app on a paid Bubble account (some older accounts already using the API are the exception), with the Data API and the Workflow API switched on.

Bubble also has an n8n node, covered on the Bubble n8n integration page, and the n8n vs Make comparison helps you choose. New to the editor? The Make training starts from zero.

Connect

How do you connect Bubble to Make?

  1. 01

    Open the API tab of your Bubble app

    In Bubble, pick your app, go to Settings then API. Tick Enable Workflow API and backend workflows and Enable Data API, plus the data types you need. Click Generate a new API token and copy the Private key.

  2. 02

    Create the connection in Make

    Add any Bubble module to your scenario and click Create a connection. For Watch Events, click Create a webhook first. In Domain Type, choose Application Domain (the name after id= in your app URL) or Custom Domain.

  3. 03

    Paste the key and pick the environment

    Paste the private key into API Token. Under Environment, choose Development (version-test) or Released (live), then click Save. That connection is your Bubble account linked once to Make, and every Bubble module reuses it.

First scenario

Your first scenario: turn each new form entry into a Bubble record

GoalWhen someone fills in the form you use outside Bubble, Make creates the matching record in your Bubble app.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. Pick the trigger of your form tool first: it is the app that starts this flow.

  2. 02

    Add the Bubble module

    Click the + on the right of that first module, search for Bubble and choose Create/Update a Data Thing. Click Create a connection and follow the three steps above.

  3. 03

    Pick the type and map the answers

    Once connected, Make lists the data types it can read. Choose the one that stores your applicants, then map each answer from the form bundle, the item passed from one module to the next.

  4. 04

    Test with Run once

    Send a test entry through your form, then click Run once. Read the bundles each module received and check that the new record appears in your Bubble app.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module, every 15 minutes by default for a new scenario, then switch the scenario on. Leave the ID empty so every entry creates a fresh record.

Triggers

What can start a Bubble scenario?

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

Bubble1Watch Data Things

Watch Data Things

Scheduled trigger

In Make“Trigger when there is a new data thing of the given type.”

This trigger looks at one data type in your Bubble database and starts the scenario for every new record it finds there. Each new thing becomes a bundle the rest of the flow can use.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, 1 minute at best on a paid plan.
When to use it
new orders, signups or bookings that should reach another tool without any change to your Bubble workflows.
Watch out
it watches for new things only; the doc says nothing about edits, so do not count on it to catch an updated record.
Bubble2Watch Events

Watch Events

Instant trigger

In Make“Triggers when an event is posted from your Bubble application.”

Here your Bubble app does the talking: when it posts an event, Make wakes up and runs the scenario with what the app sent. You decide on the Bubble side which moments deserve an event.

How it fires
instant. The app calls Make through a webhook as soon as it happens, with no waiting for a schedule.
When to use it
a payment confirmed or a form submitted in your app, where the next step should not wait for the next check.
Watch out
in Make you click Create a webhook before Create a connection, and nothing arrives until your app actually posts the event.
Modules

What can Make do inside your Bubble app?

Bubble gives you 6 modules in 2 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Data Things

5 modules
Bubble1

Create the Bulk of New Data Things

Action

In Make“Creates new data things in a single operation. The workflow 'load_data_types' must be defined in your Bubble application. See the documentation.”

Loads a whole batch of new records into Bubble in a single operation instead of one run per record, which keeps your operation count low on big imports.

When to use it
a product catalog or a list of members arriving from a spreadsheet in one go.
Watch out
the doc requires a workflow named load_data_types in your Bubble app, or the module has nothing to call.
Bubble2

Create/Update a Data Thing

Action

In Make“Creates a new data thing of the given type, or updates an existing one. To update a data thing, the unique ID of the data thing must be provided.”

Writes one record of the type you choose. Leave the ID empty and Bubble gets a fresh thing; give it the unique ID of an existing one and Make updates that record in place.

When to use it
a lead captured elsewhere that should appear in your app, or a status to refresh after a payment.
Watch out
forgetting the ID on an update creates a duplicate instead of changing the original.
Bubble3

Delete a Data Thing

Action

In Make“Deletes a data thing.”

Removes one record from your Bubble database. It is the cleanup step at the end of a flow, once the data lives somewhere else or no longer has a reason to exist.

When to use it
a test account to purge, or a draft record that another tool has already turned into a real order.
Watch out
a delete does not come back. Run the scenario with Run once on test data before switching it on.
Bubble4

Search Data Things

Search

In Make“Retrieves a list of data things of the given type.”

Pulls a list of records of one type from your Bubble database, so the next modules can work through them. Each result becomes its own bundle.

When to use it
going through all the bookings stored in your app to send them to a report or a reminder tool.
Watch out
the search can return zero, one or many bundles, and every module after it runs once per bundle, which adds operations fast.
Bubble5

Get a Data Thing

Action

In Make“Returns a data thing of the given type.”

Fetches a single record of a given type, complete, when you already hold its unique ID from an earlier module. You get the full record rather than the few fields that came with the trigger.

When to use it
an event gave you an ID and the next app needs the whole customer profile.
Watch out
no ID, no result. Without an ID, start from Search Data Things, which returns the list of records of that type.

Workflows

1 module
Bubble6

Run a Workflow

Action

In Make“Runs a workflow in your Bubble application.”

Starts a backend workflow you already built in Bubble. Make does not rewrite your app logic, it simply presses the button at the right moment in the scenario.

When to use it
a signed contract in another tool should unlock a premium plan that your Bubble workflow already knows how to grant.
Watch out
Enable Workflow API and backend workflows must be ticked in the API tab of your app, or Make cannot reach the workflow.
Need help

Need help automating Bubble with Make?

A person reads every message.

FAQ

Bubble and Make: common questions

01Is the Bubble Make integration free?
On the Make side, yes. Bubble is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans drop the interval to 1 minute and lift the active scenario limit. On the Bubble side, the doc expects an existing app on a paid Bubble account, with an exception for some older accounts already using the API. Check your Bubble plan before you start.
02What do you need to connect Bubble to Make?
You need access to the Bubble app itself. In its Settings, under the API tab, tick Enable Workflow API and backend workflows and Enable Data API, and check the data types Make should see. Generate a new API token and keep the private key. In Make, you then give the domain type (the application name or your custom domain), paste the key in the API Token field and pick the Development or Released environment. A self-signed certificate field is there too, if your app uses one.
03Does the Bubble trigger in Make fire instantly?
It depends which one you pick. Watch Events is an instant trigger: your Bubble app calls Make through a webhook as soon as it posts the event, so the scenario runs right away. Watch Data Things is a scheduled trigger: Make checks for new records on the scenario's schedule, every 15 minutes by default. On the Free plan 15 minutes is also the minimum; paid plans can check every minute. If speed matters, post an event from Bubble and use Watch Events.
04What if the Bubble module you need is missing in Make?
Start by looking at Run a Workflow. Bubble has no Make an API Call module in Make, so the 8 modules are the full toolbox. A practical route is to build the missing step as a backend workflow inside Bubble, where you control everything, and let Make start it with Run a Workflow. If the need goes beyond what Bubble and these modules cover, another app in Make may handle that part, or the team can look at your case with you.
05Make or n8n for Bubble?
It depends on where the rest of your automations live. Bubble exists on both: in Make you get the 8 modules on this page, from data triggers to workflow runs, and n8n has its own Bubble node. Compare the two module lists against the one flow you want to build first. If your team already runs its scenarios in Make, keeping Bubble there means one place to watch, one set of connections and one history of runs.
Same platform

Other docs you might need on this stack.

Browse all integrations