Hiring
An AI agent for your Greenhouse hiring pipeline.
Connect Greenhouse and an OpenHelm agent can keep hiring moving between syncs: summarising pipeline health, nudging interviewers on overdue scorecards, and researching candidates and sourcing targets with a real browser, all on a recurring schedule.
What agents do with Greenhouse. Recurring jobs, checked every run.
Weekly pipeline digest
Summarise candidates by stage per role, time-in-stage outliers and offer status into one email before the hiring sync.
Stuck-candidate nudges
Flag candidates waiting too long on feedback or scheduling and prompt the responsible interviewer or coordinator by email.
Candidate research briefs
Before onsites, compile a short public-profile brief for each candidate from open web sources, cited and fabrication-free.
Sourcing long-lists
Research potential candidates matching a role brief into a data table for recruiters to review before anyone is contacted.
Connect Greenhouse. A few minutes, once.
Connect Greenhouse
Add Greenhouse under Connections in the OpenHelm app and paste a scoped API key, or provision it programmatically with POST /v1/connections.
Describe the job in plain English
Tell OpenHelm what you want done and how often. It drafts a plan with a schedule, the tools it will use, and a clear definition of done.
Approve the plan
No job fires until you have reviewed the plan. Set the autonomy level to control whether writes execute directly or queue for your approval.
It runs, self-checks and reports
Runs execute in isolated cloud sandboxes on schedule. An independent evaluator scores each run against the goal, and results arrive as logs, emails or data-table rows.
Or provision it over the API (see the Connections API docs):
curl https://api.openhelm.ai/v1/connections \
-H "Authorization: Bearer oh_live_..." \
-H "Content-Type: application/json" \
-d '{ "name": "Greenhouse", "type": "token", "secret": "<your Greenhouse API key>" }'
# The secret is write-only: stored encrypted, injected only at run time.Questions
Does the agent contact candidates?
Only if you build a job that does, and then subject to the autonomy level you set. Most teams keep candidate outreach human and use the agent for digests, nudges and research.
How does OpenHelm connect to Greenhouse?
With a scoped API key: create one in Greenhouse, paste it into Connections in the OpenHelm app, or provision it programmatically with POST /v1/connections. The key is stored encrypted and injected only at run time inside an isolated sandbox, and you can rotate or delete it whenever you like.
Can the jobs run on a schedule without me?
Yes, that is the point. Jobs run once, on an interval, or on a cron expression. A scheduler fires them, a watchdog times out anything hung, and a separate evaluator checks each run actually advanced the goal. You approve the plan before anything runs for the first time.
Is my Greenhouse data safe?
Each run executes in an isolated cloud sandbox with scoped, revocable credentials and no middle-layer copy of your data. Every action is logged per run, results come back with evidence, and the agent never fabricates data it could not verify.
Give your product a team that never clocks off.
Start free in the browser, or run it on your Mac with your own Claude Code or Codex plan.