Nametag Integration for Breezy HR

Overview

The Nametag and Breezy HR integration lets organizations verify candidate identities directly inside their Breezy hiring pipeline. When a candidate reaches a stage you choose, Nametag verifies their government ID and a live selfie on their phone, then moves the candidate to a passed or failed stage in Breezy.

Nametag holds the verified identity — no personal data is ever stored in Breezy. Breezy only receives a pass/fail stage change and a note with a link back to Nametag.

Prerequisites

Before setting up the integration, ensure you have:

1. An active Nametag account with the Breezy HR integration enabled.
2. A Breezy HR Pro plan — the API and webhooks this integration uses are available only on Pro.
3. Webhooks enabled on your Breezy account. Webhooks are a Pro feature that Breezy support switches on for your account — this is a one-time request to Breezy.
4. A dedicated Breezy service account for Nametag to sign in as. Breezy does not use OAuth, so Nametag authenticates as this account. Use a dedicated account (not a personal one) so the connection stays stable.

Setup

The setup wizard in the Nametag Console walks you through every step. You can see the full set of steps up front.

Step 1: Connect Breezy

1. In the Nametag Console, go to Configure → Integrations.
2. Select Add Integration and choose Breezy HR.
3. Confirm the prerequisites above, then enter your Breezy service-account email and password. Nametag validates the credential and stores it encrypted. (You never enter a Nametag key here — Nametag already knows who you are.)

Step 2: Choose company and positions

Pick the Breezy company the gate applies to, then choose whether identity verification applies to all positions or a selected list.

Step 3: Map pipeline stages

Map three stages in your Breezy pipeline:

• Trigger stage — when a candidate reaches this stage, verification begins (for example, Identity Check).
• Passed → move to — where verified candidates go (for example, ID Verified).
• Failed → move to — where candidates who fail or need review go (for example, ID Review).

If these stages don’t exist yet, create ID Verified and ID Review stages in the Breezy positions you want to protect before mapping them.

Step 4: Delivery and activation

Choose how candidates receive the verification request (Email or SMS), then Activate. The connection becomes Connected. If Breezy has not finished enabling webhooks on your account yet, the status shows Webhooks pending and flips to Connected automatically once webhooks are on.

Day-to-day use

1. Move a candidate (or let Breezy move them automatically) into the trigger stage.
2. Nametag sends the candidate a verification request by your chosen channel.
3. The candidate scans their government ID and takes a selfie on their phone — typically under a minute.
4. When they finish, Breezy advances the candidate to your passed or failed stage and adds a short note with a link to the result in Nametag.

To see a candidate’s verification detail, open the Breezy HR page in the Nametag Console and select Open in Nametag — that data lives in Nametag, not Breezy.

Managing the integration

• Edit mapping — change the company, stages, position scope, or delivery channel at any time.
• Disconnect — removes the Nametag webhook from Breezy and deletes the stored credential and signing secret.

Troubleshooting

Symptom	Likely cause	Fix
Status stuck on Webhooks pending	Breezy hasn’t enabled webhooks on your account	Contact Breezy support to enable webhooks (a Pro feature)
“Could not connect” at setup	Wrong service-account credentials, or the account lacks access	Re-check the service account; ensure it can see the company and positions
Candidate reached the trigger stage but no request was sent	Position out of scope, or the webhook isn’t healthy yet	Check the position scope and webhook status on the Breezy HR detail page
Candidate verified but the stage didn’t move	The passed/failed stage was renamed or removed in Breezy	Re-map the stages under Edit mapping
Verification shows Expired	The candidate didn’t finish in about 7 days	Re-send by moving them out of and back into the trigger stage

Privacy

Personal data — ID images, selfie, and extracted identity fields — is processed and stored by Nametag, not Breezy. Breezy only ever receives a pass/fail stage change and a note with a link. This keeps identity data out of your applicant tracking system by design.