Skip to content

Start building

Integration · HR and recruiting

AI agents for Greenhouse

Find jobs, candidates and applications, add notes to candidates, and add candidates or prospects in Greenhouse Recruiting, through the Harvest v3 API.

Actions
6
Read
4
Write
2

Actions

What your agents can do in Greenhouse

6 actions. Each one is a tool your agents can call and a step your workflows can run.

Read 4

Look things up. Nothing changes.

  • List jobs

    Lists jobs (requisitions), newest first, optionally only open, closed or draft ones, or those in a department or office, or with a requisition ID.

  • List candidates

    Lists candidates and prospects, newest first, optionally only the one with an email address (any of theirs, case-insensitive), with a tag, or updated since a time.

  • Get a candidate

    Reads one candidate or prospect by their ID: names, company, title, emails, phones, web and social links, tags, time zone and last activity.

  • List applications

    Lists applications, newest first: a candidate's journey on one job (or a prospect's), with its candidate ID, job ID, status (active, rejected, hired, converted), current stage and when it last moved.

Write 2

Create, change or send.

  • Add a note to a candidate

    Adds a note to a candidate's Notes tab, optionally tied to one of their applications.

  • Add a candidate or prospect

    Creates a person with a first and last name and optionally an email, phone, company, title and tags (new tags are created).

A person can approve first

Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything.

Connection

How it connects

Connect it once in the console, then give it to the agents and workflows that need it.

App credentials

Paste the client ID and secret of an app your organization registered with Greenhouse. The platform fetches its tokens itself (OAuth client credentials).

Kept safe

  • Credentials are stored encrypted with your organization's own keys.
  • They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
  • Calls go only to the tool's own servers.

How we protect your data

Ideas

Ideas to start with

Starting points made only from the actions above. Mix them with any other tool your agents can use.

  • 01

    Ask about your Greenhouse data

    Ask a question in plain words. The agent can list jobs, list candidates or get a candidate in Greenhouse, then answers with what it found.

  • 02

    Let an agent update Greenhouse

    Have the agent add a note to a candidate or add a candidate or prospect in Greenhouse as part of a larger task. Turn on approval and a person signs off on each change first.

  • 03

    Share what it finds in Slack

    Give one agent Greenhouse and Slack: it can list jobs in Greenhouse and post a summary to a Slack channel in the same run.

FAQ

Greenhouse and MyDeepAgents

Can MyDeepAgents connect to Greenhouse?

Yes. The Greenhouse connector has 6 actions: 4 read and 2 make changes. Your agents can call them as tools, and your workflows can run them as steps.

How do I connect Greenhouse?

Paste the client ID and secret of an app your organization registered with Greenhouse. The platform fetches its tokens itself (OAuth client credentials). Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.

Can an agent change data in Greenhouse without asking?

Only if you let it. Each of the 2 actions that change data can be set to wait for a person's approval before it runs.

Can I use Greenhouse in workflows as well as agents?

Yes. Every Greenhouse action also works as a step in a workflow, and the same connection serves your agents and your workflows.

Early access

Put Greenhouse to work

Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.