Flow XO
MessagingAutomate Flow XO chatbots, messaging end users on any channel and managing contacts, segments, transcripts, knowledge bases, and translations. Agents keep bot content current and act on what conversations reveal.
What This Integration Enables
Flow XO gives an agent the widest administrative surface of any chatbot platform in this catalog, and the reason that matters is not the surface count. It is that the evidence and the content live in the same API. Get Top Messages ranks the phrases end users actually typed. The knowledge base operations control what the bot can answer. That means a FlowRunner agent can close a loop most teams run by hand once a quarter and then stop running: read what people asked, find where the bot had nothing, propose the document that fills the gap, and measure whether the next period's top messages changed.
Beyond that loop, agents send text, media, single cards, scrollable card sets, and channel-native custom payloads into a live conversation on any connected channel. They create end users to start a conversation with somebody the bot has never met, and update existing ones with merged attributes, independent segment add and remove and replace, and an option to suppress triggers so a data sync does not start other flows. They resolve and create segments, list workflows and enable or disable them without opening the console, and pull analytics as a five-minute live snapshot or as a date range bucketed by hour, day, or month. They page conversations newest first with a total count and read a transcript where each message carries a role and a type. They maintain knowledge base documents with source URL and source fields for an auditable trail, and translation sets that hold both interface tokens and the keyword phrases the bot recognizes per language.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Turning Unanswered Questions Into Bot Knowledge
Every Monday the agent pulls Get Top Messages for the previous week and Get Top Flows alongside it. Phrases that rank high while the flows that should have handled them rank low are the gap. For each one the agent drafts a document from the relevant source material in Notion, records the source URL on the record so the origin stays auditable, and creates it with Create Knowledge Base Document. What the bot learns each week is a direct function of what customers asked it, rather than what somebody guessed they would ask.
Escalating With the Exchange Already Summarized
A conversation is flagged for handoff. The agent reads the transcript with List Conversation Messages, where each message carries a bot or channel role and a text, card, card set, or custom type, so the reconstruction is faithful rather than a flattened blob. An AI step summarizes it, and the summary plus the raw transcript open a Slack thread for the on-duty agent. The agent can also push a card set of appointment slots back into the live chat with Send Card Set Message once they decide what to offer.
Pausing an Automation Without Opening the Console
A promotional workflow should run only while an offer is live, and an out-of-hours workflow should run only outside business hours. Rather than anybody remembering, the agent calls Set Workflow Active State on a schedule, using List Workflows to confirm the current state first. When the offer ends, the workflow switches off on its own and the audit of who changed what lives in the flow run, not in somebody's memory.
Human-in-Loop Highlight
Flow XO's knowledge base is the closest thing in this catalog to a public statement made at scale, because every document is an answer the bot will give to every customer who asks that question, for as long as it stands. The write semantics make that unforgiving in two specific ways. Update Knowledge Base Document replaces the stored content rather than merging it, so the version a human edited by hand is gone the moment a sync runs. Delete Knowledge Base Document is permanent and cannot be restored through the API. Translations behave the same way: Update Translation replaces the language pack, so the regional phrases somebody added to catch a local intent vanish unless the flow read them first. FlowRunner therefore treats content replacement as a human-in-the-loop step and puts real evidence in front of the person. The agent calls Get Knowledge Base Document, sets the current text beside the proposed text, and asks the content owner: "The refund policy page changed. Knowledge base document 'Refunds and returns' would be replaced. Current version was last edited by hand and includes a sentence about damaged items that the new source page does not. Replace, replace and keep that sentence, or skip?" A person answers, and only then does the overwrite happen. Creating a new document is routine, because nothing is lost. Replacing or deleting one is not.
Agent Capabilities
28 actionsMessaging
5- Send Text Message Sends a plain text message to an end user identified by their response path. The simplest way for a flow to push a proactive message into an ongoing chat on any connected channel.
- Send Media Message Sends an image, video, or file by URL. The media must already be hosted somewhere the channel can reach, with an optional filename, thumbnail, and caption shown beside the attachment.
- Send Card Message Sends a single rich card with an optional media header and a row of choice buttons. Each choice is either a link that opens a URL or a quick reply whose value is sent back into the conversation as if the end user had typed it.
- Send Card Set Message Sends a horizontally scrollable carousel of cards in one message. Used to present a set of products, articles, or appointment slots where each card carries its own media header and buttons.
- Send Custom Message Sends a channel-native payload straight through without translation, for cases where a channel supports a format the text, media, and card types cannot express. Routing hints travel in the metadata object.
End Users and Segments
4- Create End User Creates an end user on a bot connection so a flow can start a conversation with somebody the bot has never spoken to, seeded with known profile fields, custom attributes, and segment membership.
- Update End User Updates an existing end user by response path. Attributes are merged rather than replaced, and an empty string removes one. Segments can be added, removed, or replaced independently, and triggers can be suppressed so the update does not start other flows.
- List Segments Returns every segment defined in the account. Segment IDs are what the end user operations expect, so this resolves a readable name into the ID needed to change membership.
- Create Segment Creates a new segment for end users to be assigned to. Segments are the grouping mechanism Flow XO uses for broadcasts and audience filtering, so one exists before contacts are bulk-tagged from a flow.
Workflows
2- List Workflows Returns a compact list of every workflow in the account with its ID, name, and whether it is currently active. Used to audit which automations are running or to look up the ID needed to change one.
- Set Workflow Active State Enables or disables a workflow, which makes it possible to pause an automation outside business hours or run a campaign workflow only while an offer is live, without touching the Flow XO console.
Insights
4- Get Insights Snapshot Returns live bot activity for the last five minutes: unique users, total messages, and the sent and received split. Flow XO reports these counters as strings. Useful as a lightweight check that traffic is still flowing.
- Get Insights Returns analytics over a date range bucketed by hour, day, or month. Each bucket reports active users, total users, new users, trigger runs, and message counts, alongside aggregates for the whole period.
- Get Top Messages Returns the most frequent inbound messages in a date range, ranked by how many times end users sent them. The quickest way to discover the phrases people actually type so unhandled intents can become new flows.
- Get Top Flows Returns the most frequently executed flows in a date range with their ID, name, and run count. Used to see which automations carry the load and which are effectively dormant.
Conversations
3- List Conversations Returns conversations across every bot, newest first, with the platform, bot, and end user attached. Paged with a skip offset and a limit, and the response reports the total number of matches so a flow can page through them all.
- Get Conversation Retrieves a single conversation by ID with the bot, platform, and end user it belongs to. Conversation IDs contain slashes and this action URL-encodes them, so the ID is passed exactly as returned by the list.
- List Conversation Messages Returns the transcript of a single conversation, paged with a skip offset and a limit. Each message carries a role of bot or channel and a type of text, card, card set, or custom, which lets a flow reconstruct the exchange faithfully before summarizing or escalating it.
Knowledge Base
6- List Knowledge Bases Returns every knowledge base configured in the account. A knowledge base ID is required by all document operations, so this is the entry point for any flow that maintains bot training content.
- List Knowledge Base Documents Returns the documents stored in a knowledge base. Unlike the rest of the Flow XO API, this endpoint pages with a page number and page size rather than a skip offset.
- Get Knowledge Base Document Retrieves a single document by ID including its full content. Used to read the current text before an AI step rewrites it, and to build a real diff rather than an assumed one.
- Create Knowledge Base Document Adds a document so the bot can answer from it. Only a title and content are required, with source URL and source fields recording where the material came from to keep an auditable trail. Returns the new document's UUID.
- Update Knowledge Base Document Replaces the stored content of an existing document. Used to keep bot answers in step with a changing source, such as refreshing a pricing page or a policy whenever the original is edited.
- Delete Knowledge Base Document Permanently removes a document so the bot stops answering from it. The document cannot be restored through the API and would have to be recreated.
Translations
4- List Translations Returns every translation set defined in the account, one per language. Each set holds the interface tokens and the keyword phrases the bot recognizes in that language.
- Get Translation Retrieves a single translation set by ID with its full token and keyword maps. Read it first when a flow needs to amend one phrase without discarding the rest of the language pack.
- Create Translation Creates a translation set for one of the 19 languages Flow XO supports. Tokens is a flat map of interface strings, and keywords maps each recognized intent to the phrases that should match it in that language.
- Update Translation Updates an existing translation set with new tokens or keyword phrases. The supplied maps are stored whole, because this replaces rather than merges the language pack.
Frequently Asked Questions
What can FlowRunner do with Flow XO?
FlowRunner agents can run Send Text Message, Send Media Message, and Send Card Message in Flow XO, plus 25 more actions.
Does connecting Flow XO to FlowRunner require OAuth?
No. Flow XO connects to FlowRunner with an API key, no OAuth flow required.
Can Flow XO trigger a FlowRunner workflow automatically?
Flow XO doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Flow XO
$100 in credits. No card required. Connect in minutes.