Nametag Docs
Get help Launch Nametag
Integrations Polymer

Nametag Integration for Polymer

Verify candidate identities during the Polymer hiring process and record a pass/fail result on the candidate application.

Overview

The Nametag integration for Polymer verifies candidate identity inside your Polymer hiring workflow. When a candidate reaches a hiring stage you choose, Nametag asks them to verify their identity and writes a pass/fail signal back to the Polymer application as a review and comment — optionally advancing the candidate to the next stage.

No candidate personal data is stored in Polymer. Nametag holds the verified identity; Polymer receives only the result.

Polymer has no webhooks. Nametag detects candidates by polling the Polymer Customer API with incremental updated_since cursors, so there is nothing to configure on Polymer’s side beyond the API key.

Prerequisites

Before setting up the integration, ensure you have:

  1. An active Nametag account with the Polymer integration enabled for your organization (contact Nametag support if you don’t see it).
  2. An administrator account for Polymer.
  3. A Polymer Customer API key (see below).

Get your Polymer customer API key

  1. In Polymer, go to Settings → API keys (app.polymer.co/hire/settings/api_keys).
  2. If you don’t see a “Your API key” tab, your organization needs the Customer API (beta) enabled. Ask a Polymer administrator to email support@polymer.co, then return here.
  3. Generate a key and copy it.

You are giving Nametag a Polymer key. You never paste a Nametag key into this flow.

Setup

Step 1: Add the integration

  1. In the Nametag Console, open Integrations → Add Integration.
  2. Select the Polymer card to launch the setup wizard.

Step 2: Connect Polymer

  1. Paste your Polymer Customer API key and select Connect to Polymer.
  2. Nametag validates the key against Polymer and shows your organization name to confirm.
    • “Polymer rejected the key” → re-copy it from Polymer → Settings → API keys.
    • “Customer API not enabled” → have a Polymer administrator email support@polymer.co, then reconnect. Nametag fails closed: nothing is stored and no polling starts until the key validates.

Step 3: Choose coverage

Pick which jobs the integration applies to:

  • All published jobs (default), or
  • Selected jobs — choose from your live Polymer job list.

Step 4: Set the trigger and write-back

  1. Trigger stage — pick a job, then the hiring stage that starts verification. Create a stage named “Identity Verification” in Polymer for this. Candidates who land in this stage are sent a verification link by Nametag (email or SMS).
  2. Post a scorecard review or comment — on by default; the verdict is written as a Polymer review and comment.
  3. On pass, move the candidate — optionally auto-advance verified candidates to a stage you choose.
  4. On fail or expiry — the default is a neutral review and comment for manual review (no auto-archive). You can opt into archiving instead.
  5. Skip stage messages — on by default, so Polymer’s automated stage messages don’t email candidates when Nametag moves them.

Step 5: Activate

Select Activate. Polling begins for your organization (about every 3 minutes). You can edit coverage, trigger, and write-back settings any time from the connection’s detail view.

What candidates see

Candidates receive a link, scan a government ID, and take a quick Spatial Selfie™. Verification takes under a minute. Requests expire after about 7 days; you can re-send from the detail view.

Managing the connection

From Integrations → Polymer you can:

  • View status and result counts (pending, sent, passed, failed, expired).
  • Change coverage, trigger stage, and write-back settings.
  • Pause polling without losing configuration.
  • Disconnect, which stops polling and clears your stored Polymer key.

Privacy

Nametag writes only a pass/fail signal and a short note to Polymer — never ID numbers, documents, selfies, or other personal data. The candidate’s email and phone are used only transiently to deliver the verification link and are never stored in Polymer or in the Nametag binding.

Troubleshooting

Symptom Fix
No “Your API key” tab in Polymer Enable Customer API (beta) via support@polymer.co.
“Polymer rejected the key” on connect Re-copy the key; ensure you’re a Polymer administrator.
Candidate didn’t get a link Confirm the application is in the trigger stage and has a valid email or phone on the Polymer candidate record.
Result didn’t post to Polymer Check connection status; if a candidate’s request expired, re-send from the detail view.

Need help? Contact Nametag support from the console.