Move from Trengo to Rinhelp
By Wilbert Liu, founder of Rinhelp · Facts checked · Markdown for AI agents
Trengo tickets with their messages and internal notes, your customers and your quick replies all come out of Trengo’s API. It allows 120 requests a minute, and each email needs an extra call for its original HTML, so a big history takes hours.
| Conversations | Time to read them from Trengo |
|---|---|
| 1,000 | about 25 minutes |
| 10,000 | about 4 hours |
Limit used: 120 requests a minute (Trengo’s one stated limit, no plan named), about 3 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. Create the Trengo API key as a teammate who can see every ticket, because the ticket list only shows what the key’s user may see. Then give the AI agent your public Trengo help center address, since 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.
Help me start my Trengo move with https://rinhelp.com/migrate/trengo.md. Trengo has no MCP, so I’ll paste my quick replies for you to add as saved replies, then read my public Trengo help center and set up the same articles in Rinhelp.
Follow https://rinhelp.com/migrate/trengo.md to bring every Trengo ticket into Rinhelp. Call https://app.trengo.com/api/v2 with the API key I give you, list open, assigned and closed tickets, and fetch each email message’s original HTML. When you hit the 120-a-minute limit, wait the seconds Trengo names.
Their words and ours
| In Trengo | In Rinhelp |
|---|---|
| Ticket | Conversation |
| Message | Message |
| Note | Note |
| Contact | Customer |
| Quick reply | Saved reply |
What stays behind
- Journeys and automations
- Channels and WhatsApp templates
- Reports
- Boards
Trengo facts that shape the move
Trengo allows 120 API requests a minute. Source, checked .
Going over Trengo’s limit returns an error that says how many seconds to wait. Source, checked .
Trengo lists tickets page by page, filtered by open, assigned, closed or invalid. Source, checked .
Trengo’s ticket list only shows tickets the API key’s user may see, so a key from a restricted teammate gives a partial history. Source, checked .
Each Trengo ticket’s messages come from their own call, 20 at a time, with inbound, outbound and internal notes together. Source, checked .
A Trengo message shows an attachment’s file name and caption, but the messages page gives no download link or how long one lasts. Source, checked .
Trengo’s quick replies have their own API at /quick_replies, each with a title, a message and a type. Source, checked .
The original HTML body of a Trengo email needs one extra call per message. Source, checked .
The only help center call in Trengo’s API updates its settings, with no way to list articles. Source, checked .
Questions
Why are some Trengo tickets missing after the import?
The API key only sees the tickets its user may see in Trengo. Make the key as a teammate with access to every ticket and run the import again.
Do my Trengo quick replies come across?
Yes. The AI agent reads them from /quick_replies, and they arrive in Rinhelp as shared plain-text saved replies.
How do my Trengo help center articles move?
Trengo’s API can’t list them, so the AI agent reads your public help center pages and recreates each article, and links to your old Trengo pages redirect to them.