Resources · Make integration

BoloForms Make integrationAutomate BoloForms with Make.

Every BoloForms response can start work in your other tools on its own. The BoloForms Make integration gives you 3 modules: 2 triggers that notice new responses and 1 action that sends a form. This guide walks a first-time Make user from connection to a live scenario.

Try the BoloForms integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the BoloForms Make integration do for you?

The BoloForms Make integration links your BoloForms account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a single brick such as a trigger or an action. With it, a new form response or PDF template response can push data elsewhere, and another app can ask BoloForms to send a form.

Responses that reach your CRM. Watch New Form Response picks up each new submission, and the next module in the scenario can copy the answers into the sales tool your team already works in. Nobody retypes a thing.

PDF responses that start the follow-up. Watch New PDF Template Response picks up each new response to one of your PDF templates. That is the moment to alert the account owner or file the record where your team looks for it.

Forms that leave at the right time. Send a Form lets any other app start the conversation: a deal moves forward in your pipeline, and BoloForms sends the matching form without anyone opening it.

Be aware that Make itself warns that its BoloForms documentation is limited, because little public information exists about the app. Expect to discover the module settings inside the editor rather than in a reference page. If you are still choosing a platform, the n8n vs Make comparison lays out the criteria, and the Make pricing page explains what each plan includes. For a hands-on start, see the Make training.

Connect

How do you connect BoloForms to Make?

  1. 01

    Add a BoloForms module

    Open a scenario, search for BoloForms, pick any of its modules, then click Create a connection. A connection is your BoloForms account linked to Make once, and every BoloForms module reuses it afterwards.

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, which helps when several accounts coexist. Then either approve Make on the BoloForms page that opens, or paste the key BoloForms gives you, depending on what the window asks for.

  3. 03

    Save and check

    Click Save. The connection now appears in the module, and the other BoloForms modules will offer it from their dropdown, so you only go through this once per account.

First scenario

Your first scenario with BoloForms

GoalWhen a deal is marked won in your CRM, Make asks BoloForms to send the onboarding form to that client.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the large + to place the first module. This first module will be the app where your won deals appear.

  2. 02

    Set the starting module

    Search for your CRM, pick the module that watches deals, and create its connection. Fill its fields so it only looks at the deals you care about.

  3. 03

    Add Send a Form

    Click the + on the right of the first module, search for BoloForms and choose Send a Form. Connect your account, then map the client details coming from the CRM into the module fields.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received, a bundle being one item passed along, here one deal. Check that the form went to the right person.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set the schedule, which is every 15 minutes by default on a new scenario, then switch the scenario on. From now on it runs without you.

Triggers

BoloForms triggers

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

BoloForms1Watch New Form Response

Watch New Form Response

triggerIn the docs only

This trigger gives you every fresh BoloForms submission as a bundle, so the answers can travel to a spreadsheet, a CRM or a chat channel without a copy and paste.

How it fires
scheduled: Make checks the app on the scenario's schedule, so a response waits until the next check.
When to use it
a lead or intake form whose answers someone on your team must act on.
Watch out
the documentation Make provides for this module is thin, so run it once on a test submission and read the bundle before mapping anything.
BoloForms2Watch New PDF Template Response

Watch New PDF Template Response

triggerIn the docs only

Pick this one when what you track is a response to a PDF template rather than to a regular form: it hands each new response to the next module, ready for filing or a notification.

How it fires
scheduled: Make checks the app on the scenario's schedule, which is every 15 minutes by default and can be as short as 1 minute on paid plans.
When to use it
contracts, waivers or agreements that should reach the account owner once the client fills them in.
Watch out
Make gives no official description of this trigger, so test it on one of your own templates before building the rest of the scenario.
Modules

What the BoloForms modules do

BoloForms gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

BoloForms1

Send a Form

ActionIn the docs only

With Send a Form, another app decides when BoloForms goes out: a new client, a closed deal or a booked call can each send the right form to the right person automatically.

When to use it
after an event in another tool, when you want the recipient to get a form without anyone opening BoloForms.
Watch out
Make publishes no field reference for this module, so check the fields it shows once connected and test with your own address first.
Need help

Need help automating BoloForms with Make?

A person reads every message.

FAQ

BoloForms and Make: common questions

01Is the BoloForms Make integration free?
Yes. BoloForms is a standard app in Make, so its modules are available from the Free plan. That plan allows 2 active scenarios, at least 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) bring the interval down to 1 minute, remove the cap on active scenarios and count usage in operations each month. For reference, an operation simply means one module running once on one bundle.
02What is needed to connect BoloForms to Make?
A BoloForms account and a Make account. Make's documentation lists no specific prerequisite for BoloForms. In the editor you add a BoloForms module, click Create a connection, optionally name it, authorize Make on the BoloForms page or paste the key BoloForms gives you, then save. The connection is then shared by all three BoloForms modules, so you set it up once per account. If the authorization window asks for anything else, follow what it shows.
03Do BoloForms triggers in Make react in real time?
No. Both triggers, Watch New Form Response and Watch New PDF Template Response, are scheduled: Make checks BoloForms on the scenario's schedule instead of being called the moment a response arrives. A new scenario checks every 15 minutes by default. On the Free plan 15 minutes is also the shortest interval, while paid plans can go down to 1 minute. If speed matters, shorten the schedule on the first module.
04What if a BoloForms module is missing in Make?
It depends on what you need. BoloForms has only 3 modules in Make and no Make an API Call module, so anything BoloForms does beyond these 3 modules stays out of reach from Make. Make also warns that its BoloForms documentation is limited. If a step you need is not covered, look at whether another app in your stack can hold that part of the process, or ask the team for help designing a workaround.
05Should BoloForms automations run on Make or n8n?
It depends on the tool your team already uses. On Make, BoloForms offers 2 scheduled triggers and 1 action, with the connection handled in the visual editor, which suits people building their first automations. Before choosing n8n for this app, check whether it has a BoloForms node and which operations that node covers. Pick the platform where the rest of your workflows already live, so every automation stays in one place.
Same platform

Other docs you might need on this stack.

Browse all integrations