Setting Up the Greenhouse Integration

Modified on Tue, 22 Sep at 1:09 PM

Connect your Greenhouse ATS to Lavalier to sync candidates, job openings, and applications. It only takes a few clicks. You'll sign in to Greenhouse and approve access, with no API keys to copy.

Before You Start

  • Site Admin permissions in Greenhouse. The person who approves the connection in Greenhouse must be a Site Admin.
  • Owner permissions in Lavalier

Connect Greenhouse to Lavalier

  1. In Lavalier, go to Settings → Integrations

  2. Find Greenhouse and click Connect

  3. In the Connect with Greenhouse dialog, confirm Your Greenhouse URL. It's filled in as app.greenhouse.io. If your team signs in to Greenhouse at a different address (like app2.greenhouse.io), enter that instead, without https://.

  4. Click Continue to Greenhouse

  5. Sign in to Greenhouse as a Site Admin if you're asked to, then approve Lavalier's access

Greenhouse sends you back to Lavalier, where you'll see Preparing to Sync Greenhouse Data. You don't have to wait for the sync to finish, so click Let's Go! and keep working. The Greenhouse card shows Connected - Syncing up to date information... while it works, and Connected - Last synced [time] once it's done.

What Gets Synced

Once connected, Lavalier syncs the following from Greenhouse:

  • Open positions and job posts
  • Applications and interview pipeline stages (the stage structure — names, order, and duration — is managed in Greenhouse; you can still add and edit interview questions for each stage in Lavalier)
  • Candidates with active applications in progress
  • Candidate resumes (imported automatically to their profile)
  • Scheduled interviews — they appear on your Interview Calendar with a Greenhouse icon, and Lavalier's notetaker automatically joins any interview with a video link to record and transcribe

Check the Integrations page to see sync status and progress.

When an interview is scheduled, Lavalier may also email the candidate a recording notice. If Candidate Consent is on in your Company OS, this goes out automatically the first time an interview is scheduled or started with a candidate.

Tip: Connect your calendar alongside Greenhouse so Lavalier can automatically join interviews that aren't in Greenhouse. See Connecting Your Calendar.


Already Connected with API Credentials?

If you connected Greenhouse before, using a Client Key and Client Secret, you'll see a Migrate authorization button on the Greenhouse card. Switching takes a minute, and your existing sync keeps running until you finish.

  1. Click Migrate authorization
  2. Confirm your Greenhouse URL, then click Continue to Greenhouse
  3. Sign in to Greenhouse as a Site Admin and approve Lavalier's access

Your roles, candidates, and interviews stay exactly as they are. If the switch doesn't go through, your current connection keeps working, so you can simply try again.

What's next?

With Greenhouse connected, you can:

Troubleshooting

Error: "You must be a Greenhouse Site Admin to connect this integration"

Solution: The person who approves the connection in Greenhouse has to be a Site Admin. Click Connect again (or Settings if Greenhouse is already connected), and sign in to Greenhouse with a Site Admin account when you're sent there. If you aren't a Site Admin, ask one on your team to complete this step.

Error: "This account is already connected to a different Greenhouse organization"

Solution: A Lavalier account can only connect to one Greenhouse organization. That stays true even after you disconnect. Check that Your Greenhouse URL points to your company's Greenhouse and that you're signed in to the right Greenhouse organization, then try again. If you really need to switch organizations, contact Lavalier support.

Error: "Failed to connect Greenhouse. Please try again."

Solution: This usually means the approval in Greenhouse was cancelled or took too long. Click Connect and go through the steps again, making sure to approve access on the Greenhouse page. Double-check that Your Greenhouse URL is just the domain (like app2.greenhouse.io), with no https://.

The Greenhouse card says "Reconnect required to resume syncing"

Solution: Lavalier lost its access to Greenhouse, so syncing has paused. Click Settings on the Greenhouse card, then Continue to Greenhouse, and approve access again as a Site Admin. Syncing picks up where it left off.

Some of my Greenhouse candidates aren't showing up in Lavalier

Lavalier doesn't sync every candidate from Greenhouse. To appear in Lavalier, a candidate must meet both of these conditions:

  • They have an active application on an open job
  • They have moved past the first interview stage (typically "Application Review") in your Greenhouse pipeline

Candidates who are still in the initial application review stage won't appear in Lavalier until they advance to the next stage in Greenhouse.

What happens when I merge a duplicate of a Greenhouse candidate?

You can merge a Greenhouse-linked candidate with one created in Lavalier, but not with another Greenhouse-linked candidate—two Greenhouse records have to be merged in Greenhouse, and the change syncs back.

The Greenhouse-linked record always becomes the combined candidate, and two details are locked: primary email and résumé. Each only actually locks when Greenhouse already has a value for it—if it's empty there, you can bring the duplicate's value across.

Greenhouse stores multiple emails and phone numbers, so any extras the merge adds are kept. A résumé brought in by a merge stays in Lavalier only, though—it can't be uploaded to Greenhouse, so it won't appear there.

Why can't interview feedback push from Lavalier to Greenhouse?

Greenhouse doesn't allow any tool — including Lavalier — to write interview feedback or scorecards through its API. Feedback has to be entered directly in Greenhouse.

To make this easy, click Open in Greenhouse on the feedback toolbar to jump straight to the matching Greenhouse scorecard.

I see "Pending creation in Greenhouse" on a candidate

Solution: This candidate was created in Lavalier and is being synced to Greenhouse. While the badge is visible, the candidate can't be edited or deleted in Lavalier. Once the sync completes (usually within a few minutes), the badge will update.

I can't cancel or edit a Greenhouse interview

Interviews synced from Greenhouse are managed in Greenhouse. When you try to cancel or change one in Lavalier, you'll see a dialog—"This interview is managed by Greenhouse. Open the candidate in Greenhouse to make changes."—with a button to open the candidate directly in Greenhouse. This includes the virtual meeting link, which is also set in Greenhouse.

I can't choose how to record my Greenhouse interview

For Greenhouse interviews, the recording method stays locked until an interviewer is assigned. If the interview has more than one interviewer, use Assign Interviewer (or Change Interviewer) to pick who's conducting it—then choose how to record.

An interview was cancelled in Greenhouse — what happens to it in Lavalier?

When an interview is cancelled in Greenhouse, what happens depends on whether it has any Lavalier data:

  • No recording, transcript, or feedback yet: the interview is removed from Lavalier automatically.
  • Has a recording, transcript, or feedback: the interview is kept so you don't lose your data, but it's disconnected from Greenhouse. Its icon changes to "Originally from Greenhouse" with the note "This interview came from Greenhouse, which no longer has it. It's now managed in Lavalier and won't sync."
I see "Interviewer is in a Separate Lavalier Team" on a Greenhouse interview

This happens when the interviewer assigned in Greenhouse uses an email that already belongs to a different Lavalier team. Lavalier can't invite interviewers across teams, so the interview shows no interviewer and an attention indicator instead.

To fix it: open the candidate in Greenhouse and assign an interviewer who belongs to your Lavalier team. The change will sync back to Lavalier.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article