NewCost control: a token allowance a month for each model choice — when one runs out, the cheaper one answers.See how it works
memtro

Greenhouse + Memtro

Your hiring pipeline, answered in plain language.

Connect Greenhouse Recruiting and Memtro can list open roles with their hiring teams, show where every candidate sits in the pipeline, read scorecards and upcoming interviews, and track offer status. Read-only through a Harvest API key; salary and compensation fields are never requested.

What you can do with Greenhouse in Memtro

Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Greenhouse tool, reads what it needs, and answers with the source cited.

01

Hiring sync

Ask for the pipeline of a role: Memtro groups applications by stage, names the candidates and flags who has been waiting longest.

02

Candidate debrief

Before a decision meeting, ask for a candidate: Memtro gathers their applications, every scorecard's recommendation and the interviews already held.

  • Open jobs with departments, hiring teams, openings and stages
  • Candidates with applications, stage and source
  • Pipeline per stage for any job
  • Scorecards with recommendations and ratings
  • Upcoming interviews and offer status

Ask it like this

Questions people ask once Greenhouse is connected. In agent mode each one also checks the other systems that know about the same people, companies or identifiers.

  • ›How many candidates are in onsite for the Backend Engineer role?
  • ›Who interviewed Ann Lee and what did they recommend?
  • ›What interviews are scheduled this week?
  • ›Which offers are still unresolved?

Where it fits

Teams that get the most from Greenhouse in Memtro, with the rest of their stack attached.

Better together

A record in Greenhouse is rarely the whole story. Connect the systems that hold the rest and the agent cross-references them by default, then remembers what it learned so the next question starts further along.

Also in People and HR

Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.

How to connect

  1. 01In Greenhouse go to Configure → Dev Center → API Credential Management and create a Harvest API key with GET permissions
  2. 02In Memtro choose Greenhouse and paste the key
  3. 03Memtro verifies the key and syncs application activity, scorecards and offers hourly
Also works from

Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Greenhouse tools are the same everywhere.

Set it up as an MCP server →Clients and agents →

Questions

Can Memtro change anything in Greenhouse?
Not yet. Today every Greenhouse tool reads, searches or lists. When the connector gains actions, each is marked, granted by name per team and used only when a person asks for exactly that, so nothing is created, sent, updated or deleted until you say so.
Who can use a Greenhouse connection?
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Does Memtro store my Greenhouse data?
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded. An hourly sync anchors recently changed Greenhouse records into memory as entities.
How do I connect Greenhouse?
API key. In Greenhouse go to Configure → Dev Center → API Credential Management and create a Harvest API key with GET permissions.

Connect Greenhouse in a few minutes

Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.