Skip to main content
Telara

Integrations / Workable

Workable logo

Workable

Workable applicant tracking system (ATS) for recruiting — jobs (requisitions) and candidates across the hiring pipeline.

API key
Indexes
Actions

What Telara does

Capability matrix

Before you connect

Prerequisites

A Workable account you can administer.
Admin who can generate an access token under Integrations.

Vendor setup

Get the credential

1
Open Integrations
In Workable, click the account menu (top right) → Integrations.
2
Generate a token
Click Generate new token. Copy it immediately — Workable shows it once. Also copy your account subdomain (the part before .workable.com).
3
Paste in Telara
Settings → Integrations → Workable. Paste the access token and the subdomain. The API is per-subdomain, not a global host.

In Telara

Connect in Telara

API key

Workable API token ("Access Token"), sent as a bearer token. Generate one in the Workable web app: account menu (top right) > Integrations > "Generate new token" — the token is shown once and must be stored immediately. Workable additionally requires a per-account subdomain: every request path is scoped to https://<subdomain>.workable.com/spi/v3, not a shared global host, so the subdomain (the part before ".workable.com" in the account's Workable URL, also visible in company profile settings) must be stored as its own non-secret credential field "subdomain" (e.g. "acmeco") alongside the secret "api_key". This is the same {placeholder}-in-base_url pattern already used by mailchimp.yaml's {server} and zendesk.yaml's {subdomain} — the auth engine only does whole-field template substitution into api.base_url, it cannot parse a value out of the token itself.

In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.

Fields Telara asks for
  • API key
  • Subdomain

Knowledge

What gets indexed

ResourceCoverage
JobPartial — not every record the vendor holds is synced
CandidatePartial — not every record the vendor holds is synced

Sync

Freshness & sync

ResourceLagDeletions
JobUp to 1 dayRemoved records disappear on the next full sync
CandidateUp to 1 dayRemoved records disappear on the next full sync

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

Excluded from semantic search: Job, Candidate.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

The wrong subdomain authenticates nowhere even with a valid token.
Sandbox accounts are different subdomains and different tokens.