Skip to content
Business productivity ⇄ Human resources

GitHub to Lever integration — real-time, two-way sync

Keep GitHub and Lever in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect GitHub and Lever

Keep the people, teams, and status that GitHub and Lever share aligned in real time, so a hire, role change, or departure recorded in one reaches the other within seconds.

Each tool in GitHub keeps its own list of who can use it: users, members, or agents, along with the team they sit on and whether they are still active. Lever is the authoritative record of the same people as employees, with their department, manager, and employment status. When those two are connected only by manual account admin or a periodic export, the work tools drift: new hires wait days for access, team and manager changes never catch up, and people who have left keep standing accounts.

Stacksync syncs Workflow runs (Actions), Organizations and Teams, Users, Labels and Milestones in GitHub with Interviews, Notes and Contacts, Opportunities, Postings in Lever bi-directionally and in real time. A person added, moved, or offboarded in Lever creates or updates the matching user in GitHub within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where GitHub captures details of its own, such as a corrected contact or a login identity, those can flow back to Lever in whichever direction you configure.

Because the sync is field-level, each system keeps its own extras; only the shared facts, who a person is, which team they belong to, and whether their access should be on, are held in agreement.

Common use cases

  • 01 Publish release data into customer-communication tools when a new version ships.
  • 02 Two-way sync of GitHub issues with Jira, Linear, or a support system so engineering and customer-facing teams work in their own tools.
  • 03 Write enriched Sources, Tags, and Contact data back onto Opportunities from an outbound sourcing pipeline.
  • 04 Two-way sync Opportunities and their Stages between Lever and a Postgres database so recruiting ops and analysts query the pipeline in SQL while recruiters keep working in Lever.

Common sync patterns

Offboarding: no standing access after a departure

When someone is marked as leaving in Lever, the matching account in GitHub is deactivated or flagged, so departures do not leave open access behind.

One employee directory

A person's name, title, contact details, or status corrected in either system updates the other, so both sides stop maintaining separate copies of the same person.

Org and team structure kept current

Department, team, and reporting-line changes from Lever keep the groups, queues, or projects in GitHub assigned to the right people.

What you can sync between GitHub and Lever

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

GitHub objects Lever objects How this pairing syncs
Users Author and assignee identities matched to internal directories. Users Lever team members (recruiters, hiring managers) with configurable roles; can be created via POST /users, deactivated, and reactivated through the API. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Labels and Milestones Classification fields mapped to statuses and sprints in external trackers. Offers Offer records attached to an Opportunity with status and offer-form fields; exposed read-only through GET /opportunities/:id/offers, so they sync outbound to an HRIS or onboarding system when a candidate reaches the offer stage. Labels and Milestones is specific to GitHub and Offers to Lever — each maps to any object or custom field on the other side.
Repositories Top-level containers whose metadata and settings syncs read to scope other objects. Stages Pipeline stage definitions that Opportunities move through; read to model funnel state and stage transitions in a database. Repositories is specific to GitHub and Stages to Lever — each maps to any object or custom field on the other side.
Issues Synced two-way with project trackers and support tools, including labels and assignees. Feedback Interview feedback and scorecard forms attached to Opportunities; created via POST /opportunities/:id/feedback and consolidated into a warehouse for interviewer analytics. Issues is specific to GitHub and Feedback to Lever — each maps to any object or custom field on the other side.
Pull Requests Review state, status checks, and merge status feed engineering dashboards and workflow tools. Interviews Scheduled interview panel events with times and interviewers; read for scheduling reporting and time-to-hire metrics, and creatable via the panels endpoint. Pull Requests is specific to GitHub and Interviews to Lever — each maps to any object or custom field on the other side.
Commits Read-only history used to link code activity to tickets and releases. Notes and Contacts Free-text Notes on Opportunities plus the underlying Contact (person) that dedupes multiple Opportunities; notes are posted via POST /opportunities/:id/notes and contact-level tags, sources, and links can be added back for attribution. Commits is specific to GitHub and Notes and Contacts to Lever — each maps to any object or custom field on the other side.

How changes propagate between GitHub and Lever

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

GitHub Lever Sub-second propagation

DetectionGitHub notifies Stacksync of record changes through webhook events. Webhooks with a broad event catalog covering issues, pull requests, pushes, and releases.

DeliveryEach detected change is written to Lever through its API, with automatic retries and rate-limit backoff.

Lever GitHub Sub-second propagation

DetectionLever notifies Stacksync of record changes through webhook events. Webhooks for candidate and application lifecycle events (applicationCreated, candidateStageChange, candidateArchiveStateChange, candidateHired,.

DeliveryEach detected change is written to GitHub through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • GitHub: Authenticated REST requests are limited to 5,000 per hour per user; GitHub Apps scale limits per installation.
  • Lever: 10 requests/second per API key with a token-bucket burst to ~20/s; POSTs that create candidates/applications are throttled to roughly 2/second. Sustained overage returns 429 with Retry-After. List endpoints are cursor-paginated at up to 100 records per page.
What ships with GitHub ⇄ Lever

Connect GitHub and Lever for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every GitHub–Lever connection.

Real-time

Two-way sync

Changes in GitHub or Lever instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever GitHub or Lever data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single GitHub or Lever record.

Observability

Monitoring

Track your GitHub ⇄ Lever sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between GitHub and Lever.

How the GitHub and Lever connectors work

GitHub

Integration surface
REST API and GraphQL API
Authentication
OAuth 2.0, fine-grained personal access tokens, or GitHub App installation tokens
Change detection
Webhooks with a broad event catalog covering issues, pull requests, pushes, and releases; polling for backfill
Capabilities
read · write · webhooks
Rate limits
Authenticated REST requests are limited to 5,000 per hour per user; GitHub Apps scale limits per installation.

Lever

Integration surface
REST Data API (api.lever.co/v1)
Authentication
API key over HTTP Basic auth (key as username, blank password) for internal integrations, or OAuth 2.0 with 1-hour access tokens for partner integrations (auth.lever.co)
Change detection
Webhooks for candidate and application lifecycle events (applicationCreated, candidateStageChange, candidateArchiveStateChange, candidateHired, interview created/updated/deleted), plus incremental polling via created_at and updated_at range filters on Opportunities
Capabilities
read · write · webhooks
Rate limits
10 requests/second per API key with a token-bucket burst to ~20/s; POSTs that create candidates/applications are throttled to roughly 2/second. Sustained overage returns 429 with Retry-After. List endpoints are cursor-paginated at up to 100 records per page.
Lever setup guide
How it works

How to connect GitHub to Lever — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate GitHub and Lever with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    GitHub connected
    Lever connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the GitHub and Lever objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · GitHub ⇄ Lever
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    GitHub Lever
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

GitHub and Lever integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 457 integrations available for GitHub and Lever.

Popular · 8 of 457
All GitHub integrations All Lever integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own