Linking Lever as a source
This source is currently in alpha. The interface and available tables may change.
The Lever connector automatically pulls your Lever recruiting data into the PostHog data warehouse.
Adding a data source
- Go to the sources tab of the data pipeline section in PostHog.
- Click + New source and then click Link next to Lever.
- You need a Lever API key. In your Lever account, go to Settings → Integrations and API → API Credentials and generate an API key. The key has full read access to your account's data, so no individual scopes need to be granted.
- Back in PostHog, enter the key in the
API keyfield and click Next. - Select the tables you want to sync, set the sync method and frequency, then click Import.
Once the syncs are complete, you can start using Lever data in PostHog.
Available tables
| Table | Description | Sync method |
|---|---|---|
opportunities | Candidates and their opportunities in your pipeline | Incremental |
postings | Job postings | Full refresh |
users | Lever users in your account | Full refresh |
requisitions | Hiring requisitions | Full refresh |
archive_reasons | Reasons used when archiving opportunities | Full refresh |
stages | Pipeline stages | Full refresh |
sources | Candidate sources | Full refresh |
tags | Tags applied to opportunities | Full refresh |
Incremental tables sync only new or updated records on each run. Full refresh tables reload all data on each sync.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
opportunities | A candidate's pipeline for a specific role — Lever's central record tying a person to an opening. | Incremental, Full refresh | createdAt, updatedAt | — |
postings | A job posting (opening) in Lever that candidates can apply to. | Full refresh | — | — |
users | A Lever user — a member of your hiring team. | Full refresh | — | — |
requisitions | A requisition tracking approved headcount for a role in Lever. | Full refresh | — | — |
archive_reasons | A reason a candidate's opportunity can be archived (e.g. hired, rejected). | Full refresh | — | — |
stages | A stage in the Lever hiring pipeline that opportunities move through. | Full refresh | — | — |
sources | A source through which candidates are added to Lever, keyed by its unique text value. | Full refresh | — | — |
tags | A tag that can be applied to opportunities, keyed by its unique text value. | Full refresh | — | — |