Move from tawk.to to Rinhelp
By Wilbert Liu, founder of Rinhelp · Facts checked · Markdown for AI agents
tawk.to chats, tickets and knowledge base articles can move through its REST API, but that API isn’t self-serve. Ask tawk.to for access before you pick a switch date, since credentials only arrive once it approves you.
| Conversations | Time to read them from tawk.to |
|---|---|
| 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. A property Admin asks tawk.to for REST API access and passes the API key to the AI agent once it’s approved. Until then, that Admin can export chats from the Inbox, 50 at a time.
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.
I exported my tawk.to chats from the Inbox as ZIP files of JSON, 50 chats each, and will upload them here. Follow https://rinhelp.com/migrate/tawk-to.md to bring them into Rinhelp, and add my tawk.to shortcuts, which I’ll paste, as saved replies.
Follow https://rinhelp.com/migrate/tawk-to.md to move my whole tawk.to history into Rinhelp. Call api.tawk.to over HTTPS with my approved API key as the Basic auth username, list chats and tickets, and list the knowledge base articles for my help center. tawk.to publishes no rate limit, so retry with backoff when it pushes back.
Their words and ours
| In tawk.to | In Rinhelp |
|---|---|
| Chat | Conversation |
| Ticket | Conversation |
| Property member | Teammate |
| Knowledge base article | Article |
What stays behind
- Triggers and automations
- Widget settings
- Reports
- Monitoring
tawk.to facts that shape the move
tawk.to’s REST API isn’t self-serve: you ask for access first. Source, checked .
Once approved, requests go to api.tawk.to over HTTPS with your API key as the Basic auth username. Source, checked .
tawk.to’s REST API lists tickets, chats and the property’s teammates with filters, and can create and list knowledge base articles. Source, checked .
A tawk.to move can’t start the same day you decide, because API access is approved before credentials arrive. Source, checked .
Without the API, an Admin exports chats from the tawk.to Inbox, 50 at a time. Source, checked .
A tawk.to export arrives as a ZIP of JSON files, and only a property Admin can make one. Source, checked .
tawk.to itself points larger exports to the REST API. Source, checked .
Questions
Can I start moving from tawk.to today?
Only by hand. The REST API needs tawk.to to approve your request first, so ask early. Meanwhile an Admin can export chats from the Inbox, 50 at a time.
Is the tawk.to Inbox export enough for a small history?
It works when the history is small: each export is a ZIP of JSON with up to 50 chats, and you upload them to your AI agent. For larger histories, tawk.to itself points to the REST API.
Do my tawk.to shortcuts move?
We found no API or export for shortcuts, so paste the ones you use. They come into Rinhelp as shared plain-text saved replies.