Overview

Polymer is an applicant tracking system (ATS) that helps teams manage the hiring pipeline from candidates to offers. Persona’s integration with Polymer lets you pull candidate and job application context into Persona and take action in Polymer from within Persona Workflows—so recruiting, operations, and risk teams can keep hiring decisions moving with consistent identity context.

Benefits

• Reduce manual handoffs: Bring key candidate and application details into Persona so teams spend less time switching tools or copying information across systems.
• Keep hiring workflows moving: Automatically move job applications to the right hiring stage based on identity-related outcomes (for example, when a workflow reaches a decision point).
• Improve operational visibility: Use up-to-date candidate and application context (including current/next stage and attached materials) to support faster, more consistent decisions.

Integration Features

Persona’s Polymer integration connects your workflows to hiring data and stage movement in Polymer. Key capabilities include:

• Candidate lookups: Retrieve candidates and associated profile details (like name, email, phone, and links) to enrich workflow steps and decisioning.
• Job application visibility: List job applications with application context such as job title, current/next stage, resume URL, attached files, and question responses.
• Automated stage movement: Move a job application to a different hiring stage, with the option to skip stage-based message automations when needed.

Setting up the Polymer integration

Prerequisites

To set up the Polymer integration, ensure you have:

• Admin access to your Polymer account
• Necessary API permissions to access Polymer credentials

Setting up the Polymer credentials

1. In the Persona Dashboard, navigate to Integrations > Marketplace and click on Polymer.
2. Click on Add Credential at the top of the page.
3. Enter a credential nickname and click Continue.
4. In Polymer, create or copy your Polymer API key.
5. In Persona, paste the API key when prompted and save your credential.

Using the Polymer integration in a workflow

1. Create a new workflow, or open an existing workflow you’d like to update.
2. Add a new Action step > Integrations.
3. Select the Polymer integration and choose your Polymer credentials.
4. Choose the operation you want to run and map Persona data into the Polymer fields.
5. Save and publish the workflow.

Polymer Operations Overview

In addition to syncing field values, Persona can list and retrieve candidate or job application records and move job applications to different hiring stages using Polymer’s API. These actions support seamless two-way workflows, letting teams manage investigations without switching platforms. See below for a comprehensive list of available Workflow Action steps and possible configurations for the Polymer integration:

List Candidates

Use this step to retrieve candidates from your Polymer organization—helpful for periodic syncs, backfills, or finding a candidate record before taking additional action. You can narrow results to a specific candidate email or only return candidates updated after a particular point in time.

Configuration Steps:

• Provide values for required fields:
  • None
• Optionally add:
  • Email
  • Updated Since
  • Page
  • Per Page

Retrieve Candidate

Use this step to pull details for a specific candidate when you already know which candidate you want to reference in your workflow. You can also choose to include the candidate’s associated job applications so downstream workflow steps have the application context in one place.

Configuration Steps:

• Provide values for required fields:
  • Candidate ID
• Optionally add:
  • Include (job applications)

List Job Applications

Use this step to retrieve job applications from Polymer when you need application-level context such as job title, hiring stage, resume URL, attached files, or question responses. You can filter results by job, hiring stage, candidate, or last-updated time to target the exact segment of applications your workflow cares about.

Configuration Steps:

• Provide values for required fields:
  • None
• Optionally add:
  • Job ID
  • Hiring Stage ID
  • Candidate ID
  • Updated Since
  • Page
  • Per Page

Move Stage

Use this step to move a job application to a different hiring stage as part of an automated workflow—for example, advancing a candidate after a required check completes or routing them to a review stage for follow-up. When moving stages, you can also control whether Polymer should skip message automations configured on the target stage.

Configuration Steps:

• Provide values for required fields:
  • Job Application ID
  • Hiring Stage ID
  • Skip Message Automations

FAQs

Can I move a job application to any hiring stage?

The target hiring stage must belong to the same job as the job application you’re moving. If you’re not sure which stage IDs are valid for a given job, confirm the hiring stages available for that job in Polymer before configuring your workflow step.

What candidate and application details can Persona pull from Polymer?

Candidate data can include identifiers, timestamps, basic profile information (like name, email, phone, and location), and profile links (for example LinkedIn or GitHub). Job application data can include job and candidate context, current and next hiring stage information, resume URL, attached files, and question responses.