DialoX
AIDrive conversational AI agents built on DialoX, steering conversations across WhatsApp, web, phone, and email. Agents hand context into a bot and take the thread back when a person needs to decide.
What This Integration Enables
DialoX is not a chat widget with a phone number bolted on. The conversation is the primary object and the channel is a property of it, so the same thread carries a direction, a channel, a locale, a tag set, an assigned operator and a bag of custom data the bot script collected along the way. That model is what lets a FlowRunner agent treat a WhatsApp thread, a web session and a phone call as the same kind of thing, and it is why the connector reaches for Start Outbound Call and Send SMS in the same breath as List Conversations.
The two operations that matter most in an orchestrated setup are the ones that push into a live dialog. Send Conversation Event raises a named event with an arbitrary payload that the bot script listens for, which is the sanctioned way to tell a running conversation that a payment cleared or an order shipped and let the script decide what to say about it. Invoke Task calls a task declared in the bot script with REST access enabled and returns whatever it produces, so bot side logic can be run on demand rather than waited for. Send Operator Action puts a message, a typing indicator, a location or a media attachment into the thread as the bot or as a human operator, which is how a person takes over without the customer changing surface. DialoX also exposes a real webhook registration API, so the On Bot Event trigger creates and deletes its own webhook and never touches webhooks configured by hand, and delivered payloads are verified against the bot's API token with an HMAC header before anything downstream runs.
Without FlowRunner
With FlowRunner
Use Case Scenarios
An external outcome pushed into a conversation that is still open
A customer is in a WhatsApp thread asking where their order is. Meanwhile the warehouse dispatches it and Shopify records the fulfilment. Rather than sending a separate templated notification that arrives alongside the live chat and confuses everyone, the agent calls Get Conversation to confirm the thread is still open, then raises a named event into it with Send Conversation Event carrying the tracking number. The bot script listens for that event and branches into the dialog its designers wrote for it. The customer sees one continuous conversation in which the answer to their question simply arrives, because the system that knew the answer was able to speak into the dialog they were already in.
An anonymous visitor turned into a known contact, then followed up on
A web conversation starts with no identity attached. The bot collects an email in its custom conversation data. The agent reads that with Get Conversation, looks the person up in HubSpot, and calls Create User or Update User to write the name, locale, timezone, tags and external id back onto the DialoX user record so future conversations start from a known identity rather than an anonymous visitor. Because timezone is now on the record, the follow up flow can send an SMS at a defensible local hour rather than whenever the workflow happened to run. List SMS reconciles delivery afterwards, so a failed send becomes a task rather than a silence.
A note raised in chat that becomes a task and closes itself
The bot raises notes and scheduled follow ups against conversations. The agent walks List Notes for anything open, creates a matching task in Asana with the note's title, body, due time and a link back to the originating conversation, and carries over the custom data the bot collected so whoever picks it up has the context. When the task closes, the agent calls Update Note to mark the follow up done, which keeps DialoX and the task tracker from drifting. The one thing it does not do automatically is close a note whose body reads as a complaint or a cancellation intent; those go to a supervisor to close by hand, because a follow up marked done is a claim that somebody actually followed up.
Human-in-Loop Highlight
Start Outbound Call is where the agent stops, and the reason is that this connector can compose speech.
An outbound call in DialoX is not a notification. It rings a real phone, it incurs usage based cost per call, and it names a specific dialog with arguments passed into it, which means the workflow supplies the variables the bot will speak aloud. A customer name, an amount owed, an appointment time. Get one of those wrong and a person hears the wrong thing once, at whatever hour the flow ran, with no recall and no edit. Send SMS carries the same finality in text form and the same per message cost.
So a campaign flow assembles everything and then hands over the trigger. It builds the call list, resolves each recipient's timezone from List Users so nobody is dialled at seven in the morning, and then does the thing only DialoX makes possible: it calls Synthesize Speech on the rendered dialog arguments and attaches the actual MP3 to the approval. The message posted to the operations owner reads: "412 outbound calls staged on the renewal dialog. Local dial window is 09:00 to 18:00 per recipient timezone; 37 recipients fall outside it and are excluded. Here is the audio a customer will hear, with sample data filled in. Approve the batch, or send it back?" The owner listens to sixteen seconds of audio and decides. That is a materially better review than reading a template, and it is the difference between approving a plan and approving what will actually happen. The agent handles the list building, the timezone arithmetic and the exclusions. A person owns the moment a stranger's phone rings.
Agent Capabilities
20 actionsConversations
6- List Conversations Returns the conversations the API token can reach with status, direction, channel, locale, tags, operator, the last user and text message, and the custom conversation data the bot collected. Narrowable by status, channel, bot, date range, free text search and tag inclusion or exclusion.
- Get Conversation Returns one conversation by id with its full state including status, direction, channel, user key, locale, tags, assigned operator, last messages and collected custom data. Used to refresh a thread before deciding how a workflow should respond.
- Create Conversation Creates a conversation without starting it, so a workflow can prepare a thread before any message is exchanged. Leaving the user empty creates a new anonymous user.
- Delete Conversation Permanently removes a conversation and its history. Used to honour an erasure request or clean up threads created by automated tests.
- Get Conversation History Returns the chat actions of a conversation in reverse chronological batches, covering user messages, bot replies, media, locations and events. The returned cursor walks further back through the transcript.
- Get Conversation Summary Returns per conversation counts over a date range including total messages, user messages, group, tags and the start and end times. Used for volume and engagement reporting without pulling every transcript.
Speaking Into a Conversation
3- Send Operator Action Emits an action into a conversation as the bot or as a human operator, which is how a workflow or a person speaks to the end user. Sends a text message, a typing indicator, a location, a media attachment, or stops the current dialog.
- Send Conversation Event Raises a named event inside a conversation with an arbitrary payload that the bot script can listen for and branch on. The standard way to push an outcome from an external system, such as a completed payment or a shipped order, back into a running conversation.
- Invoke Task Calls a task declared in the bot script and returns what it produces along with a success flag and any error message. The task must be declared with REST API access enabled in DialoX Studio.
End Users
4- List Users Returns the end users known to a bot with names, locale, timezone, external id, profile picture, tags and the custom user data collected across conversations. Supports free text search, tag filters, locale filtering and pagination.
- Create User Creates an end user so a conversation can start against a known identity rather than an anonymous visitor. Accepts contact details, locale and timezone, an external id for CRM correlation, tags, and a free form data object bot scripts can read.
- Update User Updates an existing end user, changing only the fields supplied, so a workflow can enrich a chat visitor as CRM details become known. Tags and the custom data object are replaced wholesale when supplied.
- Delete User Permanently removes an end user. Used to honour an erasure request.
Outbound Channels
4- Send SMS Sends a one off SMS through the bot's configured provider. It incurs usage based cost, does not start a conversation and does not execute any bot script. The sender name must already be approved in the environment settings.
- List SMS Returns the messages sent by a bot with delivery status, sender, recipient, your reference and any failure reason. Used to reconcile delivery outcomes after a send.
- Start Outbound Call Places an outbound voice call from the bot to a destination number and returns the resulting conversation. It incurs usage based cost. A specific dialog can be named and arguments passed into it, so the call is personalised with workflow context.
- Synthesize Speech Converts text to spoken audio using a DialoX voice and returns the raw MP3 bytes. Used to preview exactly what a caller will hear before a batch of calls is authorised, and requires text to speech to be enabled on the environment.
Notes and Follow-ups
2- List Notes Returns the notes and scheduled follow ups raised against conversations with status, title, location, body, start and due times, and the originating conversation with its collected data. Filterable by status, conversation, tags and free text.
- Update Note Updates a note raised against a conversation, most often to mark a follow up done once a workflow has handled it. Title, location, body and the start and due times can also be changed.
Bot
1- Get Bot Returns a bot's profile including title, default and extra locales, region, timezone, purpose, organisation and privacy URL. Used to confirm which environment a workflow is pointed at before it starts writing conversations.
Triggers
1 triggersEvent Triggers
1- On Bot Event Fires when the selected bot emits a webhook event, delivering the raw payload with its type, creation time, bot, user, conversation and channel. DialoX exposes a real webhook registration API, so this trigger creates its own webhook on activation and deletes it on removal without touching webhooks configured by hand. Leave the event filter empty to receive everything or pick one to narrow it. Payloads are verified against the bot's API token using an HMAC signature header, and events that fail verification are dropped.
Frequently Asked Questions
What can FlowRunner do with DialoX?
FlowRunner agents can run List Conversations, Get Conversation, and Create Conversation in DialoX, plus 17 more actions.
Does connecting DialoX to FlowRunner require OAuth?
No. DialoX connects to FlowRunner with an API key, no OAuth flow required.
Can DialoX trigger a FlowRunner workflow automatically?
Yes. DialoX supports 1 trigger that can start a FlowRunner workflow automatically.
Start building with DialoX
$100 in credits. No card required. Connect in minutes.