Move from Re:amaze to Rinhelp
By Wilbert Liu, founder of Rinhelp · Facts checked · Markdown for AI agents
Re:amaze conversations with their internal notes and files, articles by topic and Response Templates all come across over the Re:amaze API. Ask for filter=all, because the conversation list hides every archived conversation unless you do.
| Conversations | Time to read them from Re:amaze |
|---|---|
| 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 (per API token, number not published), 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. Give the AI agent your Re:amaze login email, your own API token and the host name of each brand, since the API works one brand at a time. Afterwards, set each teammate’s role again in Rinhelp, because Re:amaze’s API doesn’t share staff roles.
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.
Re:amaze has no MCP or export file, so read https://rinhelp.com/migrate/reamaze.md and call the Re:amaze API with the login email and API token I paste here. Start with my Response Templates and articles, drafts included, then bring over a small batch of open and archived conversations.
Follow https://rinhelp.com/migrate/reamaze.md to copy every Re:amaze brand I have into Rinhelp. Sign in with my login email and API token, list conversations with filter=all, 30 per page, and fetch each one’s messages, keeping visibility 1 as notes. Re:amaze publishes no per-minute number, so back off whenever it answers HTTP 429.
Their words and ours
| In Re:amaze | In Rinhelp |
|---|---|
| Internal note | Note |
| Contact | Customer |
| Staff | Teammate |
| Topic | Section |
| Response Template | Saved reply |
What stays behind
- Automations (workflows)
- Reports
- Satisfaction ratings history
- Status page
- Staff roles
Re:amaze facts that shape the move
The Re:amaze API signs in with your login email and a personal API token over HTTPS, and every staff user has their own token. Source, checked .
Each Re:amaze API request is scoped to one brand, chosen by the host name you call, so an account with several brands needs one pass per brand. Source, checked .
Re:amaze rate limits each API token per minute without publishing the number, and answers HTTP 429 when you go over. Source, checked .
By default Re:amaze lists only unarchived conversations, so a copy that skips filter=all quietly misses all closed history. Source, checked .
Re:amaze returns conversations and their messages 30 per page, moving on by page number. Source, checked .
Re:amaze mixes internal notes into the messages and marks them only with visibility 1, so the AI agent must keep those private. Source, checked .
Each Re:amaze message lists its attachments with a content type and download links. Source, checked .
The Re:amaze articles call returns only published articles unless you ask for draft or internal ones, and each article names its topic. Source, checked .
Re:amaze’s API doesn’t support its staff “Role” resource, so roles don’t come across. Source, checked .
Questions
Re:amaze shows only my open conversations. Where did the archived ones go?
Re:amaze leaves archived conversations out of its list unless the request says filter=all. Ask the AI agent to list again with that filter, and the closed history comes across too.
I run three brands in Re:amaze. Do I move each one separately?
Yes. Re:amaze picks the brand from the host name each request goes to, so the AI agent makes one pass per brand host with the same login email and token.
Will my internal notes show up as replies to customers?
No. Re:amaze marks an internal note with visibility 1, and the AI agent saves those as notes in Rinhelp, which customers never see.