Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Workable

Workable integration for Flows360 workflows.

CategoryHuman Resources
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 24, 2026

Overview

Connect Workable with Flows360

Workable integration for Flows360 workflows.

Use the Workable connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 7 actions and 1 trigger.

Available actions

  • Get Candidate
  • Get Members
  • Get Job
  • Get Stages
  • Move Candidate
  • Rate candidate
  • Custom API Call

Available triggers

  • New Candidate

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Workable
  • Package: @activepieces/piece-workable@0.2.0
  • Exact artifact digest: sha256:4267e2fe28a7b6063f3146a85c184e71958890a5f43b5477b7b3ede5d43fd403
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Get Candidate (getCandidate), Gets candidate's information. Classification: read.
  • Get Members (getMembers), Gets members of hiring team. Classification: read.
  • Get Job (getJob), Gets specific job deatils. Classification: read.
  • Get Stages (getStages), Gets stages in your recruitment pipeline stages. Classification: read.
  • Move Candidate (moveCandidate), Moves candidate to the specified stage. Classification: read.
  • Rate candidate (rateCandidate), Rates the candidate on workable. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Candidate, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects8
Supported actions7
Triggers1

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Access Token Required · protected credential

Supported objects

ObjectReadWriteNotes
Get Candidate Yes No Gets candidate's information.
Get Members Yes No Gets members of hiring team.
Get Job Yes No Gets specific job deatils.
Get Stages Yes No Gets stages in your recruitment pipeline stages.
Move Candidate Yes No Moves candidate to the specified stage.
Rate candidate Yes No Rates the candidate on workable.
Custom API Call Yes No Make a custom API call to a specific endpoint
New Candidate Yes No webhook trigger declared by the pinned package.

Supported actions

Get Candidate · Read

Gets candidate's information.

get_candidate · Risk: low · Retry: safe

Inputs

  • id · string · Required
Get Members · Read

Gets members of hiring team.

get_members · Risk: low · Retry: safe

Inputs

  • limit · number · Optional, Default is 50
  • role · string · Optional, Filter for member of specified role
  • shortcode · string · Optional, Shortcode of specific job
  • email · string · Optional, Filter for specific member by email
  • name · string · Optional, Filter for members of specified name (Exact Match)
Get Job · Read

Gets specific job deatils.

get_job · Risk: low · Retry: safe

Inputs

  • shortcode · string · Required, Shortcode of specific job
Get Stages · Read

Gets stages in your recruitment pipeline stages.

get_stages · Risk: low · Retry: safe

Inputs

  • shortcode · string · Required, Shortcode of specific job
Move Candidate · Read

Moves candidate to the specified stage.

move_candidate · Risk: low · Retry: safe

Inputs

  • id · string · Required, Id of candidate
  • member_id · string · Required, This person's Id is used to move the candidate to the next stage
  • target_stage · string · Required, Slug of stage target should be moved to
Rate candidate · Read

Rates the candidate on workable.

rate_candidate · Risk: low · Retry: safe

Inputs

  • id · string · Required, Id of candidate
  • member_id · string · Required, Id of member that is adding the rating
  • comment · string · Required, Comment about the scoring of the candidate
  • scale · string · Required, Select scale to rate candidate on
  • grade · number · Required, Thumbs scale: 0-2, Stars scale: 0-4, Numbers scale: 0-9
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

New Candidate · Webhook

Triggers when new candidate submits application. Can be filtered by specific job and/or hiring pipeline stage.

Inputs

  • shortcode · string
  • stage_slug · string

Setup

Setup

  1. Add the Workable connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-workable@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 7 actions and 1 trigger declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Workable connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-workable@0.2.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com