Move from Helpwise to Rinhelp
By Wilbert Liu, founder of Rinhelp · Facts checked · Markdown for AI agents
Helpwise conversations move through its API with a key and a secret, while saved replies and Knowledgebase articles have no API and come across another way. Skip the Export All Data file for the move: it cuts email text to 200 characters.
| Conversations | Time to read them from Helpwise |
|---|---|
| 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 key, number not shown on Helpwise’s docs page), 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. Copy both the API key and the API secret from Helpwise’s settings page and give them to the AI agent. You also paste your saved replies, since Helpwise only describes making them in the app.
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/helpwise.md first. I’ll paste my Helpwise canned responses for you to add as saved replies, and give you my public Knowledgebase address so you can copy its articles into my Rinhelp help center.
Follow https://rinhelp.com/migrate/helpwise.md to bring my full Helpwise history into Rinhelp. Send my API key and API secret together as a Basic auth header on every call, and watch the per-minute allowance in the reply headers so you slow down before Helpwise refuses.
Their words and ours
| In Helpwise | In Rinhelp |
|---|---|
| Conversation | Conversation |
| Saved reply | Saved reply |
| Canned response | Saved reply |
| Knowledgebase | Help center |
What stays behind
- Automations and workflows
- Connected inboxes and channels
- Reports
- CSAT surveys
Helpwise facts that shape the move
Helpwise’s API needs both an API key and an API secret, found on the Helpwise settings page. Source, checked .
Helpwise wants the key and the secret in every request, as a Basic auth header, so the key alone can’t connect an AI agent. Source, checked .
Helpwise’s limits apply per API key, and reply headers show the per-minute allowance and what’s left of it. Source, checked .
Going over Helpwise’s limit returns an error, and the caller has to slow down. Source, checked .
Helpwise’s Export All Data gives one row per event, with the conversation ID, message ID, action, subject and status. Source, checked .
The Export All Data file cuts email text to 200 characters, so it can’t carry real message bodies. Source, checked .
Helpwise calls saved replies canned responses too, and its help article only covers making them in the app. Source, checked .
Questions
Can I use Helpwise’s Export All Data file instead of the API?
Not for the move. It holds one row per event and cuts email text to 200 characters, so the real message bodies have to come through the API.
I only have my Helpwise API key. Is that enough?
No. Helpwise needs the API secret too, sent with the key on every call. Both are on the Helpwise settings page.
How do my Helpwise Knowledgebase articles move?
We found no API or export for them, so the AI agent reads your public Knowledgebase pages and recreates each article in your help center. Old links redirect to the new articles.