M+💬

Connect Chatwoot

Handle your WhatsApp & SMS conversations from your Chatwoot inbox — both ways, in real time.

This uses our ready-made bridge — a single container you drop into your Chatwoot docker-compose.yaml. No coding. Fill in a few values, run it, and you're done.
📱 Customer⇄ Mobile API Connect⇄ bridge⇄ 💬 Chatwoot

1 Create an API inbox in Chatwoot

This is the inbox your WhatsApp/SMS chats will land in.

  1. Chatwoot → Settings → Inboxes → Add Inbox
  2. Choose the API channel
  3. Name it (e.g. WhatsApp), set the Webhook URL to:
    http://mac-bridge:8080/from-chatwoot
    If your bridge runs elsewhere, use that host instead of mac-bridge.
  4. Open the inbox → Configuration tab → copy the Inbox Identifier 📋

2 Grab your two tokens

WhatWhere to find it
Chatwoot Access TokenChatwoot → Profile Settings → Access Token
Mobile API Connect keyPortal → API keys → + Create key (sk_live_…)

3 Add the bridge to your compose

Paste this one service into your Chatwoot docker-compose.yaml and fill the 4 values.

# add under: services: mac-bridge: image: mobileapiconnect/chatwoot-bridge:latest restart: always environment: # ── [mobileapiconnect] ── MAC_API_KEY: "sk_live_REPLACE_ME" MAC_CHANNEL: "whatsapp" # or "sms" # ── [chatwoot] ── CHATWOOT_BASE_URL: "http://rails:3000" CHATWOOT_ACCOUNT_ID: "1" CHATWOOT_INBOX_IDENTIFIER: "REPLACE_ME" CHATWOOT_API_ACCESS_TOKEN: "REPLACE_ME" ports: - "8080:8080" volumes: - mac_bridge_data:/data # and add under: volumes: mac_bridge_data:

Then start it:

docker compose up -d mac-bridge

4 Point your inbound messages at the bridge

So customer messages flow into Chatwoot.

  1. Portal → Integrations → + Add software → pick Generic
  2. Set the Outbound URL (we POST every inbound message here) to your bridge:
    http://YOUR_BRIDGE_HOST:8080/inbound
  3. Enable it. Done — incoming WhatsApp/SMS now appears in your Chatwoot inbox.
Tip: if Chatwoot and the bridge are on the same Docker network, agents replies reach it as http://mac-bridge:8080. For the inbound URL above, use a host/IP reachable from the public internet (or a tunnel) since our servers call it.

✓ What happens now

DirectionFlow
inbound Customer texts → Mobile API Connect → bridge → new conversation in Chatwoot
outbound Agent replies in Chatwoot → bridge → WhatsApp/SMS to the customer
✅ That's it. Your team now chats with customers over WhatsApp & SMS straight from Chatwoot — full history, multiple agents, all the Chatwoot features. No code, no servers of ours in the middle.
Works the same for other tools. Any helpdesk that can call a webhook in and receive one out (FreeScout, Zoho Desk, n8n, Make, your own app) connects with the exact same two URLs — /inbound and your reply webhook. See the developer docs and the rules guide.

All product names, logos, and brands are property of their respective owners. Use of these names does not imply any affiliation with or endorsement by them.