Skip to content
Help Center

Greenhouse integration overview

View MarkdownContact support9 min read
On this page

Overview

Greenhouse is an applicant tracking system (ATS) that helps teams manage candidates, applications, interviews, and offers across the hiring lifecycle. Persona’s Greenhouse integration helps you connect recruiting activity in Greenhouse with identity workflows in Persona by pulling in candidate and application data, taking actions in Greenhouse from Persona, and triggering Persona workflows from key Greenhouse events.

This integration is especially useful for recruiting operations, talent teams, and risk/compliance teams that want to automate identity checks at specific points in the hiring process (for example, when an offer is updated or when a candidate reaches a certain stage).

Benefits

Reduce manual follow-up: Automatically look up the right candidate or application in Greenhouse from Persona workflows, so teams spend less time searching across tools.

Faster, more consistent screening: Trigger identity workflows at the right hiring moments (like offer updates or stage changes) to keep processes consistent across roles and teams.

Cleaner downstream reporting: Keep candidate records up to date by writing back structured outcomes (such as tags or custom fields) so recruiting dashboards and audits stay accurate.

Integration Features

Persona’s Greenhouse integration supports workflow automation, data retrieval, and write-backs to support recruiting operations. Key capabilities include:

  • Search and retrieve hiring records: Look up candidates and applications to enrich Persona Inquiries, Cases, or Accounts with recruiting context.
  • Update candidate profiles: Write back updates to candidate fields (such as contact details, tags, or custom fields) to reflect Persona outcomes.
  • Event-driven workflow triggers: Trigger Persona workflows when Greenhouse sends webhook events like offer updates or candidate stage changes.

Setting up the Greenhouse integration

Prerequisites

To set up the Greenhouse integration, ensure you have:

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

Setting up the Greenhouse Credentials

  1. In the Persona Dashboard, navigate to Integrations > Marketplace and click on Greenhouse.
  2. Click on Add Credential at the top of the page.
  3. Enter the Nickname for Credential in the modal and click Continue.
  4. Complete the authentication steps in the popup, then click Authorize when prompted.

Setting up Greenhouse Webhooks

If you want Persona workflows to trigger from Greenhouse events (like offer updates or stage changes), configure webhooks in Greenhouse and connect them to Persona.

  1. In the Persona Dashboard, navigate to Integrations > Marketplace > Greenhouse.
  2. Click Add Webhook, select the Persona environment(s) the webhook will be active in, and create a Secret Key.
    • The signature key will be used to cryptographically sign all webhook payloads and ensure the information is transmitted securely from Greenhouse to Persona.
    • The signature key can be any value, but it is recommended that the key is a long, random, and complex string, such as a7e4a56cf7c1cd80cb1c735c72bab2aa75d06fe08b8c50a18cf6afbcfe834122.
  3. Copy the webhook URL and Secret Key shown in Persona.
  4. In Greenhouse, go to Settings > Dev Center > Webhooks.
  5. Create a webhook in Greenhouse and paste the Persona URL and Secret Key into the corresponding Greenhouse fields.
  6. Save the webhook. If the webhook is set up properly, you should see a ping event appear in Persona’s integration logs for Greenhouse.

Because webhooks are used as a way to trigger Persona workflows, each environment you select for a webhook will cause a workflow run in that environment when the webhook fires.

Using the Greenhouse 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 Greenhouse integration and choose your Greenhouse credential.
  4. Configure the input fields to pass in the correct information (for example, a candidate ID, an application ID, or filters to find the right record).
  5. Save/publish the workflow.

If you’ve configured Greenhouse webhooks, you can also start workflows using the External Integration Log Created trigger and select Greenhouse as the integration. From there, you can filter by the webhook “operation type” (for example, offer updates or candidate stage changes) and use the webhook payload to look up the related candidate or application.

Greenhouse Operations Overview

In addition to syncing field values, Persona can retrieve candidate and application details, and update candidate profiles using Greenhouse’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 Greenhouse integration:

List applications

Returns a list of applications from Greenhouse. This is commonly used to (1) find a specific application when you only have partial context (like a candidate ID) or (2) retrieve recent application activity to inform routing and decisioning in Persona.

Because applications can be filtered in several ways, this step is useful for narrowing down to the exact application record you need before taking a follow-up action.

Configuration Steps:

  • Optionally add filters to narrow results, such as:
    • Application IDs
    • Candidate IDs
    • Job IDs, job post IDs, or prospective job IDs
    • Stage IDs
    • Application status
    • Prospect status
  • Optionally adjust pagination settings:
    • Results per page
    • Pagination cursor
  • Optionally specify which fields to return to limit the response to only what you need

List interviews

Returns scheduled interview events on candidate applications from Greenhouse, including interview timing, status, location, and organizer details. This step is commonly used to see where a candidate is in the interview process, identify upcoming or overdue interviews, or enrich Persona context with interview scheduling information.

Configuration Steps:

  • Optionally add filters to narrow results, such as:
    • Interview IDs
    • Application IDs
    • Job IDs
    • Job interview IDs (the stage’s interview configuration template)
    • Organizer IDs
    • External calendar event ID
    • Interview status (to be scheduled, scheduled, awaiting feedback, complete, skipped, or sent)
    • Created at, updated at, starts at, or ends at date ranges
    • All-day interview start or end dates
  • Optionally adjust pagination settings:
    • Results per page
    • Pagination cursor
  • Optionally specify which fields to return to limit the response to only what you need

List interviewers

Returns the panel members scheduled on interviews from Greenhouse. This step is commonly used to see who is interviewing a candidate, track interviewer availability, or enrich Persona context with interviewer details.

Configuration Steps:

  • Optionally add filters to narrow results, such as:
    • Interviewer IDs
    • Interview IDs
    • User IDs (Greenhouse user IDs on the panel)
    • Scorecard IDs
    • Response status (needs action, declined, tentative, or accepted)
    • Created at or updated at date ranges
  • Optionally adjust pagination settings:
    • Results per page
    • Pagination cursor
  • Optionally specify which fields to return to limit the response to only what you need

List candidates

Returns a list of candidates from Greenhouse. This step is commonly used to enrich Persona context by pulling candidate profile details like name, contact information, and tags.

Configuration Steps:

  • Optionally add filters to narrow results, such as:
    • Candidate IDs
    • Email address
    • Tag
    • Private status
    • Custom field option ID
  • Optionally adjust pagination settings:
    • Results per page
    • Pagination cursor
  • Optionally specify which fields to return to limit the response to only what you need

List application stages

Returns the stage history for applications from Greenhouse. Each row represents an application’s visit to an interview stage, with timestamps for when the application entered and left the stage. This step is commonly used to track how long candidates spend at each stage or to see where a candidate is in the hiring process.

Configuration Steps:

  • Optionally add filters to narrow results, such as:
    • Application stage IDs
    • Application IDs
    • Job interview stage IDs
    • Created at or updated at date ranges
  • Optionally filter by current stage status:
    • Set Current to true to return only each application’s current stage entry, false to return only past entries, or omit it for full history
  • Optionally adjust pagination settings:
    • Results per page
    • Pagination cursor
  • Optionally specify which fields to return to limit the response to only what you need

List attachments

Returns a list of attachments on applications from Greenhouse, including each attachment’s type and the application and candidate it belongs to. This step is commonly used to retrieve supporting documents like resumes or offer letters to enrich Persona context or inform routing and decisioning.

Configuration Steps:

  • Optionally add filters to narrow results, such as:
    • Attachment IDs
    • Application IDs
    • Candidate IDs
    • Attachment type (resume, cover letter, take home test, offer packet, offer letter, signed offer letter, form attachment, midfunnel agreement, automated agreement, or other)
    • Created at or updated at date ranges
  • Optionally adjust pagination settings:
    • Results per page
    • Pagination cursor
  • Optionally specify which fields to return to limit the response to only what you need

Update candidate

Updates a candidate’s profile information in Greenhouse. Teams often use this step to write Persona outcomes back into the candidate record so recruiters can see status without leaving Greenhouse (for example, adding tags or updating custom fields).

This step supports updating common profile fields (like name and contact details) as well as structured fields like tags and custom fields, depending on what your Greenhouse account has configured.

Configuration Steps:

  • Provide values for required fields:
    • Candidate ID
  • Provide one or more fields to update, such as:
    • Name or basic profile fields
    • Email addresses, phone numbers, or addresses
    • Tags
    • Linked user IDs
    • Custom fields (using the appropriate custom field identifier/key from Greenhouse)

Move application stage

Moves an application to a different stage within the same job, or transfers it to another job. Teams often use this step to keep the hiring pipeline in sync with Persona outcomes (for example, promoting an application after an identity check passes). The From Stage ID must match the candidate’s actual current stage.

Configuration Steps:

  • Provide values for required fields:
    • Application ID
    • From Stage ID (the application’s current stage; must match its actual current stage in Greenhouse)
  • Optionally provide:
    • To Stage ID (the target stage to move the application to)
    • To Job ID (transfers the candidate to another job; the application lands on that job’s first interview stage)
    • Email From User ID (the user whose identity is used as the sender for automated stage transition emails)

FAQs

Which Greenhouse webhook events are supported?

Persona supports Greenhouse webhook events for offer updates and candidate stage changes, which can be used to trigger workflows via the External Integration Log Created trigger. Greenhouse may also send a ping event to verify the webhook endpoint is reachable.

What data can I pull from Greenhouse?

You can retrieve candidate records, application records, and the attachments on them (including commonly used attributes like IDs, timestamps, status/stage information, and associated metadata). The specific fields available depend on the record type you’re pulling and how your Greenhouse account is configured.

Plans Explained

Greenhouse Integration by plan

Startup ProgramEssential PlanGrowth PlanEnterprise Plan
Greenhouse IntegrationNot AvailableNot AvailableLimitedAvailable

Learn more about pricing and plans.

Last updated on .

Was this page helpful?If something is missing, let us know and we will take a look.
Thanks for the feedback. It helps us improve these docs.