Connect your live chat to Zapier, Make, or n8n

You do not need a custom backend to plug muro into the rest of your stack. Automation platforms like Zapier, Make, and n8n are built to receive a webhook and call an API, which is exactly the two halves of the muro developer surface. Wire those two together and you can route chats into a spreadsheet, a CRM, a project tool, or a notification channel in minutes.

Two directions

There are two flows, and most useful automations use one or both. Inbound: muro sends an event to your automation when something happens (a new message, a visitor identifies themselves). Outbound: your automation calls the muro REST API to do something back, usually to send a reply.

Inbound: trigger a flow on a chat event

1. 01In your automation tool, create a flow that starts with a webhook or catch hook trigger. It gives you a unique URL.
2. 02In muro, open Settings, then Webhooks, and add an endpoint pointing at that URL.
3. 03Pick the events you care about: message.created, conversation.opened, visitor.identified, conversation.closed.
4. 04Send the test event from the webhooks page and confirm your flow fires.

muro signs every webhook with HMAC-SHA256 so you can verify it really came from us. Most automation tools let you add a verification step or a code node for this. The full contract, headers, and a constant-time verify are in our webhooks guide.

Zapier

Use a "Webhooks by Zapier" Catch Hook as the trigger, paste its URL into muro, and map fields like data.content and data.conversation_id into the action step (a new row, a Slack message, a CRM contact).

Make

Add a "Custom webhook" module, copy its address into muro, and run the scenario once so Make learns the payload shape. From there you drag the parsed fields into any of its hundreds of modules.

n8n

Drop a Webhook node, set it to POST, and use the production URL in muro. Because n8n can self-host, this is the privacy-friendly option: the event never leaves your own server before you decide where it goes.

Outbound: send a reply from your flow

When your automation needs to write back into the chat (an auto-acknowledgement, an answer assembled from another system) it calls the REST API. Add an HTTP request step with your mr_live_ key and POST to the conversation:

bashPOST https://muro.chat/api/v1/conversations/{id}/messages
Authorization: Bearer mr_live_xxxxxxxxxxxxxxxx
Content-Type: application/json

{ "content": "Thanks! A teammate will be with you shortly." }

A few flows worth stealing

• →New conversation, then a card on your project board with the first message.
• →Visitor identifies, then create or update the contact in your CRM.
• →Conversation closed, then append the transcript to a customer record.
• →Message contains "refund", then notify the billing channel instantly.

Webhooks out, REST in. With those two wired into an automation platform, muro becomes a node in your stack instead of a silo, and you never had to host a line of backend code.