Connect Workable to Rig

    Sync your Workable recruiting data into Rig, from candidates and jobs to the activity on each candidate and your pipeline stages. Connecting takes your subdomain and an API access token with two read scopes.

    Before you start

    • You need permission to generate an API access token in your Workable account.
    • Know your subdomain. For acme.workable.com it is acme.

    Step 1: Generate a Workable access token

    1. Sign in to Workable and open the menu at the top right, then choose Integrations.
    2. Click Generate new token.
    3. Tick the r_jobs and r_candidates scopes. Scopes are fixed when you create the token.
    4. Copy the token. Workable shows it once.

    Both scopes matter
    A token missing a scope gets a 403 on that endpoint, and a 403 fails the whole sync. Tick both scopes when you create the token.

    Step 2: Connect it in Rig

    Adding a source needs a workspace owner, or a role with the Manage connections permission, on a workspace where you manage your own connections. If the Connectors tab says “Data ingestion for this workspace is managed by Rig”, ask an owner or Rig support to add the source.

    1. In Rig, open Connections, choose the Connectors tab and go to Sources & actions.
    2. Search for Workable, open the card and click Connect.
    3. Workable subdomain: The first part of your Workable address, such as acme. Pasting the full URL also works.
    4. API access token: Paste the token you generated.
    5. Click Continue. Rig checks the credentials and lists the streams it can reach, so choose the ones you want and click Connect.
    6. The source then syncs on its schedule, which is nightly unless you change it. To load data straight away, click Sync on its row; Test pulls a small sample first if you want to check the connection.

    What Rig pulls in

    Workable lands in its own workable schema in your warehouse:

    • Candidates: every candidate in your account.
    • Jobs: your job postings.
    • Candidate activities: the activity log on each candidate.
    • Reference data: members, recruiters, pipeline stages, custom attributes and disqualification reasons.

    Good to know

    • Workable's API takes the subdomain in the address, so a wrong subdomain shows up as a connection failure.
    • Stages and disqualification reasons return in a single page. Members, recruiters and custom attributes page through the API as lists grow.
    • Candidates and jobs sync incrementally after the first load.
    • To disconnect Workable, click the bin icon on the source's row under Sources & actions. Only whoever connected the source or a workspace owner can do this, and data already synced stays in the warehouse.

    What people use this for

    • Measure the hiring pipeline
    • Understand why candidates are rejected
    • Review recruiter activity

    More ideas for using Workable

    Was this guide helpful?