Automate Lever

Know what's happening to your Lever opportunities without watching the pipeline. Your team hears about new candidates, you get word when someone reaches the Offer stage, and a weekly report surfaces candidates nobody has touched in a while. Describe what you want to your AI assistant, check what it will do, and it keeps running.

Add to ChatGPT Add to Claude

Works inChatGPT Claude Claude Code Cursor Codex VS Code Gemini CLI Zed opencode Any MCP client

Try asking

Create a ClickRuntime automation: when a new candidate is added in Lever, post their name, the posting they applied to and a link to their profile in #recruiting on Slack.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Ideas

What you can automate in Lever

New candidates announced as they arrive, a heads-up when someone hits a key stage, and a weekly nudge about the ones that went quiet. These are ready-made starting points. Anything else you can describe works too.

The moment it happens

Announce new Lever candidates in Slack

Your hiring channel gets each new candidate's name and the role they applied for as soon as they come in.

See how it works

The moment it happens

Hear when a candidate reaches Offer in Lever

You get an email the moment a candidate moves into the stage you care about.

See how it works

Weekly

Find candidates stuck in your Lever pipeline

Every Monday you get a list of active candidates with no activity in the last two weeks.

See how it works Your own logic

Any other automation you can describe in words

Your own rules, schedule and AI steps with Lever, plus any other app. Describe it and your assistant builds it.

See how to build your own

Build your own

Build any Lever automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what Lever should do in your own words, with your conditions, other apps or an AI step, and your assistant writes it, tests it and runs it on ClickRuntime.

Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

For example, ask your assistant

Every Monday, tell me which Lever opportunities have had no activity for 10 days and which postings got zero new applicants last week.

When a Lever opportunity moves to the offer stage, post the candidate name, role and owner in our #recruiting Slack channel.

When a new applicant arrives in Lever, have AI summarize their resume against the job description, add the summary as a note in Lever, and log it in Google Sheets with a fit score.

Beyond chat

Have Lever work when you're not in the chat

Connecting Lever to ChatGPT or Claude lets you ask about it while you chat. ClickRuntime handles the part that should happen on its own: checks on a schedule and actions on each new event, set up from the same chat and running after you close it.

Instant
Announce new Lever candidates in Slack
The moment it happens
On a schedule
Find candidates stuck in your Lever pipeline
Weekly
Instant
Hear when a candidate reaches Offer in Lever
The moment it happens

Setup

Connect Lever

Lever connects with a Data API key that a Super Admin generates in your Lever account. You pick which endpoints the key can use when you create it.

Lever

Recruiting / ATS

Sign in to Lever as a Super Admin and open Settings, then Integrations and API.
Under API Credentials, choose Generate New Key.
Select the endpoint permissions the automation needs, such as read access to opportunities, then copy the key.
In the ClickRuntime dashboard, open Connections & secrets and save the key as a secret for Lever.

Good to know

Lever limits that affect automations

Only Super Admins can create Lever API keys and set up Lever webhooks.
The Lever Basic plan only includes the Postings API. Automations that read candidates and opportunities need a higher plan with full Data API access.
Each key can make about 10 requests per second, with short bursts up to 20. A weekly report across a large pipeline simply takes a little longer to run.

FAQ

Questions about automating Lever

What can ClickRuntime access in Lever?

Only the endpoints you ticked when you generated the key. The automations here only read opportunities and their stages; they don't change anything in Lever.

Will this work on the Lever Basic plan?

Only for job postings. Basic includes just the Postings API, so candidate and stage automations need a Lever plan with the full Data API.

Are stage changes reported straight away?

Yes. Lever can send a webhook when a candidate changes stage, so the alert goes out as soon as it happens. A Super Admin sets up the webhook in Lever using the link ClickRuntime gives you.

How does it decide a candidate is stale?

It looks at each active opportunity's last interaction date and lists the ones older than the number of days you choose, such as 14.

Do I need AI for Lever automations?

No. These alerts and reports run without it. If you later want summaries, they use the AI that comes with every ClickRuntime plan, with no AI key of your own.

Is this a Lever connector for ChatGPT or Claude?

Not for chatting with Lever data. A chat connector lets your assistant read and change Lever while you're in the conversation. ClickRuntime is for the work that should happen without you: you set up an automation from the chat once, and it keeps running on a schedule or on each Lever event.

Keep exploring