Skip to content
Human resources ⇄ Business productivity

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

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

Keep the people, teams, and status that SendGrid 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 SendGrid 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 Email Activity, Contacts, List, Segments in SendGrid with Requisitions, Offers, Users, Stages in Lever bi-directionally and in real time. A person added, moved, or offboarded in Lever creates or updates the matching user in SendGrid within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where SendGrid 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 CRM contacts and their custom fields into SendGrid lists so campaign targeting reflects live sales data
  • 02 Write bounces, spam reports, and unsubscribes back to the CRM to keep email opt-in status accurate everywhere
  • 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

Onboarding: access ready on day one

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

Offboarding: no standing access after a departure

When someone is marked as leaving in Lever, the matching account in SendGrid 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.

What you can sync between Lever and SendGrid

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 SendGrid objects How this pairing syncs
Stages Pipeline stage definitions that Opportunities move through; read to model funnel state and stage transitions in a database. Senders Synced with incremental and full sync per the Stacksync docs. Stages is specific to Lever and Senders to SendGrid — 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. Single Sends One-off marketing campaigns whose stats are read back for reporting. Feedback is specific to Lever and Single Sends to SendGrid — each maps to any object or custom field on the other side.
Interviews Scheduled interview panel events with times and interviewers; read for scheduling reporting and time-to-hire metrics, and creatable via the panels endpoint. Unsubscribe Groups Synced with incremental and full sync per the Stacksync docs. Interviews is specific to Lever and Unsubscribe Groups to SendGrid — each maps to any object or custom field on the other side.
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. Email Activity Synced with incremental and full sync per the Stacksync docs. Notes and Contacts is specific to Lever and Email Activity to SendGrid — each maps to any object or custom field on the other side.
Opportunities The core pipeline record for a candidate applying to a role; replaced the deprecated Candidates endpoint. Created via POST /opportunities and updated (stage, archive, links, tags, sources, files) through the API, and synced two-way with a database or HRIS. Contacts Marketing recipients upserted from CRM or database records, including custom field values. Opportunities is specific to Lever and Contacts to SendGrid — each maps to any object or custom field on the other side.
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. List Synced with incremental and full sync per the Stacksync docs. Postings is specific to Lever and List to SendGrid — each maps to any object or custom field on the other side.

How changes propagate between Lever and SendGrid

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

SendGrid Lever Sub-second propagation

DetectionSendGrid notifies Stacksync of record changes through webhook events. Event Webhook posts delivery and engagement events (processed, delivered, open, click, bounce, spam report) to an HTTP endpoint.

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.
  • SendGrid: Subject to the platform's API rate limits; contact upserts are batched, asynchronous jobs rather than per-row writes.
What ships with Lever ⇄ SendGrid

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Lever ⇄ SendGrid 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 SendGrid.

How the Lever and SendGrid 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

SendGrid

Integration surface
REST API (v3)
Authentication
API key (create in SendGrid Settings > API Keys with Custom Access / Full Access for the objects to sync; key begins with "SG")
Change detection
Event Webhook posts delivery and engagement events (processed, delivered, open, click, bounce, spam report) to an HTTP endpoint; contact and list changes are detected by polling
Capabilities
read · write · webhooks
Rate limits
Subject to the platform's API rate limits; contact upserts are batched, asynchronous jobs rather than per-row writes
SendGrid setup guide
How it works

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

    Choose tables

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

Lever and SendGrid 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 455 integrations available for Lever and SendGrid.

Popular · 8 of 455
All Lever integrations All SendGrid 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