Two-way sync
Changes in Airtable or Lever instantly reflect in both systems. No stale data, no manual imports.
Keep Airtable 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.
Lever is the system of record for the people side of the business — employees, candidates, roles, and the org structure around them. Airtable is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Opportunities, Postings, Requisitions, Offers in Lever need to exist as queryable Views, Linked records, Attachments, Collaborators in Airtable before an app can act on them. When that bridge is a nightly export or a hand-run CSV, every downstream system spends the day working from a roster that has already moved on.
Stacksync syncs Views, Linked records, Attachments, Collaborators in Airtable with Opportunities, Postings, Requisitions, Offers in Lever field by field, in real time. You decide which system owns which fields — Lever typically owns identity and org attributes, while operational or computed values can flow back the other way — and Stacksync keeps every copy consistent, matching records on a stable key and resolving conflicts by rules you set.
The result is one live picture of the workforce on both sides: HR keeps its source of truth, and the database keeps a current mirror that internal apps, reports, and access controls can trust without a batch window in between.
Values assembled or corrected in Airtable write onto the matching record in Lever where those fields are writable, keeping the people system enriched.
Records maintained in Lever land as queryable Views, Linked records, Attachments, Collaborators in Airtable, so internal apps and dashboards read live data instead of a periodic export.
When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.
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.
| Airtable objects | Lever objects | How this pairing syncs | |
|---|---|---|---|
| Fields Typed columns including linked records, lookups, and rollups; computed fields are read-only in syncs. | Feedback Interview feedback and scorecard forms attached to Opportunities; created via POST /opportunities/:id/feedback and consolidated into a warehouse for interviewer analytics. | Fields is specific to Airtable and Feedback to Lever — each maps to any object or custom field on the other side. | |
| Views Filtered subsets of a table that can scope which records a sync reads. | Interviews Scheduled interview panel events with times and interviewers; read for scheduling reporting and time-to-hire metrics, and creatable via the panels endpoint. | Views is specific to Airtable and Interviews to Lever — each maps to any object or custom field on the other side. | |
| Linked records Cross-table references that carry relationships between synced tables. | 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. | Linked records is specific to Airtable and Notes and Contacts to Lever — each maps to any object or custom field on the other side. | |
| Attachments File fields exposed as expiring URLs that syncs can mirror to other systems. | 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. | Attachments is specific to Airtable and Opportunities to Lever — each maps to any object or custom field on the other side. | |
| Collaborators User fields useful for mapping record ownership to accounts in a CRM or database. | 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. | Collaborators is specific to Airtable and Postings to Lever — each maps to any object or custom field on the other side. | |
| Bases Top-level containers; each base has its own API endpoint and schema. | 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. | Bases is specific to Airtable and Requisitions to Lever — each maps to any object or custom field on the other side. |
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.
DetectionAirtable pushes changes as they happen — webhook events backed by change data capture. Incremental updates: changes in Airtable are detected and synced efficiently in realtime (webhook-based — creator role required to create webhooks).
DeliveryEach detected change is written to Lever through its API, with automatic retries and rate-limit backoff.
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 Airtable through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Airtable–Lever connection.
Changes in Airtable or Lever instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Airtable or Lever data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Airtable or Lever record.
Track your Airtable ⇄ Lever sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Airtable and Lever.
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.
Authenticate Airtable 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.
Pick the Airtable 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Airtable and Lever: authenticate both systems, choose the objects to sync (such as Airtable's Fields and Views), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for Airtable and Lever: Computed and operational fields flow back; Mirror people records into the database; One directory of record. Values assembled or corrected in Airtable write onto the matching record in Lever where those fields are writable, keeping the people system enriched.
Airtable: REST API (per-base Web API plus metadata and webhooks endpoints). Authentication: OAuth (Airtable OAuth grant to specific bases or all resources); the authorizing user must have a `creator` role, since only creator roles can create webhooks. Lever: 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). Stacksync manages authentication, retries, and rate limits on both sides.
Airtable: Airtable API rate limit of 5 requests/second; Stacksync rate-limits to stay under it. Lever: OAuth access tokens expire after 1 hour and must be refreshed; API keys authenticate over HTTP Basic auth with the key as the username and a blank password. Stacksync's field mapping accounts for these differences between Airtable and Lever without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Airtable and Lever records are not retained after a sync operation.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 541 integrations available for Airtable and Lever.