Resources · Make integration

beTool Make integrationAutomate beTool with Make.

Can Make push new leads and process records into beTool for you? The beTool Make integration offers 5 action modules and no trigger. This guide covers the connection, a first scenario fed by another app, and when to pick each module.

Try the beTool integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the beTool Make integration let you automate?

The beTool Make integration links your beTool account to Make, a visual tool where you build a scenario (the automation itself, a chain of modules). Each of the 5 beTool modules is an action: it writes or reads data in beTool once something else has started the scenario.

Leads that land on their own. Another app catches a sign-up, and Create a Lead Record files it in beTool, so nobody retypes contact details.

Process records kept in step. Create Record in Process opens a record when a request comes in elsewhere, and Update Record in Process changes it later when that request moves forward.

Data pulled back out. Get Record Data by Register Token fetches a record so the next module, in beTool or another app, can reuse its contents.

Know the limits before you start. beTool has no trigger in Make, so a scenario always starts from another app or from a schedule. Make's own documentation for beTool is thin and states that not enough public information exists to describe the app fully. For anything the listed modules miss, Make an API Call is the escape hatch.

If you are still choosing a platform, the n8n vs Make comparison lays out both options, the Make review covers the tool itself, and Make training helps if you want to go further on your own.

Connect

How do you connect beTool to Make?

  1. 01

    Add a beTool module

    In your scenario, add any beTool module, for instance Create a Lead Record. Its settings panel opens, and the first thing it asks for is a connection. Click Create a connection.

  2. 02

    Name the connection

    A connection is your beTool account linked to Make once, then reused by every beTool module. Giving it a clear name is optional, yet it helps later when several accounts or workspaces sit side by side.

  3. 03

    Authorize and save

    Depending on what beTool asks for, either approve access on the beTool page that opens or paste the key beTool gives you. Then click Save, and the module can read and write your data.

First scenario

Build your first scenario with beTool

GoalWhen another app receives a new contact, Make creates a lead record in beTool.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario, and click the + in the middle of the canvas to place the first module.

  2. 02

    Start from the source app

    beTool has no trigger, so the first module belongs to the app where contacts appear, such as your form tool. Connect it and pick where the new entries come from.

  3. 03

    Add Create a Lead Record

    Click the + to the right of that module, search for beTool, pick Create a Lead Record and link your account with Create a connection.

  4. 04

    Map the contact data

    Fill the module fields by picking values from the first module, so each new contact lands in beTool with the details it arrived with.

  5. 05

    Test with Run once

    Click Run once, add a test entry in the source app, then open each module to read the bundle it received (a bundle is one item passing between modules).

  6. 06

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on so it keeps running without you.

Modules

What can the beTool modules do?

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

beTool1

Create Record in Process

ActionIn the docs only

You get a fresh record inside a beTool process without opening beTool, fed straight from the data of an earlier module. As its name says, the record is created within a process, so each run adds one new entry.

When to use it
a request arrives in another app, like a support ticket or a form, and it should start its own record in beTool.
Watch out
every run creates a new record, so test with Run once before switching on to avoid duplicates.
beTool2

Create a Lead Record

ActionIn the docs only

New prospects show up in beTool as leads the moment the scenario runs, with no copy and paste. The module files one lead per bundle, so a list of ten contacts becomes ten leads and ten operations on your plan.

When to use it
contacts are captured elsewhere, in a form, a landing page or a chat tool, and your team follows them up in beTool.
Watch out
Make's documentation says nothing about duplicate checks, so run one test lead first.
beTool3

Get Record Data by Register Token

ActionIn the docs only

This one hands you the content of an existing beTool record so later modules can reuse it. Going by its name, you give it the register token of a record and get that record back as a bundle to map into the next step.

When to use it
a scenario already holds a token, from a previous beTool module or another app, and needs the matching data before acting.
Watch out
without a valid token there is nothing to fetch, so keep that value flowing from an earlier module.
beTool4

Make an API Call

ActionIn the docs only

You reach any endpoint of the beTool API from your scenario, reusing the same connection as the other modules. It covers what the four named modules do not, since Make's documentation for beTool remains limited.

When to use it
you need a beTool operation that has no dedicated module and the beTool API offers it.
Watch out
this module expects you to know the endpoint and its parameters; the other modules spare you that work, so try them first.
beTool5

Update Record in Process

ActionIn the docs only

An existing process record gets refreshed with new values, so beTool reflects what happened in your other tools. Unlike Create Record in Process, it changes a record that is already there instead of adding one.

When to use it
a deal, ticket or order changes status in another app and the matching beTool record must follow.
Watch out
the scenario must know which record to change, so pass it from an earlier module.
Need help

Need help automating beTool with Make?

A person reads every message.

FAQ

beTool and Make: frequently asked questions

01Is the beTool Make integration free?
Yes, beTool is a standard app in Make, so it works 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 (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module per bundle. Your beTool subscription is a separate matter.
02What do you need to connect beTool to Make?
A beTool account and a Make account. Make's documentation lists no specific prerequisite for beTool and gives no dedicated connection steps, so the generic flow applies: add a beTool module, click Create a connection, name it if you like, authorize Make on the beTool page or paste the key beTool gives you, then save. The connection is created once and reused by all 5 beTool modules. If beTool asks for a key, get it from your beTool account before you start.
03Does the beTool Make integration have a real-time trigger?
No. beTool has no trigger module in Make, neither scheduled nor instant. A scenario that uses beTool therefore starts in another way: with a trigger from another app, such as a new form entry or a new message, or with a schedule on the first module, every 15 minutes by default and down to 15 minutes on the Free plan or 1 minute on paid plans. Whichever start you choose, the beTool modules then run in order, one after the other.
04What if a beTool module is missing in Make?
Use Make an API Call. It is one of the 5 beTool modules and lets the scenario call any endpoint of the beTool API with the same connection as the other modules. Make's documentation for beTool is limited and says there is not enough public information about the app to describe it fully, so ask beTool for its API reference when you need an operation the four named modules do not cover.
05Should you use Make or n8n for beTool?
It depends on the tool you already use and how you like to build. On Make, beTool comes with 5 action modules, a guided connection and the Make an API Call module for everything else, all usable from the Free plan. The same app may also be available as an n8n node; check that before deciding. Neither choice is better by default. Pick the platform your team knows, and compare the two side by side if you are starting from scratch.
Same platform

Other docs you might need on this stack.

Browse all integrations