SensiBot
MessagingAutomate the SensiBot AI WhatsApp platform, switching the assistant between AI and keyword replies and reading chat history. Agents hand a conversation to a human the moment it needs one.
What This Integration Enables
SensiBot is the only connector in this batch whose primary object is the assistant rather than the message. You switch its brain with Set Bot Type, choosing between the ChatGPT-powered AI Bot and the Keyword Bot that replies only from configured keyword rules without calling a model at all. You turn it off for one person with Set Human Takeover or for an entire channel with Set WhatsApp Cloud Bot Status. You rewrite its opening line with Set Welcome Message. Sending messages is something this connector also does; governing an assistant that is already talking to your customers is what it is for.
It is also the connector where this batch's central distinction lives inside one product. SensiBot runs two kinds of WhatsApp account side by side and the connector exposes both. WhatsApp Cloud is the official Meta path: approved templates, the 24 hour service window, positional variables and quick reply or URL buttons, with scheduling. WhatsApp Beta is an unofficial web session, which needs no template approval and depends on a live session staying connected. Knowing which one a given flow is sending through is not a detail, it decides what is deliverable and what happens when the connection drops. One note on the surface itself: prefer Send WhatsApp Beta Message over Send WhatsApp Beta Message Via GET, because the GET variant carries the API token in the query string where logs and proxies can see it. And Get Assistant Settings is documented as a GET but a live host answered 405 for GET, so check the current SensiBot reference if that call is rejected.
Governing an assistant is exactly what Orchestration as a Service means in practice. SensiBot's bot is an agent your company is already running. FlowRunner sits above it, reads what it has been saying, decides when a person should take over, and holds the switches that change its behaviour at scale.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Handing one conversation to a person, with the context intact
A subscriber writes something the classifier reads as an explicit request for a human. The agent calls Set Human Takeover for that subscriber, which stops the bot replying so a live agent can own the conversation. It then calls Get Subscriber Info and Get Subscriber Variables to collect what SensiBot already captured, which is usually the name, the contact details and every answer the customer gave during the chat, and Get Chat History for the transcript. All of it goes into a ticket in Zendesk with a summary at the top. The agent who picks it up does not open with a question the customer already answered, and turning takeover back off later hands the conversation back to the assistant cleanly.
A deterministic fallback when the AI cannot be trusted right now
An incident is declared in PagerDuty because the model provider behind the assistant is returning errors or nonsense. Leaving an AI Bot answering customers through that is worse than answering nothing. The agent assembles the evidence, recent transcripts from Get All Chat History and the current configuration from Get Assistant Settings, and proposes the switch. On approval, Set Bot Type moves the account to Keyword Bot, which replies only from configured keyword rules and calls no model, and Set Welcome Message updates the greeting to say answers are limited while the issue is being worked. When the incident closes, the same flow proposes switching back. Deterministic replies during a bad hour are a feature, and this connector makes them a one-call change.
An audience built from conversations rather than from a spreadsheet
A lead capture flow qualifies subscribers from what they told the bot. The agent reads Get Subscriber Variables, applies the qualification rules, and calls List WhatsApp Cloud Customer Lists to resolve the target list name into the identifier the rest of the API expects, creating it with Create WhatsApp Cloud Customer List when it does not exist yet. Qualified subscribers are grouped for a later campaign, and the segment definition is written to Google Sheets so the marketing team can audit it. The follow-up itself goes out with Send WhatsApp Cloud Template, which is the only way to start a conversation outside the 24 hour window, with up to ten positional variables, an optional media header, up to three buttons, and a Schedule Date Time with a Timezone so it lands in working hours.
Human-in-Loop Highlight
The interesting thing about SensiBot is that it has two escalation levers with wildly different blast radius, and only one of them should be gated. Set Human Takeover affects a single subscriber. When a flow detects an explicit request for a person, an agent should just do it, immediately, without waiting for anyone. Making a customer wait for approval before a human is allowed to answer them is the automation being precious about itself.
Set Bot Type and Set WhatsApp Cloud Bot Status are the other kind. They change every live conversation on the account at once, including the ones already halfway through an answer, and no customer in any of them knows why the tone just changed. So when the agent detects that the assistant is going wrong at scale, it does not silence it. It builds the case: transcripts from Get All Chat History for the affected window, the classification of where the assistant lost the thread, the current bot type and welcome message from Get Assistant Settings, and the subscriber count in active conversations right now. Then it asks. "Repeated-question rate on the assistant is running well above its normal band across 61 conversations in the last two hours, transcripts attached. I have taken over the 4 that asked for a person. Flip the whole account to Keyword Bot, disable Cloud bot replies entirely, or leave it on AI?" A support lead answers in Slack and the flow acts on that answer. The line is drawn where it should be: the agent owns per-conversation escalation and a person owns the switch that touches everyone.
Agent Capabilities
16 actionsAssistant Control
4- Get Assistant Settings Returns the current configuration of the assistant, including the active bot type, welcome message and human takeover state. SensiBot documents this endpoint as a GET, but a live host answered 405 Method Not Allowed for GET, so the verb is unconfirmed against a real account; check the current SensiBot reference if the call is rejected.
- Set Bot Type Switches the assistant between the ChatGPT-powered AI Bot and the Keyword Bot that replies only from configured keyword rules without calling an AI model. Used to fall back to deterministic replies during an incident or outside business hours, then switch back when AI answers are wanted again. This changes every conversation on the account.
- Set Welcome Message Updates the greeting the assistant sends when a subscriber opens a new conversation, for rotating seasonal messaging, announcing support hours, or personalising the opening line per campaign without editing the bot by hand.
- Set Human Takeover Turns human takeover on or off. While takeover is on the bot stops replying so a live agent can own the conversation, and turning it off hands the conversation back to the assistant. This is the per-subscriber escalation switch, and it is the one an agent should be trusted to throw on its own.
Conversations and Subscribers
4- Get Chat History Retrieves the stored chat history for a single subscriber so a flow can summarise the conversation, detect intent, or supply an AI step with prior context before drafting a reply.
- Get All Chat History Retrieves stored transcripts across every subscriber of the connected account in one call, intended for reporting, bulk export and offline analysis. For a single conversation use Get Chat History, which is far cheaper.
- Get Subscriber Info Returns the stored profile of a subscriber, such as the name and contact details SensiBot captured during the conversation. Used to enrich a CRM record or personalise an outbound message before it is sent.
- Get Subscriber Variables Returns the custom variables SensiBot stores against one subscriber, which are the values the bot collected during the chat. This is the fastest way for a flow to read answers a customer already gave instead of asking again.
WhatsApp Cloud
5- Send WhatsApp Cloud Message Sends a free-form message through a WhatsApp Cloud API account connected to SensiBot, as Text or as Image, Audio, Video or Document media. WhatsApp only allows free-form messages inside the 24-hour customer service window; outside it, use Send WhatsApp Cloud Template.
- Send WhatsApp Cloud Template Sends an approved WhatsApp Cloud template, which is the only way to start a conversation outside the 24-hour service window. Supply up to ten positional Variables, an optional media or text header, and up to three Buttons rendered as quick replies or URL buttons. Set Schedule Date Time with a Timezone to queue the send, or a Bot Flow ID to hand the reply to a SensiBot flow.
- Set WhatsApp Cloud Bot Status Enables or disables automated bot replies on a WhatsApp Cloud account. Disabling stops the bot answering while leaving the connection intact, which is the clean way to silence automation during a migration, an outage or a manual support push. It applies to the whole account.
- List WhatsApp Cloud Customer Lists Returns the customer lists defined on the connected WhatsApp Cloud account. Customer lists are the audience groupings SensiBot uses for broadcasts, so this is how a flow resolves a list name into the identifier the rest of the API expects.
- Create WhatsApp Cloud Customer List Creates a new customer list on the connected account so contacts can be grouped for later broadcasts, which pairs naturally with a lead-capture flow that builds a segmented audience automatically.
WhatsApp Beta
3- Send WhatsApp Beta Message Sends a message through a WhatsApp Beta account, which is an unofficial web session, as Text, as Media with an Image, Audio or Video media type, or as Document with a PDF, XLS, XLSX, DOC or DOCX document type. Beta accounts do not require template approval but depend on a live web session staying connected.
- Send WhatsApp Beta Message Via GET Sends a Beta message using the query-string variant of the send endpoint, authenticating with the API token as a query parameter rather than an Authorization header. It suits callers that cannot set headers, but prefer Send WhatsApp Beta Message where possible, because a token in a URL is more easily leaked through logs and proxies.
- Set WhatsApp Beta Bot Status Enables or disables automated bot replies on a WhatsApp Beta account, so automation can be paused on an unofficial web session while an agent works the inbox manually and re-enabled without reconnecting the session.
Frequently Asked Questions
What can FlowRunner do with SensiBot?
FlowRunner agents can run Get Assistant Settings, Set Bot Type, and Set Welcome Message in SensiBot, plus 13 more actions.
Does connecting SensiBot to FlowRunner require OAuth?
No. SensiBot connects to FlowRunner with an API key, no OAuth flow required.
Can SensiBot trigger a FlowRunner workflow automatically?
SensiBot doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with SensiBot
$100 in credits. No card required. Connect in minutes.