Hiring
An AI agent working alongside Lever.
Connect Lever and an OpenHelm agent can take the recurring coordination work off the recruiting team: scheduled pipeline summaries, feedback chasing, and browser-researched sourcing lists that arrive as reviewable data tables.
What agents do with Lever. Recurring jobs, checked every run.
Pipeline summary email
A recurring digest of candidate movement, offers in flight and roles at risk of slipping, in plain language for hiring managers.
Feedback chaser
Find interviews missing feedback after a set period and nudge the interviewer with the candidate and role attached.
Sourcing research runs
Research candidates matching a role profile from public sources into a data table, deduplicated against people already in Lever.
Connect Lever. A few minutes, once.
Connect Lever
Add Lever 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": "Lever", "type": "token", "secret": "<your Lever API key>" }'
# The secret is write-only: stored encrypted, injected only at run time.Questions
What credential does this need?
A Lever API key scoped to what the jobs read. It is stored encrypted, used only at run time inside an isolated sandbox, and revocable from Lever whenever you choose.
How does OpenHelm connect to Lever?
With a scoped API key: create one in Lever, 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 Lever 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.
More in Hiring
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.