Botsify
MessagingDrive Botsify chatbots from a flow across web, Messenger, WhatsApp, Telegram, Instagram, and SMS. Agents read conversations, send messages and stories, and manage the users behind them.
What This Integration Enables
Botsify's useful trait is per-user control across a lot of surface. The bot runs on web, Messenger, WhatsApp, Telegram, Instagram, and SMS, and activation is a per-messenger-user switch rather than a global one. That combination is what makes a real support handoff possible: you can take one customer out of automation without pausing the bot for everybody else, and you do not need a different escalation design per channel.
FlowRunner agents list the bots on the account with their per-bot keys, create bots, and list conversations narrowed to a source channel. They read the complete message history between the bot and one user, keyed by message push ID with sender, text, timestamp, and deletion state. They turn the bot on or off for a single user. They ask the bot what it would reply to a phrase without delivering the answer, which is unusual and turns out to be the most useful operation on the list. They list and create messenger users with the identifier rules each channel requires, send plain text or trigger a saved story or template postback, and store named attributes the bot can branch on later. On the reporting side they pull headline metrics with a segment breakdown and WhatsApp broadcast delivery results. On WhatsApp they list templates with approval status and any rejection reason, send an approved template to one or more numbers with numbered placeholders filled, and submit a new template for approval.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Escalation That Actually Silences the Bot
A customer on WhatsApp types something the bot classifies as a refund request. The agent calls Set Bot Activation For User to switch automation off for that person alone, pulls the exchange with Get Chat History, and opens a Zendesk ticket with the transcript and the channel attached. The support agent replies through the normal inbox. Nothing automated arrives on top of them, and no other customer notices anything changed.
Reusing the Bot's Knowledge Somewhere Else
The website has a search box that is not connected to the chatbot. Rather than maintaining a second answer set, the flow passes the query to Get Bot Response To Query for a system user and returns the bot's answer to the search results page. Nothing is delivered to any conversation, because this operation returns what the bot would say rather than saying it. One knowledge base, two front doors.
Imported Audience, Approved Template, Measured Result
A campaign list is imported with Create Bot Users, which requires the identifier to match the phone number for WhatsApp and SMS users and does not for website, Facebook, and Instagram ones. The agent sends the approved template with Send WhatsApp Template Message, filling the numbered placeholders per recipient. A day later it pulls Get WhatsApp Broadcast Report for the date range and posts delivery results to the channel, so the next send is decided on what happened rather than on what was hoped.
Human-in-Loop Highlight
The interesting gate on Botsify is not switching the bot off. That is safe, reversible, and the right reflex when a conversation turns. The gate is switching it back on. Set Bot Activation For User has no concept of who is currently mid-sentence, so re-enabling the bot while a support agent is still working the thread means automated replies start landing in the middle of a human conversation, in front of a customer who has already been escalated once. There is no undo for a message a customer has read. So FlowRunner puts the human-in-the-loop moment on the return path, and Botsify gives it an unusually good instrument: Get Bot Response To Query returns what the bot would say without delivering it. The agent takes the customer's last message, previews the bot's answer, and posts both to the support agent: "Ticket 3318 looks resolved. If the bot takes this thread back, its next reply to 'when will my refund show up' would be the generic refund policy card. Re-enable the bot for this user, keep it off, or hand back with a closing message from you?" The person decides with the bot's actual answer in front of them, not a guess about it. Deactivation stays automatic, because stopping the line is cheap. Restarting it is the decision worth a human.
Agent Capabilities
16 actionsBots
3- List Bots Returns every chatbot on the account with the per-bot API key each one uses, plus any bots another team has shared with the account. Used to discover the key to pass when a flow works with more than one bot.
- Create Bot Creates a new chatbot and returns its ID, name, page token, and per-bot API key. That key is the value every other bot-scoped operation needs and is not derivable from the bot ID, so it has to be stored.
- Get Bot Dashboard Stats Returns headline metrics: total users, incoming and outgoing message counts, and a breakdown by user segment. Supply both dates to scope the figures to a period, or leave them empty for lifetime totals.
Conversations
4- List Conversations Returns the messenger users who have conversations with the bot, optionally narrowed to a single source channel. This is the only paginated Botsify endpoint, so pages are walked by incrementing until an empty result returns.
- Get Chat History Returns the full message history between the bot and one messenger user, keyed by message push ID. Each entry reports the sender, the text, the creation time, and whether it has been deleted.
- Set Bot Activation For User Turns the bot on or off for a single messenger user. Switching it off hands the conversation to a human agent so automated replies stop; switching it back on returns the thread to automation.
- Get Bot Response To Query Asks the bot what it would reply to a given phrase for a specific user and returns the resulting messages without delivering them. Used to preview an answer, test intent matching, or let another system reuse the bot's knowledge.
Messenger Users
3- List Bot Users Returns every messenger user subscribed to the bot with their name, email, channel type, identifier, sign-up date, and stored attributes. Used to export an audience or look up the identifier the conversation operations need.
- Create Bot Users Adds one or more messenger users in a single call, optionally placing them all in a segment. For WhatsApp and SMS the identifier must match the phone number; website, Facebook, and Instagram users do not need one.
- Add User Attribute Stores a named value against one messenger user so the bot can personalize later replies or branch on it. Calling it again with the same key overwrites the previous value.
Messaging
2- Send Message To User Sends a plain text message to one messenger user on the selected channel. Botsify's documentation spells the Facebook channel as both facebook and messenger, so a rejected delivery is usually fixed by typing the alternative value into the Channel field.
- Send Story Or Template To User Triggers a saved story or message template for one messenger user instead of sending free text, referencing the block the bot should run through a story or template postback.
- List WhatsApp Templates Returns the templates registered on the bot with their approval status, language, buttons, parameters, and any rejection reason. Botsify documents this route as a GET carrying a body; this action sends the bot key as a query parameter instead, which is the safer equivalent.
- Create WhatsApp Template Submits a new WhatsApp template for approval, with body text and optional image, video, and buttons. The specification describes the category, header type, button type, which sections the template includes, and its placeholder variables.
- Send WhatsApp Template Message Sends an approved WhatsApp Business template to one or more phone numbers, referenced by its WABA template ID, with each numbered placeholder paired to the value to substitute.
- Get WhatsApp Broadcast Report Returns delivery results for WhatsApp broadcasts sent within a date range, so a flow can check how a campaign performed before sending the next one. Both dates are required.
Frequently Asked Questions
What can FlowRunner do with Botsify?
FlowRunner agents can run List Bots, Create Bot, and List Conversations in Botsify, plus 13 more actions.
Does connecting Botsify to FlowRunner require OAuth?
No. Botsify connects to FlowRunner with an API key, no OAuth flow required.
Can Botsify trigger a FlowRunner workflow automatically?
Botsify doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Botsify
$100 in credits. No card required. Connect in minutes.