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 or authorize apps.
  3. Admin permissions in JOIN.

Setup

One-time setup

Step 1: Connect JOIN

  1. In the Nametag Console, go to Configure.
  2. In the left sidebar, select Integrations.
  3. Select Add Integration and choose JOIN.
  4. Connect JOIN. You are already signed in to Nametag, so this step authorizes JOIN — you never paste a Nametag key here:
    • Connect with JOIN (recommended, if available): complete JOIN’s authorization flow to grant Nametag access.
    • API token: in JOIN, go to Settings → API, generate a token, and paste it into the JOIN API token field. Nametag validates the token before saving and stores it encrypted.
  5. Give the connection a name (visible only in Nametag), then continue.

Step 2: Choose the trigger stage

Select the JOIN pipeline stage that should trigger identity verification (default: Interview). When a candidate’s application enters that stage, Nametag sends them a verification request.

Step 3: Choose coverage

  • All jobs (recommended) — every job in this environment is covered.
  • Selected jobs — choose specific JOIN jobs.

Step 4: Write-back & enable

Choose how the result is written back to JOIN (default: an application custom field named “Nametag Identity”), review the summary, and select Enable integration.

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.

Additional settings

Integration name (optional)

You may assign a custom name to the integration in Nametag. This name is only visible inside the Nametag console and does not affect JOIN configuration.

Verification template (optional)

By default, Nametag uses a standard verification template. If your organization has custom Nametag request templates, you can select a different template for JOIN verifications from the integration settings.

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 or authorization you provide, and can be revoked at any time from your JOIN account.

Managing the integration

The connected detail view in the Nametag Console shows connection health, coverage, and recent verifications (candidate initials only). From there you can Reconnect (if the JOIN token is revoked or expired), Edit the trigger, coverage, and write-back settings, or Remove the integration (which deletes the stored JOIN credential).

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 Select Reconnect

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