Nametag Integration for Workable

Overview

The Nametag and Workable integration verifies candidate identities directly in your Workable hiring pipeline. When a recruiter moves a candidate into a stage you choose (for example, a dedicated Identity Verification stage), Nametag sends the candidate an identity verification request and records the result back on the candidate’s Workable profile.

Nametag stores no candidate personal data from Workable beyond the verification result — only an opaque binding between the Workable candidate and the Nametag verification is kept.

How it works

1. A recruiter moves a candidate into the configured trigger stage in Workable.
2. Workable sends Nametag a signed candidate_moved webhook.
3. Nametag creates an identity verification request and posts the verification link to the candidate’s Workable timeline.
4. The candidate completes verification with Nametag (government ID + live selfie).
5. Nametag writes the result back to the candidate’s Workable profile: an Identity Verification Status custom attribute and a timeline comment, plus any optional actions you enable.

Prerequisites

Before setting up the integration, ensure you have:

1. An active Nametag account with the Workable integration enabled.
2. Admin access to your Workable account.
3. A pipeline stage to trigger verification (you should use a dedicated Identity Verification stage), and a candidate custom attribute named Identity Verification Status to receive the result.

Setup

Step 1: Add the integration

1. In the Nametag Console, go to Configure → Integrations.
2. Select Add Integration and choose Workable.

Step 2: Connect Workable

1. In the wizard’s Connect Workable step, enter your Workable subdomain (for example, acme-corp for acme-corp.workable.com).

2. Generate a Workable account access token (in Workable: Settings → Integrations → API access tokens) with the scopes to read jobs and candidates and to write candidates and comments, and paste it into the wizard.

   You are authorizing Workable — you never enter a Nametag API key during setup. The Workable token is also used to verify the authenticity of Workable’s webhooks.

Step 3: Choose coverage

Pick the jobs (all jobs, or specific ones) and the trigger stage. When a candidate is moved into that stage, Nametag begins verification.

Step 4: Set the rules

• Result attribute — the Workable custom attribute that receives the verification status (Verified / Failed / Expired).
• Timeline comment — post the result as a comment on the candidate (on by default).
• Tag on pass — add a Nametag Verified tag when a candidate passes (optional).
• Advance on pass — move the candidate forward when they pass (optional).
• Disqualify on fail — off by default. Automatically disqualifying candidates carries legal and fairness risk; enable only with review.

Step 5: Review and activate

Confirm your choices and activate. Nametag creates a candidate_moved webhook subscription in Workable, filtered to your configured stage.

Managing the integration

From the integration’s detail view you can see its status, coverage, and result-handling configuration, edit the coverage and rules, and Disconnect. Disconnecting removes the Workable webhook subscription and turns the integration off.

Data handling

Workable’s candidate webhook payload is rich with personal data. Nametag routes every event through a single sanitizer that keeps only the candidate id, job shortcode, stage, and account subdomain. No name, email, phone, address, or résumé from Workable is ever stored or logged. The only candidate identifier Nametag persists is the binding label workable:<subdomain>:<candidate_id>.