Skip to main content
Integrations6 min read

Connect Greenhouse and your calendar

Open Integrations, set Greenhouse up with a Harvest API key, import jobs or create a job sync, then connect Cal.com so scheduling and the dashboard week view work.

Before you start

  • A plan on Starter or above. Connecting an existing ATS unlocks there. The built-in pipeline board is on every plan, including the trial.
  • Someone in Greenhouse who can generate a Harvest API key.
  • A Cal.com account for the calendar side.
  • Owner access. A Hiring Manager has recruiting access but not integrations, members or billing.
Steps

8 steps, in order.

1

Open Integrations and read the two cards

Click Integrations in the sidebar. The page is headed Connections and holds two provider cards and nothing else. Greenhouse reads sync jobs and candidates between Greenhouse and Expert Hire, and carries a Set up control with a toggle. Cal.com reads turn Cal.com bookings into scheduled Expert Hire meetings, and carries Connect. Both show Not connected until you finish the setup.

2

Know what the Greenhouse connector covers today

Greenhouse is the one ATS connector available today, and it is in early access. Greenhouse stays your system of record. Expert Hire sits between intake and the human decision, runs the round and hands the evidence back. Four object types move, and nothing outside them is touched. Bullhorn, Lever, Workday and Vincere are named on the roadmap and are not live yet.

  • Jobs

    Direction
    Greenhouse into Expert Hire, so rounds are built against a real role
  • Candidates

    Direction
    Both directions
  • Reportcards: score, verdict, skill breakdown, evidence link

    Direction
    Expert Hire into Greenhouse
  • Reviewer notes

    Direction
    Expert Hire into Greenhouse
3

Generate a Harvest API key with the right access

Press Set up on the Greenhouse card. It asks for the API key. Generate it in Greenhouse as a Harvest API key with job and candidate read access, then paste it in. A key that comes back rejected is almost always a key without Harvest permissions rather than a mistyped one.

  • Greenhouse rejecting the key is a permissions problem. It needs Harvest API permissions with job and candidate read access.
4

Import jobs, or create a job sync

With the key accepted you have two options: import jobs once, or create a job sync that keeps them current. Open jobs come across so you do not recreate a role by hand before building rounds against it. An imported job arrives with its title and its description, and the description is scoring input, so open it and check the text survived the import before you add the first round.

Create role
Job details
Step 1 of 3
Role title *
e.g. Senior backend engineer
Location
e.g. Austin TX, Remote
Language *
English
Voice *
AndrewMALE
Job description * Complete with AI Upload PDF
Aa
Describe the role, responsibilities, and expectations
Minimum 100 characters · 0/100
Use company branding
On: candidate emails and call screen show the company logo. Off: your organisation logo is used instead.
Enable workflow
Let each round auto-reject or auto-advance candidates by score. Off hides the selection-criteria step when creating rounds.
Only advance via workflow
Adding a round won't auto-pull the previous round's shortlisted candidates. Advancement happens only through workflow rules or manual moves.
BackContinue

Where an imported job lands. The description here is what answers are scored against.

5

Run the round and let the reportcard go back

Add rounds to the imported job exactly as you would to one you created. When a round is scored, the reportcard, the score and the reviewer-facing summary are written back onto the Greenhouse record, so nobody opens a second tool to see how a round went.

  • What syncs back is evidence, not a decision. Scores, integrity signals and malpractice flags go to a human reviewer, and nothing is auto-rejected by the integration.
6

Connect Cal.com so scheduling works

Back on Integrations, press Connect on the Cal.com card and complete the sign-in. Do this early. Without a connected calendar, scheduling is manual and the week view on the dashboard stays empty. Once it is connected, Cal.com bookings become scheduled Expert Hire meetings.

  • An empty calendar card on the dashboard means no calendar is connected, not that nothing is booked.
7

Check it on the Meetings page

Open Meetings and go to the Scheduled Meetings tab. That is the tab the connected calendar fills, so a booking appearing there is your confirmation that the connection works. Everything else on that page, the notetaker, uploading a recording made elsewhere and reading what a meeting produced, is covered in Record and review live interviews.

Live & scheduled
Meetings
All MeetingsScheduled Meetings
Scheduled meetings
Upcoming meetings you've scheduled with candidates.
ConnectedGoogle Calendar
Auto-record:
All MeetingsInternal
UpcomingPast Synced just now
Today6
Cloudline standup
10:30 - 11:00EXTERNAL
Dana Whitfield / Datadog
12:30 - 12:45EXTERNAL1:1
Stripe intake
15:00 - 15:45EXTERNAL
Shopify role scope
16:00 - 16:30EXTERNAL
Recruiting weekly
17:30 - 18:00INTERNAL
Databricks debrief
18:15 - 18:45EXTERNAL

Scheduled Meetings, the tab a connected calendar fills.

8

Know the fallback if your ATS is not Greenhouse

Three routes, none of which need a connector. Run Expert Hire as the ATS: the pipeline board is on every plan, with the stages set up under Settings, then Pipeline. Connect the MCP server at mcp.experthire.cloud and drive jobs, rounds, candidates and scheduling from ChatGPT or Claude, which unlocks at Growth with higher limits on Scale. Or export candidates and interviews to CSV whenever you need them somewhere else.

What you get

At the end of this guide.

Greenhouse jobs imported rather than retyped, with a sync that keeps them current.

Candidates aligned in both systems, and the reportcard written back onto the Greenhouse record.

A connected calendar, so scheduling stops being manual and the dashboard week view fills in.

Scheduled Meetings on the Meetings page, fed by that calendar.

A named fallback when your ATS is not Greenhouse: the built-in board, the MCP server or CSV.

Common mistakes

What goes wrong, and the fix.

Generating a plain Greenhouse API key.

It needs Harvest API permissions with job and candidate read access. Anything else is rejected at setup.

Leaving the calendar connection until later.

Connect it early. Until you do, scheduling is manual and the dashboard week view stays empty.

Expecting Bullhorn, Lever, Workday or Vincere to be connectable today.

They are on the roadmap, not live. Use the MCP server, the built-in pipeline board or CSV export until they ship.

Building rounds on an imported job without reading the description.

The description is scoring input. Open the imported job and check the text before the first candidate sits a round.

FAQ

Questions people ask on this one.

Still stuck? Talk to us and we will walk through your setup.

Try this in your own workspace.

The 30-day trial includes 75 Hire Credits, which covers a resume batch and a first round of interviews. Nothing charged for 30 days.

30-day free trial with 75 Hire Credits. Card required, nothing charged for 30 days.