Nametag Docs
Get help Launch Nametag
Integrations JOIN

Nametag Integration for JOIN

Verify candidate identities during the JOIN hiring process and record results on the candidate application.

Overview

The Nametag and JOIN integration enables organizations to verify candidate identities directly in their JOIN hiring workflow. By connecting Nametag to JOIN (join.com), recruiters can confirm that candidates are who they claim to be — countering deepfake interviews, proxy candidates, and fake applications — before moving forward in the hiring process.

No candidate personal data is stored in JOIN. Nametag holds the verified identity; JOIN receives only a pass/fail signal recorded on the candidate’s application.

Prerequisites

Before setting up the integration, ensure you have:

  1. An active Nametag account with the JOIN integration available for your organization (contact Nametag if you don’t see JOIN under Integrations).
  2. A JOIN account on an integration-enabled plan (Advanced or Enterprise) with permission to generate an API token.
  3. Admin permissions in JOIN.

Setup

Setup has two parts: generate an API token in JOIN, then paste it into the Nametag Console. The trigger stage, job coverage, and write-back mode are configured afterward, on the integration’s detail page — see Configuration.

Step 1: Generate a JOIN API token

  1. In JOIN, go to Settings → API.
  2. Generate a new API token and copy it. You will paste it into Nametag in the next step.

Step 2: Connect Nametag to JOIN

  1. In the Nametag Console, go to Configure.
  2. In the left sidebar, select Integrations.
  3. Select Add Integration and choose JOIN. You are already signed in to Nametag, so this step authorizes JOIN — you never paste a Nametag key here.
  4. Optionally give the connection a name (visible only inside Nametag).
  5. Paste the JOIN API token you generated in Step 1.
  6. Select Connect to JOIN.

Nametag validates the token before saving it, encrypted.

Configuration

After connecting, you land on the integration’s detail view, where each setting is edited in place by selecting its row:

Field Description
Connection name Optional friendly name for the connection, visible only inside Nametag
JOIN API token Shown masked; paste a new token here to reconnect if it’s revoked or expired
Trigger stage The JOIN pipeline stage whose entry launches a Nametag check (default: Interview)
Job coverage Enter all to cover every job, or selected to scope to specific jobs
Write-back mode Enter custom_field, tag, note, or none for how the result is written back to the application

Verification flow

  1. A candidate progresses through the hiring pipeline in JOIN.
  2. The candidate’s application enters the configured trigger stage.
  3. Nametag sends the candidate a verification link (by email or JOIN message).
  4. The candidate opens the link on their phone and completes identity verification (government-ID + selfie).
  5. Nametag processes the verification and determines the outcome.
  6. Nametag writes the result back to the candidate’s application in JOIN (custom field and/or note).
flowchart TD A[Candidate enters pipeline] B[Application enters trigger stage] C[Nametag sends verification link] D[Candidate completes identity verification] E{Verification result} F[Write Verified status to application] G[Write Failed status to application] A --> B --> C --> D --> E E -->|Verified| F E -->|Not verified| G

Data updated in JOIN

Nametag records verification status on the candidate’s application in JOIN — never any personal data.

Field Description
Nametag Identity The current verification result: Verified, Failed, Pending, or Expired
Verification Details Link (Nametag) A link to the detailed results in the Nametag console (optional)

Names, ID images, date of birth, document numbers, and selfies never leave Nametag.

Permissions and scopes

What Nametag requests from candidates

By default, candidates are asked to share a government-issued photo ID and a live selfie. If your organization uses a custom template, the specific data requested depends on that template.

What Nametag requests from JOIN

The integration requests only the minimum permissions required to:

  • Read job and application information to associate verification activity with the correct application.
  • Read candidate contact information to send the verification request to the correct candidate.
  • Write verification status back to the application (custom field and/or note).

Access is granted via the JOIN API token you provide, and can be revoked at any time from your JOIN account.

Managing the integration

The integration’s detail page in the Nametag Console shows connection status and lets you edit any setting in place — see Configuration. If the JOIN token is revoked or expired, select the JOIN API token row and paste a fresh token to reconnect.

Removing the integration

You can disconnect the JOIN integration at any time from the Nametag Console.

  1. In the Nametag Console, go to Configure.
  2. In the left sidebar, select Integrations, then open the JOIN integration’s detail page.
  3. Select the three-dot menu in the header.
  4. Select Delete integration.
  5. Confirm the deletion in the dialog that appears.

Deleting the integration removes the stored JOIN credential. No changes are made to your JOIN account.

Troubleshooting

Symptom Likely cause Fix
JOIN not listed under Integrations Not yet available for your org Contact Nametag support
“Invalid token” on connect Token wrong/revoked or plan lacks API access Regenerate in JOIN → Settings → API; confirm plan
Candidates not getting invites Wrong trigger stage or job not in coverage Check the trigger and coverage settings
Status not showing in JOIN Write-back disabled or custom field missing Set write-back to a custom field; confirm it exists
Connection shows “Action needed” Token expired/revoked in JOIN Generate a new token in JOIN, then paste it into the JOIN API token row on the detail page

Need help? Contact Nametag support with your environment name and the connection name.