BoloForms

BoloForms, through its BoloSign product, sends templates out for signature and collects the responses. Agents fill a template's placeholders from a record, send it to the right signers with roles assigned, and read back who has responded.

4 actions API key available

BoloForms website Platform Documentation Capability data verified 2026-08-13

A work order or agreement reaches the stage that calls for a signature

Agent builds the template's custom variables from the record, with the bracketed names the template expects

List Documents confirms this record has not already been sent, so nobody receives it twice

Each receiver's role title is matched against the mapping the team maintains, because nothing in the connector can check it

The assembled send posts to the operations channel showing every value and every role exactly as it will go out

A person confirms it, and only that confirmation releases Send Template For Signing

What This Integration Enables

BoloForms, through its BoloSign product, does exactly four things, and the shortness of that list is the point. It sends a template to the people who have to sign it, and it reads back what happened. There is no envelope model, no requirement layer, no draft state, and no delete. For a team whose signing process is genuinely simple, that is not a limitation, it is an absence of ceremony: one call sends the agreement, and two calls tell you where everyone stands.

FlowRunner agents fill the template's placeholders from the record that triggered the send, assign each recipient the role the template defines, and sweep the responses afterward so nobody has to open a dashboard to find out who is stalling. What the agent does not do is decide that the send is correct. On a connector with four actions and no way back, the value of human-in-the-loop is not that it slows anything down. It is that this is the only place a mistake can still be caught.

Without FlowRunner

Fields typed per send Someone copies names, emails, and amounts out of a record and into a signing form

Placeholder errors found by the signer An unreplaced placeholder reaches the recipient before anyone notices the name did not match

Follow-up by memory Whoever remembers checks the dashboard for who has not signed yet

With FlowRunner

Fields built from the record Custom variables come from the system that already holds them, assembled the same way every time

Placeholder errors found in review The exact values and role titles are shown to a person while the send can still be stopped

Follow-up as a sweep List Template Respondents surfaces everyone still pending, and the chase names them

Use Case Scenarios

The agreement that fills itself in

A record reaches the signing stage in Airtable or HubSpot. The agent builds the custom variables from the record's own fields, matching the bracketed placeholder names the template uses, and resolves each recipient to the role title that template defines. It assembles the send and posts it for approval rather than dispatching it. Once approved, Send Template For Signing goes out with the signer names, emails, and roles already correct, and nobody retyped a figure that was already sitting in a database.
The same template with a different document

The wording of an addendum changes each quarter, but the layout and the signature field positions do not. Rather than rebuilding the template, the agent renders the new wording elsewhere and passes it as the PDF for the same template, so the field positions still apply. This only works for PDF templates, so the flow checks the template type before it tries. The result is one maintained layout with quarterly content, instead of four near-identical templates that drift apart.
Chasing precisely, and moving the answers on

On a schedule, the agent sweeps List Template Respondents for anyone still pending past the agreed window and posts just those names to the owning manager in Slack, rather than a blanket reminder to a list that includes people who already signed. In parallel, List Form Responses is read as answers arrive, and each response creates or updates the record it belongs to in Google Sheets or the operational system of record. The form stops being a place answers accumulate and becomes a place they pass through.

Human-in-Loop Highlight

Look at what this connector cannot do. There is no cancel, no withdraw, no void, and no delete. Once Send Template For Signing succeeds, every remaining operation is a read. That would matter less if the send were hard to get wrong, but it is not: custom variable names are matched with their square brackets, so a name supplied without them goes out unreplaced with nothing to report the failure, and each receiver's role title has to match what the template defines exactly, or the signature fields land somewhere other than where they belong. Nothing in the connector can check either of those against the template, because no operation reads a template's definition back. So the gate sits in the only place it can. The agent assembles the whole send and posts it: "Service agreement for Northfield Logistics, ready to go to [email protected] as Client Signatory and [email protected] as Company Rep. Variables: [client_name] Northfield Logistics, [monthly_fee] 4,200, [start_date] 1 October. Send?" A person reads the values and the roles and answers. After that call, the only correction available is a phone call to the recipient.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

4 actions

Documents

List Documents Lists the documents in a workspace, with filters for text, date, and status. The check that stops a record being sent for signature twice, and the source of document identifiers for everything downstream.
Send Template For Signing Sends a template to the people who have to sign it. They are emailed as soon as this succeeds, there is no draft state, and no operation in this connector recalls it. This is the call the human gate on this page exists for.

Responses

List Template Respondents Lists who has been sent a template and where each of them has got to, so follow-up names the people who are actually holding things up.
List Form Responses Lists the answers people have submitted to a form, so responses can be read as they arrive and moved into the system that needs them.

Frequently Asked Questions

What can FlowRunner do with BoloForms?

FlowRunner agents can run List Documents, Send Template For Signing, and List Template Respondents in BoloForms, plus 1 more action.

Does connecting BoloForms to FlowRunner require OAuth?

No. BoloForms connects to FlowRunner with an API key, no OAuth flow required.

Can BoloForms trigger a FlowRunner workflow automatically?

BoloForms doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with BoloForms

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us