Move from Groove to Rinhelp
By Wilbert Liu, founder of Rinhelp · Facts checked · Markdown for AI agents
Groove’s JSON export carries all your conversations, and its older REST API reads tickets and their attachments. Large exports can take up to 72 hours, and Groove publishes no API rate limit.
| Conversations | Time to read them from Groove |
|---|---|
| 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), 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. The Groove account owner or an admin requests the export under “Settings” → “Company” → “More” → “Exports”, then saves the file from the same signed-in browser, since the link won’t work for anyone else. Groove saved replies have no API, so copy them by hand.
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/groove.md, then bring the conversations from the Groove JSON export I upload into Rinhelp. Check a few first, since Groove doesn’t say whether notes and attachments are in the file, and read my public “Knowledge Base” pages for the help center.
Follow https://rinhelp.com/migrate/groove.md for my full Groove history: start from the JSON export, and fill gaps from the REST API with my access token as a Bearer header. Tickets list 50 a page, and each message lists up to 25 attachments of up to 20 MB. Groove publishes no rate limit, so slow down at the first refusal.
Their words and ours
| In Groove | In Rinhelp |
|---|---|
| Ticket | Conversation |
| Contacts | Customer |
| Agents | Teammate |
| Knowledge Base | Help center |
What stays behind
- Rules and workflows
- Reports
- Widget settings
- Customer satisfaction ratings
Groove facts that shape the move
A Groove owner or admin requests a full JSON export of all conversations under “Settings” → “Company” → “More” → “Exports”. Source, checked .
Groove exports JSON only, with no CSV. Source, checked .
A large Groove export can take up to 72 hours, and only one request can run at a time. Source, checked .
Groove’s export download link stops working when shared with someone else. Source, checked .
Groove’s export page doesn’t say whether notes and attachments are in the file, so check a sample first. Source, checked .
Groove’s REST API is no longer developed, and its newer GraphQL API still lacks finished Inbox and “Knowledge Base” parts. Source, checked .
Groove’s REST API takes an access token as a query parameter or a Bearer header. Source, checked .
Groove’s REST ticket list returns at most 50 a page and can filter by state. Source, checked .
Groove lists attachments per message with a link, up to 25 per message and 20 MB each. Source, checked .
Questions
My Groove export link doesn’t open for the AI agent. Why?
Groove makes the link personal, so it fails for anyone else. Download the file in the browser where you’re signed in to Groove, then upload it to your AI agent.
How long until my Groove export is ready?
Groove says a large export can take up to 72 hours, and you can have only one request at a time. Start it early, and set up your Rinhelp help center while you wait.
Will my Groove attachments come across?
Yes. Groove’s files are at most 20 MB each, well under Rinhelp’s 50 MB per file, and the AI agent downloads them from each message’s links.