Nametag Docs
Get help Launch Nametag
Integrations CATS

Nametag Integration for CATS

Verify candidate identities during the CATS hiring pipeline and record the result on the candidate record.

Overview

The Nametag and CATS integration lets organizations verify candidate identities directly inside their CATS (catsone.com) hiring pipeline. When a candidate reaches a status you choose, Nametag sends them a verification link, confirms they are who they claim to be, and records a pass/fail result on the candidate — without ever writing personal data back into CATS.

Prerequisites

Before setting up the integration, ensure you have:

  1. An active Nametag account.
  2. A CATS account on an API-enabled (paid) plan, with administrator rights to generate an API key.
  3. The CATS integration enabled for your Nametag tenant. If you don’t see it in the console, contact Nametag support to enable the feature.

Setup

Step 1: Generate a CATS API key

  1. In CATS, go to Administration → API.
  2. Create a new API key and copy it.

This is the CATS key — it authorizes Nametag to talk to your CATS workspace. Keep it secret. You never enter a Nametag API key; you are already signed in to the Nametag Console.

Step 2: Connect in the Nametag Console

  1. In the Nametag Console, go to Configure.
  2. In the left sidebar, select Integrations.
  3. Select Add Integration and choose CATS.
  4. Paste your CATS API key and select Connect.

Nametag validates the key against CATS, displays your CATS workspace name, and stores the key encrypted. The key never leaves Nametag.

Step 3: Choose the trigger status

Pick the pipeline (workflow) and the status in it that should start an identity check — for example, an Identity Check status shortly before an offer.

When a candidate reaches this status in CATS, CATS notifies Nametag and Nametag sends the candidate a verification link.

Step 4: Map the result

  • Result field: choose the candidate custom field where Nametag writes the verification result. Create one in CATS first if needed (for example, “Nametag Verification”).
  • On pass (optional): choose a status to automatically advance the candidate to when they pass verification.

Step 5: Choose candidate delivery

Choose how candidates receive their verification link: email, SMS, or both. Delivery uses the candidate’s contact details as stored in CATS.

Step 6: Review and enable

Review your choices and select Enable. Nametag registers a webhook in CATS and the connection goes live. You’ll land on the connection detail view.

Verification flow

After the integration is configured and enabled, identity verification is triggered when a candidate reaches the trigger status in CATS.

  1. A candidate progresses through the hiring pipeline in CATS.
  2. The candidate reaches the configured trigger status.
  3. CATS notifies Nametag, and Nametag sends the candidate a verification link by email and/or SMS.
  4. The candidate opens the link and completes identity verification.
  5. Nametag processes the verification and determines the outcome.
  6. Nametag writes the result to the mapped custom field on the candidate and logs an activity with a link to the verification details in the Nametag Console.
  7. If an on-pass status is configured and the candidate passes, Nametag advances them to that status.
flowchart TD A[Candidate enters pipeline] B[Candidate reaches trigger status] C[Nametag sends verification link] D[Candidate completes identity verification] E{Verification result} F[Write result to custom field + log activity] G{On-pass status configured?} H[Advance candidate to on-pass status] I[Leave candidate in current status] A --> B --> C --> D --> E E -->|Passed| F F --> G G -->|Yes| H G -->|No| I E -->|Failed / Pending / Expired| F

Data recorded in CATS

Nametag records verification information on the candidate in CATS. Only a status value and an activity note are ever written.

Result custom field

Nametag writes one of the following values to the custom field you mapped in Step 4:

Value Meaning
Passed The candidate completed verification successfully.
Failed The candidate did not pass verification.
Pending A verification link has been sent and is awaiting completion.
Expired The verification link expired before the candidate completed it.

Activity note

Nametag also logs an activity on the candidate summarizing the outcome, with a link to the detailed verification results in the Nametag Console.

What is never written to CATS

Nametag holds the verified identity. No personal data — date of birth, ID numbers, document images, or selfies — is ever written into CATS. Only the pass/fail result and the activity note leave Nametag.

Managing the connection

From Integrations → CATS in the Nametag Console you can:

  • View verification stats and webhook health.
  • Edit the trigger, result mapping, and delivery configuration.
  • Send a test verification to an address you supply, without a CATS trigger.
  • Rotate the CATS API key or rotate the webhook secret.
  • Enable or disable the integration for your tenant.

Removing the integration

You can disconnect the CATS integration at any time from the Nametag Console:

  1. In the Nametag Console, go to Configure.
  2. In the left sidebar, select Integrations.
  3. Locate the CATS integration.
  4. Select Remove.

Once disconnected:

  • Nametag deletes the webhook in CATS, so CATS stops notifying Nametag.
  • The encrypted CATS API key is wiped from Nametag.
  • Existing data already recorded on candidates in CATS remains unchanged.

If you want to use the integration again, set it up again by following the setup steps.

Troubleshooting

Symptom Fix
“Invalid CATS API key” Regenerate the key in CATS Administration → API, and confirm your plan includes API access.
Candidates aren’t receiving links Confirm the trigger status matches the stage candidates actually reach, and check the delivery method plus the candidate’s email/phone in CATS.
Results not appearing in CATS Confirm the mapped custom field still exists, and check webhook health on the detail view.
“Feature not available” Ask Nametag support to enable the CATS integration for your tenant.
Verification “stopped working” after a while A verification link expires after about 7 days; the candidate must complete it in that window. Re-trigger by moving the candidate back to the trigger status.