Migrate from Workable: what moves, API key, limits
What Shuttio reads from Workable, where it lands in Ashby, Lever, Greenhouse, which permissions it needs and why, and what does not move.
Last updated: 20 November 2026
Shuttio connects to Workable with your account subdomain (the part before .workable.com in your account address) and an account API access token. A Workable admin makes the token under Integrations, Generate new token, and ticks the read scopes. Shuttio sends the token only to Workable's own addresses: your account address, https://<subdomain>.workable.com, and Workable file links. File links on other storage hosts are fetched without it.
Object by object: What objects are supported for Workable migrations.
What Shuttio reads and moves
- Jobs: all four states, draft, published, archived and closed, with the description, requirements, benefits, department, locations, salary range, the job's own stages and its hiring team with each member's role. Workable's closed state is a job used internally or confidentially, and the job's details say so.
- Requisitions: read when the account has the Hiring Plan. Each goes into its job's details, and its custom attributes become job fields.
- Members and recruiters: read so comments, ratings and events carry a name and an email. Departments keep their parent. Disqualification reasons become rejection reasons.
- Candidates: in Workable one candidate is one person on one job. A person who applied to two jobs has two candidate ids, and Shuttio reads each as a candidate with one application. The destination matches people by email, so both land on one candidate.
- Activity: a stage move with a target stage, or a stage action such as interview or offer, becomes a dated entry of the stage history. A comment becomes a note, a message becomes an email note, a rating becomes feedback. Any other action, for example offer-sent, is listed in one dated Activity note.
- Events: every event for the candidate, cancelled ones included, becomes an interview with its time, members, type and conference link.
- Offer: read for a candidate whose activity or stage shows an offer or a hire, with its state, its document fields and the dates of sending and decision taken from the activity. Offer documents move as files.
- Files: the resume and the candidate's files. A resume that is also in the files list is read once.
- Answers: the candidate's answers to the job's questions, with the question text from the job.
Where each thing lands
| Workable object | In Ashby | In Lever | In Greenhouse |
|---|---|---|---|
| Candidates | Its own object, or the one you already have with that name | Its own object, or the one you already have with that name | Its own object, or the one you already have with that name |
Notes, tasks, meetings, calls, files, owners and lists depend on the destination. This is the row for Workable, generated from the same tables the runner uses:
Into Ashby
| From | Objects | Notes | Tasks | Meetings | Calls | Emails | Files | Owners | Lists |
|---|---|---|---|---|---|---|---|---|---|
| Workable | Candidates | Yes | No | No | No | No | Yes | Yes | No |
Into Lever
| From | Objects | Notes | Tasks | Meetings | Calls | Emails | Files | Owners | Lists |
|---|---|---|---|---|---|---|---|---|---|
| Workable | Candidates | Yes | No | No | No | No | Yes | Yes | No |
Into Greenhouse
| From | Objects | Notes | Tasks | Meetings | Calls | Emails | Files | Owners | Lists |
|---|---|---|---|---|---|---|---|---|---|
| Workable | Candidates | Yes | No | No | No | No | Yes | Yes | No |
In Ashby, Lever and Greenhouse, notes and files move with the candidate; interviews and offers are written as notes, offers as private notes.
Each destination's own article says how its data is written: Ashby, Lever, Greenhouse.
The API key and why
| What | Why Shuttio needs it |
|---|---|
| Account subdomain | Every request goes to https://<subdomain>.workable.com. Shuttio accepts a pasted address and reduces it to the subdomain. |
| An account API access token | Workable's OAuth 2.0 needs a registered partner app, so a pasted token is the only way to connect. Shuttio sends it as a Bearer token. It checks r_jobs, r_candidates and r_account with one request each before it saves anything; r_requisitions is checked during the run. |
| r_jobs | Jobs, stages, members, recruiters, events and disqualification reasons. A token Workable refuses for r_jobs is refused at connect. |
| r_candidates | Candidates, their activity, files and offers. Without r_candidates nothing can be moved; make the token with it. |
| r_account | Departments. Checked at connect. Without it departments are left out, and the run says so. |
| r_requisitions | Requisitions, which only accounts with the Hiring Plan have. Not checked at connect. Without it they are left out, and the run says so. |
A token that lacks r_candidates or r_account but can read jobs still connects, and the connect step names what is missing. During the run, a missing r_account or r_requisitions is named in the run's warnings.
What Workable's API does not give
- EEO answers: Workable's API reference has no endpoint to read them, so none move.
- The talent pool: the reference has no endpoint to read it either, so only candidates attached to a job move.
- Shapes the reference does not spell out: it shows how to post an answer but not how a read answer looks, and it does not describe a rating's fields. Shuttio reads each answer shape it can recognise (text, choices, yes or no, date, number, file name) and writes a rating as plain lines of name and value.
- Stage history comes from the activity list only. A stage that no activity names does not appear in the history; the candidate's current stage is still set.
- Files: Workable links to files are signed and expire. Shuttio asks for a fresh link once when one has expired. A file over 30 MB is not copied.
Known limits
- Rate limit: an account token may make 10 requests in 10 seconds, so Shuttio sends one a second and speeds up only when a response reports a higher limit. On a 429 it waits for the next interval. After five refusals, or a wait over a minute, the run pauses until you resume it.
- Time: a large account takes hours, and the run pauses when Workable asks it to slow down.
Not answered here? Email help@shuttio.com.