Nametag Docs
Get help Launch Nametag
Integrations Recruitee

Nametag Integration for Recruitee

Verify candidate identities in the Recruitee hiring pipeline and record the result on the candidate — no personal data is stored in Recruitee.

Overview

The Nametag and Recruitee integration verifies that every candidate in your Recruitee (Tellent’s applicant tracking system) pipeline is a real, unique person. When a candidate reaches a stage you choose, Nametag automatically sends them an identity check and writes a Pass/Fail result back onto the candidate record — as a custom field, a note, and (optionally) a tag.

No personal data or ID documents are stored in Recruitee. Only the decision, a timestamp, and an opaque Nametag request reference are written back.

This integration is enabled per organization. If Recruitee does not appear under Add Integration in your Nametag Console, contact Nametag to have it enabled for your account.

Prerequisites

Before setting up the integration, ensure you have:

  1. An active Nametag account with the Recruitee integration enabled (you are already signed in to the Nametag Console — you never paste a Nametag key anywhere).
  2. Access to your Recruitee account with the “Manage webhooks” role ability.
  3. Your Recruitee company ID and the ability to create a personal API token (Settings → Apps and plugins → Personal API tokens) for a pilot, or your Tellent partner authorization for production.

Credential direction: setup starts in the Nametag Console and the “Connect” step authorizes Recruitee — the machine credential Nametag uses to call the Recruitee API. Nametag never asks for, or accepts, a Nametag API key.

Setup

Step 1: Add the integration

  1. In the Nametag Console, go to Configure.
  2. In the left sidebar, select Integrations.
  3. Select Add Integration and choose Recruitee.

Step 2: Connect Recruitee

Authorize Recruitee from the wizard. For a pilot, paste your Recruitee personal API token and company ID — this is your Recruitee credential. For production, complete the Tellent partner authorization. Nametag stores the credential encrypted at rest.

Personal API tokens are user-scoped and intended for pilots. For production, use the Tellent Partner API path so the connection does not depend on an individual user’s account.

Step 3: Set up the webhook

Nametag verifies each inbound Recruitee event using a shared secret. The wizard either provisions the Recruitee webhook for you, or shows you an exact POST URL and a generated secret to add under Recruitee → Settings → Apps and Plugins → Webhooks (+ New webhook, HTTPS URL, select the candidate events, then Verify and create). Keep the secret — Nametag uses it to authenticate every event.

Step 4: Choose coverage (scope)

Pick which jobs/departments the integration applies to. Others are left untouched.

Step 5: Choose the trigger (rule)

Choose when verification fires. By default, verification runs when a candidate is moved to a stage you select (for example, Phone interview). You can optionally verify at application instead.

Step 6: Review and activate

Confirm the summary and activate. Nothing runs until you activate (and until the integration is enabled for your account).

Verification flow

  1. A recruiter moves a candidate to the configured stage in Recruitee (or a candidate applies, if you chose that trigger).
  2. Recruitee sends a signed event to Nametag. Nametag verifies the signature, checks the event against your scope and rule, and — if it matches — creates a verification request for the candidate.
  3. Nametag sets the candidate’s Nametag Verification field to Pending and delivers the candidate a verification link.
  4. The candidate completes the check (typically under a minute; 11,000+ government ID types, no app download).
  5. Nametag writes the Pass/Fail result back onto the candidate: it updates the custom field, adds a note with the result and a link, and optionally applies a tag.
  6. Requests expire after about 7 days (~168 hours) if the candidate does not complete them. Rejected or expired candidates can be re-invited.
flowchart TD A[Recruiter moves candidate to trigger stage] B[Recruitee sends signed webhook event] C{Matches scope + rule?} D[Create Nametag request, set field to Pending, send invite] E[Ignore] F[Candidate completes verification] G{Result} H[Write Pass: custom field + note + optional tag] I[Write Fail: custom field + note; allow re-invite] J[Expired ~168h: write Expired; allow re-invite] A --> B --> C C -->|No| E C -->|Yes| D --> F --> G G -->|Pass| H G -->|Fail| I G -->|No completion| J

Because webhook delivery is best-effort, Nametag also reconciles by periodically polling Recruitee, so a missed webhook will not silently skip a candidate.

Data written to Recruitee

Nametag writes only non-personal decision data to the candidate record:

Where What
Custom field (Nametag Verification) The current status: Pending, Pass, Fail, or Expired
Candidate note The decision, a UTC timestamp, an opaque Nametag request reference, and a link to the verification details
Tag (optional) For example Nametag: Verified

No PII in Recruitee. ID images, biometrics, and personal data are never written to or stored in Recruitee.

Removing the integration

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

Once disconnected, Nametag stops calling Recruitee and stops writing results back. Existing data already written to Recruitee remains unchanged. Remove the webhook in Recruitee if it was configured manually.

Troubleshooting

  • “Recruitee” isn’t in Add Integration — the integration isn’t enabled for your account yet; contact Nametag.
  • No verifications firing — check your scope (right jobs?), your rule (right stage?), and that the webhook shows 200 in Recruitee’s Logs tab.
  • Webhook failing — confirm the POST URL is HTTPS and the secret matches; re-run Test in Recruitee.
  • Candidate stuck on Pending — the request may have expired (~168 hours); re-invite from the Nametag Console.