BoloForms Zapier integrationAutomate BoloForms with Zapier.
The BoloForms Zapier integration gives you 3 triggers, all instant, and 2 actions. Forms, signatures and templates start your Zaps the moment they happen, and Zapier can send a form or a template out for signature on its own.
Verified Trustpilot reviews · AI, automation & growth agency
What the BoloForms Zapier integration actually does
Zapier is a tool that links your apps so one event in an app sets off work in another, with nobody copying anything by hand. With BoloForms, that means three moments (a form answered, a template answered, a document signed by everyone) can each start an automation, and two jobs (sending a form, sending a template for signature) can be done for you.
Three results you can get out of it, each tied to a real operation:
A contract that leaves on its own. A prospect answers your intake form, New Form Response picks it up, and Send Templates for Signature sends your agreement template, with variables filled in from the answers.
A signed deal that kicks off the next step. New Signature Completed fires only once every signer is done, so it is a clean starting point for whatever comes after the signature.
A follow-up form nobody has to remember. Send Form mails a chosen form to an address, for example right after a template response comes in.
What Zapier does not do here: it offers no search for BoloForms, so a Zap cannot look up an existing form response or a past signature. It also only reacts to what happens after the Zap is switched on. If you want to compare the same building blocks elsewhere, the BoloForms Make integration covers the Make side.
Zapier vocabulary in one minute
Seven words come back on every line of this page. Here they are in plain English.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time that trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it, here a new BoloForms response or signature.
- Action
- What the Zap does once it has started: the step that sends, writes or moves something for you, such as sending a form.
- Task
- The unit Zapier bills. One action that completes successfully is one task, and your plan is a monthly count of those.
- Polling vs instant
- A polling trigger is checked on a timer. An instant trigger is reported by the app itself the moment it happens. All three BoloForms triggers are instant.
- Filter
- A step that lets the Zap carry on only when what arrived meets your condition, and stops it quietly otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action or a filter makes it one, and it then needs a paid plan.
What a BoloForms Zap really costs
BoloForms is not a premium app, so it works on the free plan. The bill is counted in tasks, not in Zaps.
- Free plan100 tasks a month
- Zaps on the free planUnlimited, two steps each
- BoloForms triggersInstant, no waiting on any plan
The trigger never costs a task, and waiting for new data is free too. Each action that succeeds counts as one task, and an action that fails is not counted. A Zap with a filter, or with two actions, is a multi-step Zap: the free plan stops at one trigger and one action, so the hero Zap above needs a paid plan. A Zap of BoloForms trigger plus Send Form, with no filter, stays inside the free plan from day one.
Connect BoloForms to Zapier in three steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. A connection is your BoloForms account linked to Zapier once, then reused by every Zap that needs it.
- 02
Find BoloForms and add it
Type BoloForms in the search box of the dialog, pick it, then click Add connection. You need an existing BoloForms account; Zapier does not create one for you.
- 03
Sign in and grant access
Sign in to BoloForms in the tab that opens, then allow Zapier to reach the account. Use the workspace that holds your forms and templates, since every operation reads from it.
Your first Zap: an accepted quote turns into a signature request
GoalWhen a client answers your quote form and accepts, BoloForms sends the agreement template out for signature.
- 01
Build: pick the trigger
Create a Zap, choose BoloForms as the app and New Form Response as the event. Pick your quote form in the required form field, then select your connection.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent responses of that form, so you map the next steps on a real one instead of guessing what a response looks like.
- 03
Add the filter
Add a Filter step, choose the answer that holds the client decision, a text rule, and the value that means yes. Only accepted quotes go further. This step makes the Zap multi-step.
- 04
Add the signature action
Add BoloForms again with Send Templates for Signature. Choose your agreement template and map answers from the response, such as the client name, into the template variables.
- 05
Test, then publish
Test the action once, on a response you sent yourself, and check the signature request went out as expected. Then click Publish: the Zap is on and reacts to the next response.
BoloForms triggers on Zapier
3 events start a Zap when something happens in BoloForms, and 3 of them are instant: the app calls Zapier straight away, whatever your plan.
New Form Response
Instant triggerIn Zapier“Triggers when a new form response is filled.”
Starts your Zap each time someone fills in one of your BoloForms forms, with the answers ready to pass on to the next step.
New Signature Completed
Instant triggerIn Zapier“Triggers when a PDF document is signed by all.”
Fires when a PDF signature document has been signed by everyone on it, not at the first signature. It is the signal that a deal is truly closed.
New Template Response
Instant triggerIn Zapier“Triggers when a new form template response is filled.”
Goes off when someone answers one of your form templates, the reusable signature templates kept in your BoloForms workspace.
BoloForms actions on Zapier
BoloForms gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Send Templates for Signature
ActionIn Zapier“Use this action to send a template for signature, you can also send variables as well.”
Sends one of your BoloForms templates out for signature, and lets you pass variables so names or amounts land in the right place.
Send Form
ActionIn Zapier“Use this action to send your form to someone”
Mails one of your forms to the address you give it, so the recipient can fill it in without you sending anything by hand.
When a BoloForms Zap breaks
Zapier lists no BoloForms-specific error or rate limit. What goes wrong comes from how Zaps work in general.
Four cases are worth knowing before you switch anything on. If a run fails and you cannot see why, the Zapier troubleshooting page is the next stop.
Old responses are ignored
A Zap only reacts to what happens after you publish it. Responses and signatures that already existed are never picked up; moving that backlog is a separate job.A Zap that keeps setting itself off
If a Zap sends a form whose responses feed the trigger of that same Zap, it can loop and burn through your task count fast. Keep the form you watch and the form you send apart.A sudden wave held back
When a trigger suddenly returns a huge batch, after a bulk import for instance, Zapier's flood protection can hold the runs back instead of letting them all through.A failed send costs nothing
If Send Form or Send Templates for Signature fails, for example on a missing email, no task is counted. Fix the mapping before the next response comes in.
Need help automating BoloForms with Zapier?
A person reads every message.
