Skip to main content

​
Prerequisites

Before continuing, you should have already completed the following for this connector:
1

Configure the Connector

Enable the connector and set up its connector profile in your project. See Managing Connectors.

Connector Profile

Workable - API Key
2

Link an Account

Connect an account using StackOne Hub or Auth Link.

Link Account

Workable - API Key

​
How Workable webhooks are set up

There is no manual webhook setup in Workable — it is fully automatic. On connection, StackOne calls Workable’s POST /spi/v3/subscriptions endpoint once for each event you enable, using a delivery URL unique to this connection that carries a secret token. Workable then sends one HTTPS POST per event, StackOne routes it to your integration, and only the events you enable are dispatched. Disconnecting the account deletes the subscriptions.

  • No callback URL to copy, and no verification step to complete.
  • Connect with a Workable account whose API token has the relevant read scopes (r_candidates for candidate events, r_employees for employee events).
  • Only the events you enable in StackOne are subscribed in Workable and delivered.

​
Available webhook events

The following Workable events can be enabled. Only events selected in StackOne are subscribed in Workable and delivered.

1

Review candidate events

Fired for candidates in your recruiting pipeline (require the r_candidates scope).

  • Candidate Created (candidate_created) — Fired when a new candidate is created.
  • Candidate Moved (candidate_moved) — Fired when a candidate is moved to a different stage.
2

Review employee events

Fired for employees in Workable HR (require the r_employees scope).

  • Employee Created (employee_created) — Fired when an employee is created.
  • Employee Updated (employee_updated) — Fired when an employee record is modified.
  • Employee Published (employee_published) — Fired when an employee record is published.
  • Onboarding Completed (onboarding_completed) — Fired when an employee completes onboarding.
  • Time Off Updated (timeoff_updated) — Fired when a time off request is approved or reverted (delivered with an event_type of timeoff_request_approved or timeoff_request_reverted). Requires Workable’s paid Time Off module.

​
Inspect the delivery format

Workable sends each event as a single HTTPS POST with a JSON body. Top-level fields are id (the candidate or employee id), event_type (e.g. candidate_moved), resource_type (candidate/employee), fired_at (ISO 8601 event time) and data (the full resource). StackOne maps event_type to the event type, id to the record id and fired_at to the event timestamp, and passes the full body through as the event data. A single change can produce more than one event (for example, creating an employee fires both employee_created and employee_updated), and Workable retries failed deliveries, so design your integration to handle duplicate deliveries idempotently using the record id.

​
Verify

Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.