In short: A webhook is a request Mumble sends to your system (CRM, BI, ticketing) the moment something happens. Mumble has four ways to do this. For most needs, start with the automation webhook.
The four options
| Option | When it sends | Best for |
|---|---|---|
| Account webhook | Every incoming customer message | Copying all incoming messages to another system |
| Automation webhook | When an automation’s trigger and conditions match | Specific events, like a chat closed or a customer added to a list |
| HTTP node in a chatbot | When the chatbot reaches that step | Getting or sending data at a fixed point, like checking an order status |
| HTTP action in Dolores AI | When Dolores decides the chat matches your description | Cases that need understanding, like “the customer wants to cancel” |
Only the chatbot HTTP node can use the reply from your system later in the conversation. The other options only send data out.
Set up the account webhook
- Go to Settings > Technical Profile.
- In Forward message to Webhook (
העבר הודעה אל Webhook), paste your URL. - Click Update details.
Mumble sends a fixed JSON format with the customer, the message and a timestamp. It doesn’t send delivery status, status changes or list changes.
Set up an automation webhook
- Open Automations and click +.
- Choose a trigger, for example Conversation status changed, and add conditions.
- Under actions, choose Send Webhook and enter your URL.
- Build the payload: each row is a key and a value. A value can be fixed text or a variable, like the customer’s name or phone.
- Save and set the automation to Active.
Automations run only on new events, not on past ones. Each run counts toward your plan’s monthly automation quota. More in Automations in Mumble.
Keep it safe and reliable
- Use HTTPS only and keep the URL private.
- Add a secret key to the payload and reject requests that don’t have it.
- Test first with a service like webhook.site to see exactly what Mumble sends.
- Don’t rely on webhooks alone for critical data. Add a periodic sync through the API as a backup.
Common questions
The webhook doesn’t reach my system
Check the URL from outside your network, that it uses HTTPS, and that the automation is active. Then check your system’s logs, since Mumble shows request logs only for the chatbot HTTP node (the Logs button on the canvas).
Can I get delivery status (delivered, read, failed)?
None of the four options sends it. For campaigns, see the campaign report.
The format doesn’t match what my system expects
The account webhook format is fixed, so adapt your system. In an automation webhook, edit the key and value rows.
My system matches customers by phone number only
WhatsApp is adding usernames, and some users may reach businesses without a visible phone number. Plan for records that arrive without one.