BoloForms MCP integration for AI agents.
Connect AI agents to BoloForms through 4 structured actions, including get form responses, send template for signing, and list documents. Review authenticati…
- ACTION CONTRACTS
- 4
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the BoloForms integration exposes
The BoloForms Agent App exposes 4 provider-backed actions for productivity work. Its current contract lets an authorized agent list response records for a specific form so they can be used in follow-up automations, start a signing request for a group of participants by using an existing template, and list documents and form statistics from the current boloforms workspace. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected BoloForms account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real BoloForms capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_form_responsesREADList response records for a specific form so they can be used in follow-up automations.
INPUTS: formId / page / limit
send_template_for_signingWRITEStart a signing request for a group of participants by using an existing template.
INPUTS: documentId / signingType / mailSubject / mailMessage / signers
list_documentsREADList documents and form statistics from the current BoloForms workspace.
INPUTS: workspaceId / query / documentId / filter / sortBy
list_template_respondentsREADList the current signing participants and their statuses for a specific template.
INPUTS: templateId / page / limit
INPUT CONTRACTS
Know what the action needs before it runs.
get_form_responses
formIdREQUIRED- The form ID.
pageOPTIONAL- The page number, starting from 1.
limitOPTIONAL- The number of items to return per page.
send_template_for_signing
documentIdREQUIRED- The template or document ID to use for the signing request.
signingTypeREQUIRED- The signing type, which must match the template type configured in BoloForms.
mailSubjectOPTIONAL- The default email subject.
mailMessageOPTIONAL- The default email body.
signersREQUIRED- The list of participants who will receive the signing request.
list_documents
workspaceIdOPTIONAL- The workspace ID to query. When provided, it is sent through the workspaceid header.
queryOPTIONAL- Filter the document list by document name or keywords.
documentIdOPTIONAL- Filter results by a specific document ID.
filterOPTIONAL- A filter value supported by the official API.
sortByOPTIONAL- The field used for sorting.
list_template_respondents
templateIdREQUIRED- The template ID.
pageOPTIONAL- The page number, starting from 1.
limitOPTIONAL- The number of items to return per page.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Form Responses
List response records for a specific form so they can be used in follow-up automations. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_form_responsesControl Send Template For Signing
Start a signing request for a group of participants by using an existing template. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
send_template_for_signingVerify with List Documents
List documents and form statistics from the current BoloForms workspace. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_documentsSAFETY BOUNDARY
Operate BoloForms with explicit limits
- Authorize BoloForms with API key and grant only the provider access required by the selected actions.
- 1 action is change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in BoloForms rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the BoloForms task completed successfully.
CONNECTION MODEL
API key
BoloForms API key sent with the x-api-key header. Generate or copy it from the BoloForms API Key settings page: https://signature.boloforms.com/settings?copyKey=true&subType=APIKEY&type=DEV_SEC
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 3
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by BoloForms.