Tools let your voice agents take action during a call, not just talk. Book a calendar slot, look up an order through your own API, push a lead into your CRM, or trigger a multi-step automation in Zapier. These integrations turn voice agents from answering machines into workflow engines.
Let your Bolna voice agent check open Cal.com slots and book appointments during a live call, using your Cal.com API key and event types.

Use Make with Bolna to place outbound calls and run scenarios when a call ends, such as sending an email, SMS or WhatsApp follow-up with call data.
Place outbound calls from your Bolna voice agents inside any Zap. Connect Bolna to Zapier with an API key and use the Make a phone call action.
Run n8n workflows from Bolna call events and make calls, run batches and manage agents with the official n8n-nodes-bolna community node.
Add Bolna as a node in viaSocket workflows to place outbound calls and pull agent, execution, phone number and knowledge base data into other apps.

Send approved WhatsApp templates through AiSensy from any step of a Bolna workflow, for example to follow up with hot leads after a voice call.
Buy Bolna through AWS Marketplace to draw down your AWS committed spend, get one AWS invoice, and skip a standalone vendor security review.
| Tool | What it does with Bolna | Typical use |
|---|---|---|
| Cal.com | Checks open slots and books appointments in your Cal.com calendar during a call | Appointment scheduling |
| Custom function | Calls any HTTP API with parameters the LLM collects from the caller | Fetching or updating data in your own systems |
| Transfer call | Routes the live call to a human agent, another number or your own SIP trunk | Escalations and handoffs |
| Zapier | Places outbound Bolna calls from a Zap with the Make a phone call action | Starting calls from events in other apps |
| Make | Places calls, runs Bolna API calls and triggers a scenario when a call ends | Sending email, SMS or WhatsApp messages after a call |
| n8n | The official n8n-nodes-bolna community node makes calls, runs batches and workflows, manages agents and triggers on call events | Post-call workflows such as emails and CRM updates |
| viaSocket | Native actions to make calls, get executions and list agents, phone numbers, knowledge bases and providers | Starting calls and moving call data into other apps |
| AiSensy | Sends an approved WhatsApp template from any step of a Bolna workflow | WhatsApp follow-up based on how the call went |
| AWS Marketplace | Lets you buy Bolna through AWS and draw down your AWS committed spend | Enterprise procurement without a separate vendor security review |
For the full guide, see Function calling for voice AI agents in the Bolna docs.
The LLM reads each function's name and description, decides when to call it and collects the parameter values from the caller. Bolna then makes the HTTP request and passes the response back to the LLM, which continues the conversation.
Yes. Bolna function calling follows the OpenAI specification, so existing schemas work. You can also generate a custom function from a cURL command.
Bolna calls your endpoint from 13.203.39.153, 13.126.9.249 and 13.202.133.53. Whitelist all three if your API is behind a firewall.
Yes. Connect your AiSensy project API key and project ID once, then add an AiSensy WhatsApp node to a Bolna workflow to send an approved template, for example only to leads the call marked as hot.
Yes. Make has a Watch end of phone call trigger, and n8n receives call data through a webhook or the Bolna community node trigger. You can also point the agent's webhook_url at any endpoint that should receive the call data.
Last updated