Bolna MCP integration for AI agents.
Connect AI agents to Bolna through 6 structured actions, including get agent, get execution, and get execution raw logs. Review authentication, inputs, workf…
- ACTION CONTRACTS
- 6
- 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 Bolna integration exposes
The Bolna Agent App exposes 6 provider-backed actions for ai and communication work. Its current contract lets an authorized agent get one bolna voice agent by agent_id, get one bolna execution by execution_id, and get raw logs for one bolna execution by execution_id. 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 Bolna account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Bolna capabilities.
Showing 6 of 6 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_agentREADGet one Bolna voice agent by agent_id.
INPUTS: agent_id
get_executionREADGet one Bolna execution by execution_id.
INPUTS: execution_id
get_execution_raw_logsREADGet raw logs for one Bolna execution by execution_id.
INPUTS: execution_id
get_user_infoREADGet the authenticated Bolna workspace user, wallet, and concurrency summary.
list_agent_executionsREADList execution history for one Bolna voice agent.
INPUTS: agent_id / page_number / page_size / status / call_type
list_agentsREADList all Bolna voice agents in the authenticated workspace.
INPUT CONTRACTS
Know what the action needs before it runs.
get_agent
agent_idREQUIRED- The Bolna agent identifier.
get_execution
execution_idREQUIRED- The Bolna execution identifier.
get_execution_raw_logs
execution_idREQUIRED- The Bolna execution identifier.
list_agent_executions
agent_idREQUIRED- The Bolna agent identifier.
page_numberOPTIONAL- The page number to request from Bolna.
page_sizeOPTIONAL- The number of executions to request from Bolna.
statusOPTIONAL- The execution status filter accepted by Bolna.
call_typeOPTIONAL- The call type filter accepted by Bolna.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Agent
Get one Bolna voice agent by agent_id. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_agentVerify with Get Execution
Get one Bolna execution by execution_id. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_executionSAFETY BOUNDARY
Operate Bolna with explicit limits
- Authorize Bolna with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Bolna data may still be sensitive and should be minimized before it enters model context.
- 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 Bolna rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Bolna task completed successfully.
CONNECTION MODEL
API key
Bolna API key used with the Authorization Bearer header. Sign in to the Bolna dashboard, open Developers, and create a new API key: https://platform.bolna.ai
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
- 6
- WRITE SIGNALS
- 0
- 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 Bolna.