Mumble

Connect AI agents to Mumble, a WhatsApp business messaging platform for customer conversations. Agents manage customers and labels, send session and template messages, route conversations to agents, teams, or chatbots, and create message templates so WhatsApp outreach and support run without manual triage.

Verified 27 actions API key available

Mumble website ↗ Platform Documentation ↗ Capability data verified 2026-08-11

A paid lead lands in the CRM with its click identifiers still attached to the record

Phone number, name, UTM parameters, and the Google, Meta, or TikTok click identifier are pulled off the lead

Add Customer writes the contact and every attribution field into Mumble in one call, keyed by the phone number

Is Conversation Active reports whether a WhatsApp session window is currently open for that number

Send Template Message With Variables opens the conversation with an approved template, because no session exists yet

The campaign owner gets the thread and the attribution the lead arrived carrying

When no approved template covers the message the campaign needs, the agent stops and asks whether a new one should be submitted to WhatsApp for review

What This Integration Enables

Mumble is an Israeli WhatsApp business messaging platform, and the thing that makes it worth wiring an agent into is the way it treats a conversation as an attributed asset rather than a message log. Add Customer and Edit Customer accept the entire attribution surface in the same call that creates the contact: UTM parameters, the click identifiers of Google, Meta, Microsoft, TikTok, Yandex, LinkedIn, Taboola, Outbrain, and X, Google Analytics identifiers, and the originating page, user agent, and IP address. Most teams lose all of that at the handoff between the ad platform and the messaging tool. Here it survives into the thread, which means the question of which campaign produced a WhatsApp conversation has an answer inside the messaging platform itself.

The second structural fact decides how every flow on this connector is shaped. Mumble runs on Meta's official WhatsApp Business Platform, so free text is bounded by the 24 hour customer service window and template messages are the only way to open a conversation outside it. Send Text Message and both media actions return an error once the window has elapsed. Is Conversation Active exists precisely so a flow can branch instead of finding out by failing. That branch is not a defensive nicety, it is the core control flow of any serious WhatsApp automation, and an agent that checks it first behaves like an operator who knows the platform rather than one who is discovering it in production.

Around that core sit the parts that make routing possible. Customers carry labels for segmentation, a conversation status that Mumble validates server side, and an assignment to an agent, a team, or a chatbot addressed by its bot token. Media can go out either as a URL that Mumble fetches server side or as bytes uploaded through the connector when the file is not publicly reachable. Templates are listed and created through the same surface, with body placeholders written as numbered variables and matching example values. There are no triggers, because Mumble publishes no webhook subscription endpoint, so inbound activity is read with Get Message and Get Conversation rather than pushed.

Without FlowRunner

Attribution dropped at first contact The click identifier that produced a lead is lost the moment the phone number is copied into a messaging tool

The session window is guessed A free text reply is attempted hours late, comes back rejected, and nobody can see from the log why

Templates written under campaign pressure Someone opens the console mid launch, writes a template, and waits on approval while spend is already running

With FlowRunner

Attribution carried into the thread Every UTM parameter and ad platform click identifier is written with the customer record at creation

The window is checked, then branched on The flow reads Is Conversation Active and picks a session message or a template message accordingly

Template submissions are deliberate A new template reaches WhatsApp review only after a person has agreed it needs to exist

Use Case Scenarios

The lead that keeps its provenance

A performance marketing team runs WhatsApp as its first touch channel. A form fill arrives from Facebook Lead Ads or a click from Google Ads, and the agent immediately calls Add Customer with the phone number as identity and every attribution field the click carried. It then calls Is Conversation Active, sees no open session, and sends an approved opener with Send Template Message With Variables. Add Customer To Label tags the record with the campaign so later segmentation is possible. When the customer replies, the window opens and the agent switches to Send Text Message for the rest of the exchange. Weeks later, when someone in HubSpot asks which creative produced the closed deals, the answer is on the Mumble customer record rather than reconstructed from timestamps.

Inbound routed to the right desk, not the first free one

Support conversations arrive through several products and need different owners. The agent reads Get Conversation for the thread and classifies the intent, then routes on what it found. Assign Customer To Agent when a named owner already holds the relationship, Assign Customer To Team when the question belongs to a queue, and Assign Chatbot when the request is one the automated flow handles end to end. Update Conversation Status moves the record into whatever state the account uses for triage, and Add Customer To Label records the reason so reporting can count it later. List Agents, List Teams, and List Chatbots keep the routing table honest, because they read the account's current roster rather than a hardcoded map that drifted six months ago. Escalations land in Slack with the thread already attached.

Order updates that respect the window

An ecommerce operator sends fulfillment updates over WhatsApp. A shipment event fires in Shopify, and the agent looks the customer up with Get Customer, then calls Is Conversation Active. If the window is open, Send Text Message carries the update as ordinary conversation. If it has closed, Send Template Message With Variables delivers the same content through an approved utility template with the tracking number interpolated. Send Media Message From File attaches the packing document when the file lives behind an internal URL that Mumble could not fetch itself. The point of the branch is that the customer receives one coherent stream of updates, while the platform's rules about who may speak first are respected on every send.

Human-in-Loop Highlight

The gate on Mumble is Create Template, and it is a different kind of gate from anything in the send path. A template is not a message. It is a standing account asset that Mumble submits to WhatsApp for review, that comes back with a PENDING status and becomes sendable only once WhatsApp approves it, and that is then used to open conversations with every customer the account reaches outside the 24 hour window. This connector exposes List Templates and Create Template. It does not expose a way to withdraw one. So an agent that writes templates on demand is not producing a draft, it is enrolling the account in a permanent piece of vocabulary, chosen under campaign pressure, reviewed by a third party.

That is why the agent stops here and nowhere else in the campaign path. When it finds no approved template covering the message a campaign needs, it assembles the case and posts it into Slack: "Winback campaign needs an opener for lapsed customers. No approved template matches. Closest existing templates from List Templates are order_update_v2 and cart_recovery_v1, both UTILITY, neither fits a promotional offer. Proposed new template winback_q3, category MARKETING, body: Hi {{1}}, your {{2}} plan has been inactive since {{3}}. Reply here and we will reactivate it. Example values attached. Category MARKETING is a permanent property of this template and this connector has no delete. Submit to WhatsApp review, or reuse cart_recovery_v1 with different variables?"

The digital andon cord is pulled at the point where the agent would otherwise commit the account to something it cannot take back, which is exactly where human-in-the-loop earns its keep under Orchestration as a Service. One other operation belongs on the same side of the line for its own reason. Delete Customer is permanent and takes the phone number, which is the record's identity, and Add Customer rejects a number that already exists rather than merging it. A cleanup agent that deletes and recreates therefore destroys the attribution and conversation history it was supposed to be tidying, and there is no recreate path that brings them back.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via Slack

Human decides

Agent resumes with decision

Agent Capabilities

27 actions

Customers

Add Customer Creates a customer record keyed by phone number, carrying contact details plus the full marketing attribution set in a single call: UTM parameters, click identifiers from the major ad platforms, Google Analytics identifiers, and the originating page, user agent, and IP address. A chatbot can be assigned at creation through its bot token. A number that already exists is rejected rather than merged.
Edit Customer Updates an existing customer by phone number, changing only the fields supplied and leaving everything else at its current value. Alongside the standard contact and attribution fields it writes arbitrary key value pairs as custom fields, with a per account ceiling on how many distinct custom fields may exist.
Delete Customer Permanently removes a customer record by phone number. Because the phone number is the identity and creation refuses duplicates, this is not a step in a recreate cycle. Treat it as the end of a record rather than a way to refresh one.
Get Customer Retrieves one customer by phone number, returning contact details, attribution, labels, assignment, and the conversation status the record currently carries.
List Customers Returns the workspace's customers in fixed size pages and reports the total page count, which is what a full sync or a segment rebuild iterates over.
Update Conversation Status Sets the conversation status on a customer record. Mumble validates the value server side and rejects an unknown one, and it does not publish the full set of statuses, so read a live record to see what the account is using.
Assign Customer To Agent Hands the conversation to a named human agent, which is the routing call when the relationship already has an owner.
Assign Customer To Team Hands the conversation to a team queue, which is the routing call when the question belongs to a desk rather than a person.

Labels

Create Label Creates a label used to segment customers for targeting and reporting.
Delete Label Removes a label from the account. Labels are addressed by name throughout the API, so a rename and a delete are not the same operation.
List Labels Returns every label on the account, which is how a flow validates a label exists before trying to attach it.
Add Customer To Label Attaches a label to a customer, recording campaign membership or triage reason on the record itself.
Remove Customer From Label Detaches a label from a customer while leaving the label in place for everyone else carrying it.

Messaging

Send Text Message Sends free text into an open conversation. This is a session message, so it succeeds only while the 24 hour window is open and returns an error once it has closed. Check the window first rather than treating the failure as the check.
Send Media Message From URL Sends an image, video, audio file, or document by handing Mumble a publicly reachable URL that Mumble fetches server side. Also a session message, bound by the same window.
Send Media Message From File Downloads the bytes from a source and uploads them to Mumble directly, which is the right action when the file sits behind authentication and Mumble could not fetch it itself. The accepted extension list is enforced before the request is issued.
Send Template Message Sends an approved template with no variables. Template messages are the only way to open a conversation outside the 24 hour window, which makes this the action that starts contact rather than continues it.
Send Template Message With Variables Sends an approved template with per recipient values interpolated into its numbered placeholders. This is the workhorse for order confirmations, appointment reminders, and any opener that has to carry customer specific detail.

Conversations

Get Message Retrieves a single message by its identifier, including its delivery state. With no webhook surface to subscribe to, this is how a flow follows up on a send it made.
Get Conversation Returns the message history for a customer's thread, which is the context an agent reads before it classifies, routes, or replies.
Is Conversation Active Reports whether the 24 hour session window is currently open for a customer. This is the branch point of every well built Mumble flow: open means free text is allowed, closed means a template is required.

Team and Automation

List Agents Returns the account's human agents with their identifiers, which is what an assignment step resolves a name against.
List Teams Returns the account's teams, used the same way for queue based routing.
List Chatbots Returns the account's chatbots and their bot tokens.
Assign Chatbot Attaches a chatbot to a customer by bot token, handing the conversation to automated handling instead of a person.

Templates

List Templates Returns the account's message templates. Run this before proposing a new one, because the useful question is usually whether an approved template already covers the case.
Create Template Submits a new message template for WhatsApp review and returns immediately with a template identifier and a pending status. The template is not sendable until WhatsApp approves it, its category is fixed at submission, and this connector offers no way to withdraw it afterward.

Frequently Asked Questions

What can FlowRunner do with Mumble?

FlowRunner agents can run Add Customer, Edit Customer, and Delete Customer in Mumble, plus 24 more actions.

Does connecting Mumble to FlowRunner require OAuth?

No. Mumble connects to FlowRunner with an API key, no OAuth flow required.

Can Mumble trigger a FlowRunner workflow automatically?

Mumble doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Mumble

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us