beTool Zapier integrationAutomate beTool with Zapier.
The beTool Zapier integration gives you 4 actions, 0 triggers and 0 searches. So beTool always sits at the end of the chain: another tool starts the Zap, and beTool receives the lead, the new record or the update you send it.
Verified Trustpilot reviews · AI, automation & growth agency
What the beTool Zapier integration actually does
beTool is a CRM where your team organizes work and keeps projects moving. On Zapier, beTool only receives: it can take in a new lead, add or change a record inside one of your processes, and read a record back. It cannot start an automation on its own.
Three results you can get out of it. A lead file that fills itself: someone answers a form elsewhere, and Create Lead Record drops a lead with name and phone into beTool. A process that keeps up with your other tools: an order or a signed quote lands, and Create Record in Process opens the matching record. A record that stays current: Update Record in Process changes a value when something moves on the other side.
What Zapier does not do for beTool: it cannot react to what happens inside beTool. There is no trigger, so a new lead or a changed record in beTool never starts a Zap. There is no search step either, which means a Zap cannot look up a record by name before touching it. To read a record, you need its register token, and Get Record Data by Register Token does that job.
So plan your Zaps from the other side: the starting app decides when things happen, beTool decides where they land. If you work on Make, the beTool Make integration page covers the same app on the other platform.
Zapier vocabulary in one minute
Seven words come back on every Zapier page. Here they are in plain English, once.
- Zap
- The automation you build: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it. beTool offers none.
- Action
- What the Zap does after it starts: the step that writes, sends or changes something for you, here inside beTool.
- Task
- The unit Zapier bills: one action that completes successfully. The number on your plan is a count of those.
- Polling vs instant
- A polling trigger is checked on a timer by Zapier. An instant trigger is reported by the app the moment the event happens.
- Filter
- A step that lets the Zap carry on only when what arrived meets your condition, and stops it quietly otherwise.
- Connection
- Your beTool account linked to Zapier once, then reused by every step of every Zap that touches beTool.
What a beTool Zap really costs
beTool is not a premium app: it works on the free plan. The bill depends on how many beTool actions succeed.
- Free plan100 tasks a month, two-step Zaps only
- Countedeach beTool action that succeeds
- Not countedthe trigger, the checks, failed actions
- Premium appNo, beTool works on the free plan
The trigger costs nothing, and neither does Zapier checking for new data. Each beTool action that succeeds counts as one task; an action that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, but only two steps per Zap: one trigger, one action. Add a filter or a second beTool action and you have a multi-step Zap, which needs a paid plan. A Zap with two beTool actions also counts two tasks per run.
Connect beTool to Zapier in three steps
- 01
Open the Apps page
In Zapier, go to Apps and click + Add connection. You need a beTool account, plus access to any process you do not own but want the Zap to write into.
- 02
Find beTool and add it
Type beTool in the search box of the dialog, pick it, then click Add connection. A new tab opens on the beTool side so you can sign in with the account the Zaps will use.
- 03
Grant access
Sign in to beTool in that tab and allow Zapier to work with the account. From then on, every beTool step in every Zap reuses this one connection, so you set it up once.
Your first Zap: web form answers into beTool leads
GoalEvery form answer that carries a phone number becomes a lead in beTool, with no copy and paste.
- 01
Build: pick the starting app
Since beTool has no trigger, the Zap starts in your form tool, on its new response event. Test it: Zapier brings back the three most recent answers so you map a real one.
- 02
Add the filter
From the plus icon, add Filter. Pick the phone field, the rule that checks it exists, and continue. Phone is required on a beTool lead, so empty answers stop here.
- 03
Add the beTool action
Choose beTool and
Create Lead Record. Paste your Business Unit Id and Token, then map first name, last name and phone from the form answer. - 04
Test, then publish
Run the beTool step once and open the lead it created in beTool. If it looks right, click Publish. The filter makes this a multi-step Zap, so it needs a paid plan.
The 4 beTool actions, grouped by what they do
beTool gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Lead Record
ActionIn Zapier“Create a new lead record.”
Adds a fresh lead to beTool from data that arrived in another tool, ready for your sales follow-up.
Create Record in Process
ActionIn Zapier“Create a record in an existing process.”
Opens a new record inside one of your existing beTool processes, so a step of your workflow starts by itself.
Get Record Data by Register Token
ActionIn Zapier“Get data of a record using its register token.”
Reads back the data of a single beTool record so the next steps of the Zap can reuse it.
Update Record in Process
ActionIn Zapier“Update a record in an existing process.”
Changes a value on a record that already sits in a beTool process, instead of creating a second one.
When a beTool Zap breaks
Most surprises come from Zapier itself, not from beTool.
Zapier attaches no help article and no specific limit to beTool, so the cases below are the general Zapier ones, applied to an app that only receives data. Read them before you switch the Zap on, and keep the Zapier troubleshooting page at hand when a run goes red.
Old leads never show up
A Zap only reacts to what happens after you publish it. Form answers received before that day are not sent to beTool; moving that backlog is a separate job.A required field arrives empty
Phone, Process, Type or Value left blank means the beTool step cannot go through. A filter in front of it keeps those runs out, and a failed action costs no task.A big import gets held back
If the starting app suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold the run instead of pushing everything into beTool.The same item twice? Not on polling
When the starting app uses a polling trigger, Zapier remembers what it has already seen, so one form answer does not create two beTool leads.
Need help automating beTool with Zapier?
A person reads every message.
