Introduction

Finding the best talent is the key to any successful organization, but it doesn’t stop at hiring – it’s just as important to support new hires, empower them to be productive and successful in their new role. Sapling provides significant improvements for your People Operations team and Hiring Managers, while completely streamlining the Candidate and Employee experience through the Workable Integration.

*Important note before starting setup* – in your Workable account, your hiring pipeline must include the stage Hired for the integration to Sapling to flow correctly (this stage is what triggers our webhook to pull candidate data in from Workable --> Sapling). This can be done by ensuring there is no stage_slug named “Hired" in the reporting pipeline.

How It Works

Setting up the Integration and Data Flow

Setting up the Integration Step-by-Step

Step #1. Retrieve your Workable API Key

  1. Navigate to Settings → Integrations

  2. Locate Employee Onboarding → Generate Token

  3. Copy your API Key (Partner Token)

Step #2. Enable the Workable Integration in Sapling

  1. Navigate to the Integrations → Applicant Tracking System → Workable

  2. Enter your Workable url and API key retrieved from Workable (For the url, you do not need to enter https://)

Overview

More than an applicant tracking system, Workable's talent acquisition software helps teams find candidates, evaluate applicants and make the right hire, faster.

Integration Fields

Sapling is continually expanding the number of fields that sync between Workable and Sapling. Here is a full list of the Workable to Sapling Integration fields:

  • First Name

  • Last Name

  • Job Title

  • Department

  • Location

  • Personal Email Address

  • Personal Phone Number

  • Start Date (the date the candidate was moved to hired)

Key Factors to be aware of

Field Names in Workable and Sapling

  • For the Fields to sync correctly, the field names and field option naming conventions must match between Workable and Sapling.

💡 Looking to do more?

Did this answer your question?