HR & RecruitingReal-timeUpdated September 2026

Lever integration

Lever ATS opportunity and postings

Lever is the ATS popular with high-growth tech companies — known for its "opportunities" model (a person who might be a fit for multiple roles is one opportunity, not duplicate candidate records) and tight sourcing-CRM integration. Tiny Command exposes three actions, no triggers (Lever has webhooks configured per-org in Settings → Integrations → Webhooks; point at a Tiny Command webhook trigger URL for candidate-created, candidate-hired events): List Postings (open job requisitions with team, location, status filters), List Opportunities (paginated candidate records with filters by stage, source, posting), Get Opportunity (full detail of one candidate including resume, application notes, scorecards, archive reason if archived). The connection uses Lever OAuth or a personal API key. The "opportunity" model is the conceptual centrepiece — a single candidate considered for multiple roles has a single opportunity with multiple applications; this avoids the duplicate-candidate-record problem that plagues other ATSs.

Connect Lever — start free

No credit card required · Set up in under 2 minutes

0triggers

3actions

≈ 2 minto set up

Freetier · no card

Actions

Do anything Lever can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

Action	What it does	Inputs	Open action
Get Lever Opportunity	Returns a candidate-as-person record (Lever's opportunity is the candidate, not the deal) with applications, resume, notes, archive reason. The standard lookup for hiring workflows.	1 input	View
List Lever Opportunities	Paginated candidates with filters by stage, source, posting, recently updated. For "today's candidates" digests and for warehouse-sync workflows.	3 inputs	View
List Lever Postings	Returns open requisitions with team, location, status. Useful for "auto-post to careers page" sync workflows.	1 input	View

Recipes

Pre-built Lever workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Lever → Slack alerts

AI-triage every Lever event, ping the right channel only when it matters.

Lever → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

Lever → Notion database

Turn Lever into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Each workflow step uses 1 credit. Put a filter right after the trigger: events that don't match stop there and only use credits for the steps that already ran.

Authorize once, reuse anywhere

Connect Lever once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Lever field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Lever integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Lever to TinyCommand?

Open the TinyCommand workflow builder, drop in a Lever node, and click Connect. Authorize Lever once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What Lever triggers does TinyCommand support?

TinyCommand focuses on outbound actions for Lever today. Use TinyCommand's universal Webhook or Schedule trigger to start Lever workflows, then run any Lever action you need.

What Lever actions can I run from a workflow?

3 Lever actions are available out of the box, covering hr & recruiting operations like "Get Lever Opportunity". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Lever integration real-time?

Lever actions execute synchronously inside your workflow. TinyCommand waits for Lever's API to confirm before continuing to the next step, so downstream nodes can rely on the result.

Do I need to write code to use Lever with TinyCommand?

No. Every Lever trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Lever API endpoint directly.

How much does the Lever integration cost?

The Free plan includes 1,000 credits a month and every integration, with no credit card. Each workflow step uses 1 credit, and paid plans include more credits and team seats. The Lever integration itself has no per-app surcharge.