ChatWoot is an open-source helpdesk: one place where a team answers the customers who write in from a website widget, WhatsApp, email, Instagram and the rest. Teams run it on their own server or on ChatWoot's cloud, and plenty of them already had it long before they had us.
Connecting it takes two things a member pastes once, on the rooms page: the address of their ChatWoot dashboard and an administrator's access token. Nothing of ours is installed in it; one webhook is added so the team's answers come back, and letting the connection go removes that webhook again.
What the connection is good for
- A project room can be a conversation in it: what the team says in ChatWoot reaches the room, and what the room says reaches ChatWoot.
- The MakeHybrid ChatWoot API at /chatwoot/v1 reaches the same connection: its inboxes, its conversations, what was said in them, the answer you send and whether a conversation is open, pending, snoozed or resolved.
- An AI agent — yours, in a room, or any assistant that speaks MCP — can do the same through one address, and is told the same 404 for anything that is not your organization's.
ChatWoot's own activity lines — "Conversation was marked resolved" and the rest — are left out of what the API answers. They are the tool talking about itself, not anybody's words.
Questions people ask
Is this a different inbox from the MakeHybrid Inbox API?
Yes. The Inbox API is a shared inbox we run for you. This is YOUR ChatWoot, where it already is, with its own data and its own agents; we only reach it with the token you pasted.
Does it count as a seat?
Yes — one connected ChatWoot account is one seat, the same way one LinkedIn account or one WhatsApp number is.
Who does an answer come from?
The user whose token the connection is. Send private true and it is a note only the team sees; anything else the customer sees.