Move from eDesk to Rinhelp
By Wilbert Liu, founder of Rinhelp · Facts checked · Markdown for AI agents
eDesk tickets, their messages and notes, and your Templates can all be read out of eDesk’s API. The catch: eDesk only gives API tokens to accounts on the Enterprise plan, so check your plan before you set a date.
| Conversations | Time to read them from eDesk |
|---|---|
| 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 4 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. An eDesk Admin on the Enterprise plan creates a read-only API token for the AI agent. On a lower plan you upgrade, or ask eDesk, before anything can move.
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/edesk.md and help me with the small part of my eDesk move. eDesk has no official MCP, so I’ll upload the export file my coding agent built from eDesk’s API and paste my Templates. Add the Templates to Rinhelp as saved replies.
Every eDesk ticket since we started should end up in Rinhelp, following https://rinhelp.com/migrate/edesk.md. Use the read-only eDesk API token I give you, walk the tickets in order of last update, and read every message by its ID. Download each file as soon as you read its message, because eDesk’s links stop working after an hour.
Their words and ours
| In eDesk | In Rinhelp |
|---|---|
| Ticket | Conversation |
| Message | Message |
| Note | Note |
| Template | Saved reply |
What stays behind
- Automations
- Order and marketplace connections
- Reports
- Template rules (auto-send settings)
eDesk facts that shape the move
Only an Admin on eDesk’s Enterprise plan can create an API token. Source, checked .
An eDesk token can be read-only, which is all a move needs, since it can only get data out. Source, checked .
eDesk’s ticket list filters by last-updated date and sorts by id, created date or last update, so the whole history can be walked in order. Source, checked .
Reading an eDesk ticket returns only the IDs of its messages, so each message takes a call of its own. Source, checked .
An eDesk message read returns its details, and the message can be an internal note. Source, checked .
eDesk’s attachment links are pre-signed and expire after 1 hour; reading the message again gives a fresh link. Source, checked .
Files hosted by a channel such as Instagram follow that channel’s own expiry, which can be sooner than eDesk’s hour. Source, checked .
eDesk lists every Template with GET /templates, including its text, channels and attachments. Source, checked .
Questions
Can I leave eDesk without the Enterprise plan?
Not through the API. eDesk only lets an Admin on Enterprise create a token, so on a lower plan you upgrade or ask eDesk first.
Why does an eDesk move take more calls than most?
A ticket read gives only message IDs, so the AI agent reads each message on its own, about four calls per conversation. eDesk publishes no rate limit, so the finish time can’t be worked out ahead.
Will files from Instagram messages come across?
Only if the AI agent downloads them fast. eDesk’s links last an hour and a channel like Instagram can expire its own sooner. Files up to 50 MB each come across when caught in time.