Resources · Make integration

Betty Blocks Make integrationAutomate Betty Blocks with Make.

Your Betty Blocks records can stay in sync with the rest of your tools without a single export. The Betty Blocks Make integration gives you 7 modules: 6 actions and 1 search. This guide shows how to link your account, build a first scenario and pick the right module for each job.

Try the Betty Blocks integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Betty Blocks Make integration do?

The Betty Blocks Make integration lets a Make scenario (the automation you build, a chain of modules) read and write the records of your Betty Blocks application. Each module is one brick of that chain: here, an action or a search on your data models, run on a schedule or started by another app.

Keep a record current. When a deal changes stage in your CRM, Search Records finds the matching entry and Update a Record writes the new status, so nobody retypes it.

Turn an outside event into app logic. A signed contract or a paid invoice in another tool can call Trigger an Action, which runs an action of your application by its ID. The logic you already built in Betty Blocks does the rest.

Feed a new model from a form. Every form answer becomes a row through Create a Record, ready for the screens of your application.

One thing Make does not offer here: a trigger. Betty Blocks has no module that watches for changes, so your scenario starts from another app or from a schedule. If a listed module falls short, Make an API Call reaches any endpoint of the Betty Blocks API with the same connection. To weigh the two main tools, read n8n vs Make, and check Make pricing before you scale up.

Connect

How do you connect Betty Blocks to Make?

  1. 01

    Copy your API token

    In Betty Blocks, open Settings, go to the User Management tab and click the API button next to the user Make will act as. Copy the API token shown in the window that opens.

  2. 02

    Open the connection window

    In your Make scenario, add any Betty Blocks module and click Create a connection. A connection is your Betty Blocks account linked to Make once, then reused by every Betty Blocks module.

  3. 03

    Name it and paste the credentials

    The Connection name field is optional, but a clear name helps when you run several applications. Paste the credentials you copied from Betty Blocks, or follow the on-screen instructions, then save.

First scenario

Build your first scenario with Betty Blocks

GoalWhen a customer changes status in another app, Make finds the matching Betty Blocks record and updates it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Since Betty Blocks has no trigger, pick the module of the app where the change happens first, your CRM for instance.

  2. 02

    Add Search Records

    Click the + on the right of the first module, search for Betty Blocks and choose Search Records. Click Create a connection if this is your first Betty Blocks module, then pick the data model.

  3. 03

    Map the lookup value

    Fill the search with a value from the first module, such as the customer email. Make passes each item it finds as a bundle, one record per bundle, to the next module.

  4. 04

    Add Update a Record

    Add Update a Record after the search. Map the record ID returned by Search Records, then map the new status from the first module into the matching property.

  5. 05

    Test with Run once

    Click Run once to execute the scenario one time. Open the bubble above each module to read the bundles it received and confirm the right record changed.

  6. 06

    Schedule and switch on

    Open Scheduling on the first module. A new scenario checks every 15 minutes by default. Keep that or change it, then switch the scenario on.

Modules

What can Make do in Betty Blocks?

Betty Blocks gives you 7 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Betty Blocks1

Create a Record

Action

In Make“Creates a record of a specified data model.”

Adds a new entry to a data model of your application, filled with whatever the earlier modules sent. A lead captured on your site shows up in Betty Blocks without anyone typing it.

When to use it
any time a fresh item appears elsewhere and has no match yet in your app.
Watch out
if the item might already exist, run Search Records first, or duplicates will pile up.
Betty Blocks2

Delete a Record

Action

In Make“Removes a record specified by ID.”

Removes one record, identified by its ID, from your application. It keeps a data model clean when the source of truth says an entry should go, like a cancelled booking or a withdrawn applicant.

When to use it
after a search or a get has returned the exact ID to remove.
Watch out
treat a deletion as final: test on a throwaway record with Run once before you switch the scenario on.
Betty Blocks3

Get a Record

Action

In Make“Retrieves a single record of a specified data model by record's ID.”

Reads a single record of a data model when you already hold its ID, and hands its values to the next modules. You get the full picture of one entry, not a list.

When to use it
the ID travels with the event, for example stored in another tool, and you need the latest values before acting.
Watch out
without an ID, this module cannot help; reach for Search Records instead.
Betty Blocks4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Sends a request of your choice to the Betty Blocks API, signed with the connection you already set up. It covers whatever the six other modules leave out.

When to use it
you need an endpoint that no listed module reaches, and you know which one from the Betty Blocks API documentation.
Watch out
you write the path and the body yourself, so keep the Betty Blocks API documentation open while you fill the module.
Betty Blocks5

Trigger an Action

Action

In Make“Executes an action specified by ID.”

Runs an action of your Betty Blocks application, picked by its ID. Instead of rebuilding a process inside Make, you let the logic already living in your app take over from an outside event.

When to use it
a payment, a signature or a form answer elsewhere should start work that your application already knows how to do.
Watch out
the scenario needs the exact action ID, so copy it from your application before you map anything.
Betty Blocks6

Update a Record

Action

In Make“Updates a record specified by ID.”

Changes the values of one existing record, found by its ID, Status fields, owners and dates stay aligned with what happens in your other tools.

When to use it
right after Search Records or Get a Record has given you the ID of the entry that changed.
Watch out
map only the properties you mean to change, then check with Run once that nothing else moved.
Betty Blocks7

Search Records

Search

In Make“Searches for records of a specified data model or lists them all.”

Looks through a data model and returns the records that match, or lists them all. Each result leaves the module as its own bundle, so the next module runs once per record found.

When to use it
you know a customer email or a reference, not the record ID.
Watch out
a search can return zero, one or many records, and each one costs an operation in the modules that follow.
Need help

Need help automating Betty Blocks with Make?

A person reads every message.

FAQ

Betty Blocks and Make: common questions

01Is the Betty Blocks Make integration free?
Yes, on the Make side. Betty Blocks is a standard app, so its 7 modules work on the Free plan. That plan allows 2 active scenarios, a scheduled run every 15 minutes at the shortest, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes per execution. Usage is counted in operations, one per module per bundle. Your Betty Blocks subscription is a separate matter, covered on the Betty Blocks pricing page.
02What do you need to connect Betty Blocks to Make?
You need an active Betty Blocks account with access to the application whose API you plan to use. In Betty Blocks, open Settings, then the User Management tab, click the API button next to the right user and copy the API token. In Make, add a Betty Blocks module, click Create a connection, give it a name if you like and paste the credentials. The connection is then shared by every Betty Blocks module in your scenarios.
03Can Betty Blocks start a Make scenario on its own?
No. The Betty Blocks app in Make has no trigger module, only 6 actions and 1 search. You have two ways to start a scenario anyway. Put a trigger from another app first, such as your CRM or a form tool, so the scenario reacts to what happens there. Or start with a Make schedule: a new scenario checks every 15 minutes by default, and you can then use Search Records to pick up the Betty Blocks entries to process.
04What if a Betty Blocks module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Betty Blocks API through the same connection as the other modules, so nothing new needs to be set up on the account side. You write the path and the request body yourself, based on the Betty Blocks API documentation. The Make documentation for this app flags no specific limit, yet it is partly AI-generated, so confirm important details with Betty Blocks directly before relying on them.
05Should you use Make or n8n for Betty Blocks?
It depends on what you need. In Make, Betty Blocks comes ready with 7 modules covering records and actions, plus Make an API Call for the rest, and it runs on the Free plan. Before choosing n8n, check whether it offers a Betty Blocks node and which operations that node covers, since this page does not document it. Then compare the two on the modules you actually need, and on which tool already runs the rest of your automations.
Same platform

Other docs you might need on this stack.

Browse all integrations