Move from Gorgias to Rinhelp
By Wilbert Liu, founder of Rinhelp · Facts checked · Markdown for AI agents
Gorgias tickets, messages, macros and tags move to Rinhelp, and your articles come from your public help center. Gorgias can’t export articles, and an API key gets only about 120 requests a minute, so a big history takes time.
| Conversations | Time to read them from Gorgias |
|---|---|
| 1,000 | about 9 minutes |
| 10,000 | about 84 minutes |
Limit used: 120 requests a minute (API key, 40 per 20 seconds), about 1 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. Choose the Gorgias role your AI agent signs in with, because the MCP server can reply to customers as well as read. For the full history, someone creates an API key, or an OAuth2 app for twice the speed.
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.
Sign in to the Gorgias MCP server at https://mcp.gorgias.com/mcp through the browser and follow https://rinhelp.com/migrate/gorgias.md. Copy my macros into Rinhelp and my articles from the public Gorgias help center, and don’t send any replies in Gorgias.
Follow https://rinhelp.com/migrate/gorgias.md to import all my Gorgias tickets with an API key. List tickets 100 at a time by cursor, and pull messages from the main messages list filtered by ticket_id rather than the deprecated per-ticket call. Keep under 40 requests every 20 seconds, and bring a ticket whose snooze_datetime is still in the future in as open, since Gorgias will re-open it then.
What we measured
We imported the public help center at docs.gorgias.com into a test workspace with Claude Code on : 581 articles in 8 sections came across as drafts in about 6 minutes, were published in about 2 minutes more, and every old address answered with a redirect. 64 conversations with 200 messages, shaped like its API’s responses, came across with their files. The full run.
Their words and ours
| In Gorgias | In Rinhelp |
|---|---|
| Ticket | Conversation |
| Message | Message |
| Macro | Saved reply |
| Tag | Tag |
| Article | Article |
What stays behind
- Rules
- Views
- Satisfaction surveys
- Statistics
Gorgias facts that shape the move
A snoozed Gorgias ticket carries a snooze_datetime, the time Gorgias will re-open it. Source, checked .
A Gorgias API key gets 40 requests in each 20-second window, about 120 a minute. Source, checked .
An OAuth2 app gets double that: 80 requests per 20 seconds. Source, checked .
Enterprise accounts keep the same numbers over a shorter 10-second window. Source, checked .
Tickets list 100 per page at most, by cursor, ordered by created or updated time. Source, checked .
Messages are listed across tickets with a ticket_id filter, 100 per page at most. Source, checked .
The older per-ticket messages call is deprecated. Source, checked .
Gorgias only imports help center articles; there is no export, so they’re read from the public site. Source, checked .
The official Gorgias MCP server reads and replies to tickets, manages macros and drafts articles, on all Helpdesk plans. Source, checked .
The MCP server can write, so it should only get the Gorgias role you want it to have. Source, checked .
Questions
How long does a Gorgias import take?
With an API key, Gorgias allows about 120 requests a minute and each ticket needs about one, so plan on roughly 120 tickets a minute. An OAuth2 app doubles that.
How do my Gorgias articles get to Rinhelp?
Gorgias has no article export, so your AI agent reads them from your public help center. Old article links then redirect to the new Rinhelp articles.
Is it safe to connect the Gorgias MCP server for this?
Yes, as long as you sign in with a role that fits. It can reply to customers, so ask your AI agent only to read in Gorgias.