WOZTELL
MessagingConnect AI agents to WOZTELL, an omnichannel conversational platform for WhatsApp, Messenger, Instagram, and web chat. Agents send responses, manage members and audiences, run broadcasts, administer channels and WhatsApp templates, and react to channel events so conversations flow between bots and human teams.
What This Integration Enables
WOZTELL is the outlier in FlowRunner's WhatsApp catalog, and the difference is structural rather than cosmetic. It resells Meta's official WhatsApp Business Platform. WhatsApp channels are backed by a WhatsApp Business Account, message templates are submitted to Meta for review before they can be sent, delivered messages carry Meta's own message identifiers, and Meta's twenty-four hour customer service window governs when a free-form message may be sent at all. There is no QR pairing of a personal phone and no session lifecycle anywhere in this API. It is also not only WhatsApp: the same member database drives Facebook Messenger, Instagram, Slack and web chat, so a customer who starts on one surface and finishes on another is the same record throughout.
That shape is what makes the connector interesting for orchestration. A hundred and eight actions cover the member database with its tags and notes, channels and their environments, conversation history and live chat handover, and WhatsApp templates and media. They also reach audiences, broadcasts and scheduled pushes, priority group routing, support tickets, the document collections the chatbot reads and writes, the media library, chatbot tree backup, scheduled agendas and analytics. One trigger covers inbound and outbound channel events. Authoring chatbot trees is deliberately left out, because a half-built graph corrupts a live chatbot, while reading, cloning, exporting and duplicating them is included. The result is a platform where an agent can run the conversation, the routing and the data behind it, and where the things that reach a person permanently are exactly the things a person should still decide.
Without FlowRunner
With FlowRunner
Use Case Scenarios
One member, four surfaces, one history
A customer asks about an order on Instagram, then follows up on WhatsApp two days later. On Channel Event fires on both. The agent resolves the member by external identifier scoped to the channel, because external identifiers are unique within a channel rather than across the account, and merges the two records with Merge Members By External IDs once the match is confirmed. It answers with Send Responses, pulls order state from Shopify, and writes the resolution with Add Note To Member. The second conversation opens with the first one's context already attached rather than starting from nothing.
A knowledge base the chatbot can actually write to
Support answers live in a WOZTELL data source rather than in a document nobody updates. The agent searches it with Search Data Source Documents, answers from what it finds, and when a question has no governed answer it opens a ticket instead of improvising. Where a booking slot or a queue entry has to be claimed without a race, Find And Modify Data Source Document is the atomic primitive that makes that safe. New answers written by the support team are imported with Import Data Source Documents and the background job is polled with Get Background Task, so a stale answer never sits behind a silent import failure.
A broadcast that respects the window it is sent in
A service notification goes to a segment. The agent builds the recipient set with Create Audience, using a dynamic filter that re-evaluates when the broadcast runs rather than freezing a list that will be stale by then. Because members outside Meta's twenty-four hour window can only be reached with an approved template, the agent checks List WhatsApp Message Templates for approval state before it builds the payload, and reports any template still under review rather than scheduling around it. After the run, Create Retry Audience builds an audience from the members the broadcast failed to reach, and that second pass is treated as a separate decision with its own approval rather than an automatic retry.
Human-in-Loop Highlight
Two gates matter on this connector, and the interesting part is that one of them is deliberately absent.
Toggle Live Chat, the handover from chatbot to a human agent, runs on the agent's own judgment with nothing in the way. Asking permission to fetch a person is the opposite of what human-in-the-loop means. An agent that detects frustration, a legal question or a request it cannot ground should pull that lever immediately, and the platform should get out of the way while it does.
Delete WhatsApp Message Template is the one that stops. On this platform a template is addressed by name, not by identifier, so deleting one removes every language variant registered under that name at once. It is also the only way to reach a member outside Meta's twenty-four hour service window, and a replacement has to go back through Meta's review before it can send anything. That combination means a routine cleanup can leave a cohort unreachable for as long as review takes, on a channel where the alternative is nothing. So the agent gathers the evidence and hands over the decision: "Template order_delay_notice is unused in the last 90 days and flagged for cleanup. It carries 4 language variants and deleting the name removes all 4. 812 members are currently outside the service window and this template is the only approved route to them. Delete, or archive the flow that references it and keep the template?" A person answers. The agent has already done everything that can be undone, including retiring the flow, updating the audience and writing the note on every affected member.
Agent Capabilities
108 actionsMessaging
2- Send Responses Sends one or more platform responses to a member: text, image, or an approved WhatsApp template with its components. A billed send path that delivers to real handsets.
- Redirect Member To Node Runs a node of a chatbot tree for a member, with independent switches for pre-actions, the response and post-actions, and an optional metadata object the node can read. The way an agent hands a conversation to governed bot logic rather than composing free text.
Members
18- Get Member Returns one member by WOZTELL identifier or by their external identifier on the underlying platform.
- List Members Lists members with filtering. Cursor paginated with a capped page size, which is enforced before the request.
- Create Member Creates a member record.
- Update Member Updates a member record.
- Delete Member Deletes one member.
- Delete Members In Bulk Deletes members matching criteria. It requires a criteria array or a timestamp bound, because an unqualified call would otherwise match the whole account. Runs as a background task.
- Update Members In Bulk Updates members matching a filter. Both a filter and an update are required.
- Upsert Member By External ID Creates or updates a member keyed on their identifier on the underlying platform, which is a phone number on WhatsApp and a page-scoped identifier on Facebook. Always pass the channel, because external identifiers are unique only within one.
- Upsert Web Chat Member By External ID The same operation for web chat members.
- Update Web Chat Member Updates a web chat member record.
- Merge Members By External IDs Merges member records that turn out to be the same person on different channels.
- Batch Update Members Updates an explicit list of members. The list is required rather than optional.
- Import Members Imports members in bulk as a background task. Poll it with Get Background Task.
- Add Member Tags Adds tags to a member. Tags are how audiences, routing and reporting all find people later.
- Remove Member Tags Removes tags from a member.
- Add Note To Member Writes a note on the member record, which is what a human agent reads when they pick the thread up.
- Remove Note From Member Removes a note.
- Update Note Edits an existing note.
Channels
8- List Channels Lists the channels on the app across WhatsApp, Messenger, Instagram, Slack and web chat.
- Get Channel Returns one channel, including the channel secret used to sign webhook deliveries. Read it explicitly when a flow wants to verify a delivery itself.
- Create Channel Creates a channel.
- Update Channel Updates a channel's configuration.
- Delete Channel Deletes a channel. Where dependencies block the change the platform reports it, and the call can be re-run with force enabled.
- Subscribe Channel Subscribes a channel so it starts delivering events.
- Unsubscribe Channel Unsubscribes a channel, with the same dependency reporting.
- Update Channel Priority Group Routing Binds a priority group to a channel so a named member set routes to a different chatbot tree from everyone else.
Channel Environments
9- Create Channel Environment Creates one bot configuration on a channel, such as a staging environment alongside production.
- Update Channel Environment Updates an environment, including its tree slots. It accepts replace and add semantics only, so removing a tree entry needs one of the add-or-remove actions below.
- Delete Channel Environment Deletes an environment.
- Update Channel Environment Hooks Updates the environment's hooks.
- Update Channel Environment Webhooks Updates the environment's webhook list. The trigger manages its own registration separately and appends rather than replacing.
- Add Or Remove Environment Trees Adds or removes default trees on an environment. The only route that can take an entry out.
- Add Or Remove Environment Off-Hours Trees Adds or removes the trees that run outside business hours.
- Add Or Remove Environment Live Chat Trees Adds or removes the trees that run while a conversation is in live chat.
- Update Channel Incoming Webhooks Updates the incoming webhook configuration on a channel.
Conversations
5- List Conversation History Returns stored conversation history. The read an agent runs before composing a reply so the answer is grounded in what was already said.
- Get Chat Resolves a platform message identifier back to the stored chat, which is how a delivery receipt is matched to the message it refers to.
- Export Chats Exports conversation history between two bounds. Both bounds are required and an end earlier than the start is refused.
- Create Chats In Batch Writes history records in bulk. Its send-outbound switch additionally dispatches them as real, billed messages and is off unless explicitly enabled.
- Toggle Live Chat Hands a conversation between the chatbot and a human agent, in either direction. The action an agent should reach for on its own the moment a thread stops being routine.
WhatsApp Templates and Media
5- List WhatsApp Message Templates Lists templates with their approval state. Check this before building a payload that depends on one. The vendor marks the route deprecated but publishes no replacement and it remains the only route to this data.
- Create WhatsApp Message Template Submits a template to Meta for review. It cannot send anything until Meta approves it.
- Delete WhatsApp Message Template Deletes a template by name, which removes every language variant registered under that name. A replacement has to go back through Meta's review, which is why this is the action the flow hands to a person.
- Get WhatsApp Media File URL Returns a URL for media on a WhatsApp channel. Also vendor-deprecated with no published replacement, and still the only route to its data.
- Upload Attachment To Channel Fetches a file from a URL, registers it with the platform, and returns the media identifier a later message can reference.
Audiences
5- List Audiences Lists saved recipient sets.
- Create Audience Creates an audience. A static audience freezes a member list; a dynamic one re-evaluates its filter when the broadcast runs.
- Update Audience Updates an audience. Supplying members requires an explicit member action, so the platform is never left to guess between adding and removing them.
- Delete Audience Deletes an audience.
- Create Retry Audience Builds an audience from the members a previous broadcast failed to reach. Treat the retry as its own decision rather than an automatic second pass.
Broadcasts
7- List Broadcasts Lists broadcasts and their state.
- Create Broadcast Creates a broadcast to an audience, an inline audience or an explicit member list, one of which is required. A billed send path that cannot be recalled once it starts.
- Update Broadcast Updates a broadcast that has not started.
- Delete Broadcast Deletes a broadcast, which cancels it if it is still scheduled.
- Create Subscription Push Creates a push targeting an explicit member list or notification tags, optionally chained under a parent. Also a billed send path.
- Update Subscription Push Updates a scheduled push.
- Delete Subscription Push Deletes a push, canceling it if it has not started.
Priority Groups
4- List Priority Groups Lists named member sets used for differentiated routing.
- Create Priority Group Creates a priority group.
- Update Priority Group Updates a priority group's membership or configuration.
- Delete Priority Group Deletes a priority group.
Tickets
2- List Tickets Lists support tickets with their inlet and outlet channels, member, assignee and reassignment chain.
- Get Ticket Returns one ticket.
Data Sources
15- List Data Sources Lists the document collections the chatbot reads and writes.
- Create Data Source Creates a collection, such as a catalog, an FAQ set or a booking table.
- Update Data Source Updates a collection's configuration.
- Delete Data Source Deletes a collection.
- Import Data Source Documents Imports documents in bulk.
- Search Data Source Documents Searches documents with a filter. The retrieval step behind a grounded answer.
- Get Distinct Data Source Values Returns the distinct values of a field, which is how an agent enumerates options without inventing them.
- Search Data Source Documents By Location Searches documents geographically, for stores, service areas and pickup points.
- Create Data Source Document Creates one document.
- Update Data Source Document Updates one document.
- Delete Data Source Documents Deletes documents. It requires either explicit document identifiers or an explicitly enabled delete-all, so an unqualified call cannot clear a collection.
- Upsert Data Source Documents Creates or updates documents in one call.
- Update Data Source Documents In Bulk Applies a patch across documents matching a filter.
- Find And Modify Data Source Document Finds and updates one document atomically. The right primitive for claiming a queue entry or reserving a slot without a race.
- Aggregate Data Source Documents Runs an aggregation pipeline over a collection, for reporting inside the conversation rather than after it.
Media Library
6- List Files Lists files in the media library.
- Get File Returns one file record.
- Get Upload URL Returns a pre-signed URL for uploading local bytes, which are then registered with Create File.
- Create File Registers a file, either one already at a public URL or one just uploaded.
- Delete Files Deletes files from the library.
- Update File Media IDs Records the platform media identifiers a file has been registered under, so a later message references it without re-uploading.
Bot Flows
4- List Trees Lists chatbot trees.
- Get Tree Returns a tree, including the node identifiers Redirect Member To Node needs.
- Duplicate Tree Clones a tree, which is how a change is staged without touching the live one.
- Export Trees Exports trees for backup or review.
Agendas
3- Create Agenda Schedules a bot run for a member: a one-off follow-up or a recurring pattern until a cut-off. Because the target node normally sends a message, creating an agenda schedules a billed send.
- Update Agenda Updates a scheduled agenda.
- Delete Agenda Deletes an agenda. It requires an agenda, a member or a tag rather than running unqualified.
Analytics
6- Get Daily Active Member Overview Returns daily active member figures.
- Get Active Member Counts Returns active member counts over a period.
- Get New Member Counts Returns new member counts over a period.
- Get Custom Event Table Returns custom events with member identity and per-member figures.
- Get Custom Event Histogram Returns the aggregate time series for custom events. It cannot break results down by member, which is the platform's own split rather than a simplification here.
- Get NLP Analytics Overview Returns intent and language-understanding performance.
App and Integrations
5- Get App Returns the app, including the app identifier the media library actions need, plus data sources, team members and channel pairs.
- List Installed Integrations Lists the integrations installed on the account. How the platform keys the messaging and channel actions expect are discovered rather than guessed.
- Get Installed Integration Returns one installed integration.
- List App Integrations Lists integrations available to the app.
- Update App Integration Metadata Updates metadata on an app integration.
Account
4- Get Current User Returns the authenticated user. A clean connection health check.
- Get Token Info Returns the scopes recorded for the access token, which is the fastest way to confirm a token can do what a flow is about to ask of it.
- Get Background Task Polls the jobs started by member import and bulk deletion.
- Create Notification Raises a notification inside the platform.
Triggers
1 triggersEvent Triggers
1- On Channel Event Fires when WOZTELL delivers a webhook event on the selected channel. Choose which events to subscribe to: inbound messages from members, outbound messages from the chatbot, from the send API or from a broadcast, member lifecycle changes, and node triggers. The trigger registers as an additional webhook on the channel environment rather than replacing one already configured there, and removes only its own registration when deleted. The payload carries the event type, the app, channel and member identifiers, and either a normalized message event or before and after snapshots for member updates. Note that member events are delivered under a single member-update type even though they are subscribed to individually, so the event type filter matches the value that actually arrives rather than the subscription name.
Frequently Asked Questions
What can FlowRunner do with WOZTELL?
FlowRunner agents can run Send Responses, Redirect Member To Node, and Get Member in WOZTELL, plus 105 more actions.
Does connecting WOZTELL to FlowRunner require OAuth?
No. WOZTELL connects to FlowRunner with an API key, no OAuth flow required.
Can WOZTELL trigger a FlowRunner workflow automatically?
Yes. WOZTELL supports 1 trigger that can start a FlowRunner workflow automatically.
Start building with WOZTELL
$100 in credits. No card required. Connect in minutes.