Move from Chatwoot to Rinhelp
By Wilbert Liu, founder of Rinhelp · Facts checked · Markdown for AI agents
Chatwoot conversations, their messages and your canned responses move through its Application API, and Chatwoot’s official CLI lets a coding agent do the reading. Ask for every status: by default the conversation list returns only open conversations.
| Conversations | Time to read them from Chatwoot |
|---|---|
| 1,000 | no per-minute limit to time it by |
| 10,000 | no per-minute limit to time it by |
Limit used: no per-minute number (no published limit for Chatwoot Cloud), about 2 per conversation. Rinhelp takes up to 3,000 conversations a minute.
Free. Importing never emails your customers, never runs Rin and never counts toward a plan.
Needs a person. You create a personal access token in Chatwoot’s Profile Settings, or sign in once to the Chatwoot CLI so the AI agent can run it. You also share your public Chatwoot help center address, because its articles can’t be listed through the API.
Paste one prompt
Connect your AI agent to Rinhelp first, then paste the prompt for the app you use. It reads this page’s Markdown and follows Rinhelp’s steps.
Read https://rinhelp.com/migrate/chatwoot.md. Chatwoot has no official MCP, so I’ll paste my canned responses for you to save as saved replies in Rinhelp, then copy the articles from my public Chatwoot help center.
Use the Chatwoot CLI and its agent skill, after I sign in once, to follow https://rinhelp.com/migrate/chatwoot.md. Where the CLI falls short, call the Application API with my personal access token. List conversations with status all so resolved ones come too, and page through each one’s messages.
Their words and ours
| In Chatwoot | In Rinhelp |
|---|---|
| Conversation | Conversation |
| Message | Message |
| Contact | Customer |
| Agent | Teammate |
| Portal | Help center |
| Canned response | Saved reply |
| Label | Tag |
What stays behind
- Automation rules
- Inbox and channel connections
- Reports
- Campaigns
Chatwoot facts that shape the move
Chatwoot’s Application API uses a personal access token made in Profile Settings. Source, checked .
Chatwoot lists only open conversations unless you ask for status all, so a default export misses resolved history. Source, checked .
Chatwoot returns a conversation’s messages in small pages: up to 20 older messages a call, or up to 100 when paging forward. Source, checked .
Chatwoot ships an official CLI and agent skill, so a coding agent can work in Chatwoot without an MCP server. Source, checked .
The Chatwoot agent skill reads conversations and messages, and reads help center articles when asked. Source, checked .
The Chatwoot CLI needs a one-time sign-in by you, because agents run its commands without prompting. Source, checked .
One Chatwoot call lists all canned responses with their short code and content. Source, checked .
Chatwoot’s public API lists portals and their article counts, and can add categories and articles, but has no call that lists the articles. Source, checked .
Self-hosted Chatwoot allows 3,000 requests a minute per IP by default, and Chatwoot Cloud states no limit. Source, checked .
Questions
Why did only my open Chatwoot conversations come across?
Chatwoot’s conversation list returns open ones unless asked for status all. Have the AI agent list again with status all, and resolved conversations follow.
Do I need an MCP server to move from Chatwoot?
No. Chatwoot’s official CLI and agent skill let a coding agent read conversations, messages and help center articles once you sign in a single time.
Does self-hosting Chatwoot change how fast it goes?
A self-hosted Chatwoot allows 3,000 requests a minute per IP by default, which is more than Rinhelp takes, so Rinhelp’s 60 calls of 50 conversations a minute set the pace. Chatwoot Cloud publishes no limit.