Hiring
An AI agent that keeps your Ashby pipeline honest.
Connect Ashby and an OpenHelm agent can produce scheduled hiring reports, watch for loops losing momentum, and prepare researched candidate briefs, so the recruiting team spends its time with people instead of dashboards.
What agents do with Ashby. Recurring jobs, checked every run.
Hiring health report
A weekly summary per role: pipeline volume, pass-through rates, stalled candidates and upcoming decision points.
Loop-momentum watch
Alert coordinators when interviews go unscheduled or feedback is overdue beyond your threshold, with the specific blockers named.
Pre-interview briefs
Compile public-source briefs on upcoming candidates and file them to the interview panel the day before.
Connect Ashby. A few minutes, once.
Connect Ashby
Add Ashby 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": "Ashby", "type": "token", "secret": "<your Ashby API key>" }'
# The secret is write-only: stored encrypted, injected only at run time.Questions
How current is the reporting?
As current as the schedule you choose. Jobs can run hourly, daily or weekly, and each run reads live Ashby data at execution time rather than a cached export.
How does OpenHelm connect to Ashby?
With a scoped API key: create one in Ashby, 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 Ashby 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.