Skip to content
Human resources ⇄ Business productivity

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

Keep Lever and Slack 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 Lever and Slack

Keep the people, teams, and status that Slack 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 Slack 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 Channels, Messages, Threads, Users in Slack with Opportunities, Postings, Requisitions, Offers in Lever bi-directionally and in real time. A person added, moved, or offboarded in Lever creates or updates the matching user in Slack within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Slack 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 Sync the Slack user directory with the HRIS or identity provider to keep memberships and profiles current
  • 02 Archive channel messages into a warehouse or database for compliance and analytics
  • 03 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.
  • 04 Push Postings and Requisitions into an HRIS or warehouse to reconcile approved headcount against open roles.

Common sync patterns

Org and team structure kept current

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

Where Slack routes or assigns work by person: assignments follow the org

When someone changes teams or managers in Lever, the queues, ownership, or approvals in Slack update to match, so work reaches whoever holds the role now.

Onboarding: access ready on day one

A new hire recorded in Lever creates the matching user in Slack with the right team and manager already set, so people can start working without waiting on a provisioning ticket.

What you can sync between Lever and Slack

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.

Lever objects Slack objects How this pairing syncs
Users Lever team members (recruiters, hiring managers) with configurable roles; can be created via POST /users, deactivated, and reactivated through the API. Users Workspace members with profile fields, synced against HR systems and identity providers. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Postings Job posting records with categories, apply URLs, workplace type, and requisition codes. Can be created via POST /postings and read into a warehouse for open-role reporting. Files Uploads attached to messages, retrievable for archiving. Postings is specific to Lever and Files to Slack — each maps to any object or custom field on the other side.
Requisitions Headcount/requisition records with custom requisition fields, tied to Postings; read via GET /requisitions and synced to an HRIS to reconcile approved headcount against open roles. Reactions Emoji responses that can drive workflows, such as approving a synced record. Requisitions is specific to Lever and Reactions to Slack — each maps to any object or custom field on the other side.
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. Channels Conversations (public, private, DMs) that messages are read from and posted to. Offers is specific to Lever and Channels to Slack — each maps to any object or custom field on the other side.
Stages Pipeline stage definitions that Opportunities move through; read to model funnel state and stage transitions in a database. Messages Keyed by channel and timestamp; posted via chat.postMessage and read via history methods. Stages is specific to Lever and Messages to Slack — each maps to any object or custom field on the other side.
Feedback Interview feedback and scorecard forms attached to Opportunities; created via POST /opportunities/:id/feedback and consolidated into a warehouse for interviewer analytics. Threads Replies grouped under a parent message timestamp, preserved when archiving conversations. Feedback is specific to Lever and Threads to Slack — each maps to any object or custom field on the other side.

How changes propagate between Lever and Slack

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.

Lever Slack 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 Slack through its API, with automatic retries and rate-limit backoff.

Slack Lever Sub-second propagation

DetectionSlack notifies Stacksync of record changes through webhook events. Events API webhooks, delivered over HTTP callbacks or Socket Mode.

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

Rate-limit considerations

  • 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.
  • Slack: Per-method rate limit tiers; message posting is additionally limited per channel.
What ships with Lever ⇄ Slack

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Lever or Slack 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 Lever or Slack record.

Observability

Monitoring

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

Trading partners

EDI

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

How the Lever and Slack connectors work

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

Slack

Integration surface
Web API (HTTP RPC-style methods) plus the Events API
Authentication
OAuth 2.0 with bot or user tokens and granular scopes
Change detection
Events API webhooks, delivered over HTTP callbacks or Socket Mode
Capabilities
read · write · webhooks
Rate limits
Per-method rate limit tiers; message posting is additionally limited per channel
How it works

How to connect Lever to Slack — 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 Lever and Slack 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
    Lever connected
    Slack connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Lever and Slack 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 · Lever ⇄ Slack
    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
    Lever Slack
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Lever and Slack 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 453 integrations available for Lever and Slack.

Popular · 8 of 453
All Lever integrations All Slack 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