Messaging
AiSensy logo

AiSensy WhatsApp + Bolna AI voice agents

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.

whatsappmessagingaisensynotificationsindia
At a glance

How AiSensy fits in the stack

Best for

Turning a voice agent into a workflow engine, not just a talker.

Use this layer when

The call should book, update, notify, route, or write data somewhere.

Connects to

Your telephony and AI stack plus calendars, CRMs, helpdesks, and automations.

Voice Stack

Tools are the action layer

Tools are the action layer

This layer lets Bolna take action during a call. It is how an agent books meetings, checks records, pushes updates, triggers follow-ups, and completes the workflow.

TelephonyPhone Network
→
STTListener
→
LLMReasoning
→
TTSVoice
→
ToolsActions

Last updated

What is AiSensy used for in a Bolna voice agent?

AiSensy lets a Bolna workflow send an approved WhatsApp template message as one of its steps, so a single workflow can mix voice calls and WhatsApp. Pick it when you want a WhatsApp follow-up based on how a call went, without building on Meta's WhatsApp Business API yourself.

How do I set up AiSensy with Bolna?

  1. In AiSensy, create a WhatsApp template, get it approved by Meta, and launch it as an API campaign.
  2. Open the AiSensy project and copy the project API key from Developer → Project API Keys.
  3. In your Bolna workflow, add the AiSensy WhatsApp node, paste the API key and project ID, and click Link AiSensy account. You can also connect at platform.bolna.ai/auth/aisensy.
  4. Select your campaign, fill in the template variables (you can use workflow fields), and send a test message to your own number before publishing.

Full steps: AiSensy setup guide in the Bolna docs.

Which AiSensy features does Bolna support?

Field on the aisensy_whatsapp nodeWhat it sets
template_nameThe approved WhatsApp template to send
languageThe template's ISO language code, such as en or en_US
recipientWho to message, for example a mobile number from the workflow entry
variablesTemplate placeholder values, keyed "1", "2" and so on, contiguous from 1
campaign_nameWhich AiSensy campaign the template came from (display only)

Messages use Meta-approved templates only. The node doesn't report delivery status yet, so give it a single onward path. Use numbers in international format.

What can you build with AiSensy and Bolna?

Hot lead follow-up. Call a lead, extract how the conversation went, branch on the result, and send hot leads a WhatsApp message while cold ones end.

Post-call confirmations. Send a template with details such as the caller's name, an order ID or a date once the call wraps up.

Multi-step outreach. Combine calls, waits, retries and WhatsApp messages in one workflow campaign that runs over days.

Different senders per brand. Each AiSensy project has its own WhatsApp number and API key, so link the project whose number should appear as the sender.

For in-call scheduling instead of after-call messaging, see Cal.com.

FAQ

AiSensy on Bolna: frequently asked questions

Copy your project API key from AiSensy (Developer → Project API Keys) and paste it with your project ID into the AiSensy WhatsApp node, or connect it once at platform.bolna.ai/auth/aisensy.

Bolna only shows launched campaigns. Check the API key belongs to the right AiSensy project and that the project has at least one live API campaign, since approved templates alone won't appear.

Not yet. The aisensy_whatsapp node is fire-and-forget, so it sends the message but doesn't return a delivery status to branch on.

The AiSensy integration runs as a step in a Bolna workflow, for example after a call ends. The docs list sending a WhatsApp message after a call as a workflow use case.

Browse this layer

Keep exploring the voice stack

Browse

Tools & Workflows

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.

Browse

Telephony

Telephony providers connect your voice agents to the phone network so they can make and receive real calls. Bolna supports managed integrations with major carriers as well as bring-your-own-carrier via SIP trunking, giving you full control over call routing, number provisioning, and cost.

Browse

Large Language Models

The LLM is the brain of your voice agent. It understands what callers say and decides how to respond. Bolna lets you switch between models like GPT-5.4 mini, Claude and DeepSeek by changing the provider and model in your agent LLM settings, so you can tune for speed, cost or reasoning depth.

Browse

Speech-to-Text

Speech-to-text converts what callers say into text that your LLM can process. Transcription accuracy and latency directly affect how natural a conversation feels. Bolna supports streaming STT providers optimized for telephony audio, including specialized models for Indian languages.

Browse

Text-to-Speech

Text-to-speech turns your agent responses into spoken audio. Voice quality shapes how callers perceive your brand. Flat, robotic speech kills trust while natural, expressive voices build it. Bolna integrates with the fastest TTS providers so responses sound human and arrive without awkward pauses.

See where AiSensy fits in your production workflow

Use the demo to walk through provider selection, stack tradeoffs, and the exact workflow you want Bolna to automate.