How does OCNORA authenticate with Workable?

With a stored Bearer token credential, shaped the Workable SPI access token or the access token, or {"token": "…"}. A connection test can check it when you add it.

What can I automate with Workable?

3 typed operations and 1 trigger, each with a reference page listing its config fields and the shapes it emits.

What if the Workable operation I need is not listed?

Where Workable has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.

Are there templates that use Workable?

Not yet. Start from a blank workflow, or describe the workflow to Build with AI.

How are Workable calls controlled?

Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.

Workable

Business appsBearer tokenConnection test available

Jobs and candidates on Workable.

OCNORA ships 3 typed Workable operations and 1 trigger. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.

Ask about Workable

Before you connect Workable

Authentication

Bearer token

Credential

the Workable SPI access tokenthe access token, or {"token": "…"}

Connection test

Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.

Prerequisites

The token needs the r_candidates scope for candidate events and r_employees for employee ones. It is also the key Workable signs deliveries with, so rotating it invalidates the signature until the workflow is published again. Publishing needs MANTLE_APP_PUBLIC_BASE_URL set to an https URL Workable can reach.

Prerequisites are taken from the connection notes in this provider’s node contracts; each node’s reference page says which apply to it.

What you can do with Workable

Operations, grouped by what they do to your data, plus 1 trigger that start a run.

Read and search 3

A sample Workable workflow

1
Eventtrigger.workable_event
Start a run when Workable raises an event (candidate, employee, job).
2
Get Candidateworkable.get_candidate
Fetch one candidate.

An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.

Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.

Triggers 1

Event
Start a run when Workable raises an event (candidate, employee, job).
trigger.workable_event

Operations 3

Workable questions

How does OCNORA authenticate with Workable?: With a stored Bearer token credential, shaped the Workable SPI access token or the access token, or {"token": "…"}. A connection test can check it when you add it.
What can I automate with Workable?: 3 typed operations and 1 trigger, each with a reference page listing its config fields and the shapes it emits.
What if the Workable operation I need is not listed?: Where Workable has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
Are there templates that use Workable?: Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
How are Workable calls controlled?: Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.

See your first Workable workflow run.

Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.

Book a technical demo Talk to sales