Real-time
Two-way sync
Changes in Folk CRM or Lever instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Human resources
Folk CRM to Lever integration — real-time, two-way sync
Keep Folk CRM 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 Folk CRM and Lever
Keep the people who own accounts in Folk CRM in step with the workforce records in Lever, so ownership, roles, and org structure stay current in both systems, in real time and in both directions.
Folk CRM runs on people as much as on accounts: every contact, deal, and account has an owner, and those owners are employees whose roles, teams, and status are held in Lever. Lever is the system of record for the workforce, from new hires to promotions to departures, and often for the candidates the business is still deciding on. When the two systems are connected only by re-keying or an overnight export, they drift apart, and the CRM ends up assigning accounts to people who have left, holding territories that no longer match the org chart, and waiting days to give a new rep access.
Stacksync syncs Companies, Groups, Custom fields, Notes in Folk CRM with Notes and Contacts, Opportunities, Postings, Requisitions in Lever field by field, in real time, and in both directions. You decide which system owns which fields, so Lever stays authoritative on roles and org structure while Folk CRM keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.
Common use cases
- 01 Push enriched contact data from a data warehouse into folk custom fields.
- 02 Mirror folk groups into a reporting database to track pipeline and outreach coverage.
- 03 When an Opportunity is marked hired, write the candidate and its Offer into an HRIS or onboarding system to start employee provisioning.
- 04 Consolidate Feedback, Interviews, and Notes into a warehouse for interviewer scorecard and time-to-fill reporting.
Common sync patterns
One directory of people
A person's name, title, email, phone, or manager corrected in either system updates the other, so both stop maintaining separate copies of the same individual.
Where Lever tracks people the business also engages: contacts stay in sync
A person recorded in Lever, such as a candidate or applicant, can create or update the matching contact in Folk CRM, so relationship history and outreach are not rebuilt from scratch when the same individual appears in both.
New team members provisioned when they are hired
When Lever records a new hire, a matching user or owner is created in Folk CRM, so a new rep can start working accounts without waiting on a manual setup ticket.
What you can sync between Folk CRM 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.
| Folk CRM objects | Lever objects | How this pairing syncs | |
|---|---|---|---|
| Companies Organization records linked to people and kept aligned with billing or CS systems. | Feedback Interview feedback and scorecard forms attached to Opportunities; created via POST /opportunities/:id/feedback and consolidated into a warehouse for interviewer analytics. | Companies is specific to Folk CRM and Feedback to Lever — each maps to any object or custom field on the other side. | |
| Groups Shared workspaces that organize contacts; group membership is often the field integrations act on. | Interviews Scheduled interview panel events with times and interviewers; read for scheduling reporting and time-to-hire metrics, and creatable via the panels endpoint. | Groups is specific to Folk CRM and Interviews to Lever — each maps to any object or custom field on the other side. | |
| Custom fields Group-scoped attributes that receive enriched or computed values from external systems. | 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. | Custom fields is specific to Folk CRM and Notes and Contacts to Lever — each maps to any object or custom field on the other side. | |
| Notes Free-text context attached to people and companies, readable for reporting. | 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. | Notes is specific to Folk CRM and Opportunities to Lever — each maps to any object or custom field on the other side. | |
| Reminders Follow-up items that can be created from external triggers. | 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. | Reminders is specific to Folk CRM and Postings to Lever — each maps to any object or custom field on the other side. | |
| People Contact records; the primary entity synced with outreach and enrichment tools. | 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. | People is specific to Folk CRM and Requisitions to Lever — each maps to any object or custom field on the other side. |
How changes propagate between Folk CRM 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.
Folk CRM Lever Sub-second propagation
DetectionFolk CRM notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling of list endpoints as a fallback.
DeliveryEach detected change is written to Lever through its API, with automatic retries and rate-limit backoff.
Lever Folk CRM 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 Folk CRM through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Folk CRM: Subject to the platform's API rate limits.
- 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 Folk CRM ⇄ Lever
Connect Folk CRM and Lever for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Folk CRM–Lever connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Folk CRM 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 Folk CRM or Lever record.
Observability
Monitoring
Track your Folk CRM ⇄ Lever sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Folk CRM and Lever.
How the Folk CRM and Lever connectors work
Folk CRM
- Integration surface
- REST API
- Authentication
- API key (Bearer token)
- Change detection
- Webhook subscriptions for record events, with polling of list endpoints as a fallback
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's API rate limits
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.
How it works
How to connect Folk CRM 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.
- 01
Connect your apps
Authenticate Folk CRM 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.
Folk CRM
connected
Lever
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Folk CRM 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.
objects · Folk CRM ⇄ LeverCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Folk CRM LeverCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Folk CRM and Lever integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Folk CRM and Lever: authenticate both systems, choose the objects to sync (such as Folk CRM's Companies and Groups), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Folk CRM: Folk's model centers on people and companies organized into shared groups rather than pipeline-first objects, so group membership carries much of the workflow state. Lever: List endpoints use cursor-based pagination at up to 100 records per page; incremental syncs rely on created_at and updated_at range filters. Stacksync's field mapping accounts for these differences between Folk CRM 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 Folk CRM and Lever records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Folk CRM and Lever connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Folk CRM–Lever integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Folk CRM and Lever. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Folk CRM: Webhook subscriptions for record events, with polling of list endpoints as a fallback. On Lever: 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. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 416 integrations available for Folk CRM and Lever.
Popular · 7 of 416
-
Folk CRM ⇄ Ukg Pro -
Folk CRM ⇄ Greenhouse -
Folk CRM ⇄ Jobvite -
Lever ⇄ SugarCRM -
Lever ⇄ Twenty CRM -
Lever ⇄ Veeva CRM -
Lever ⇄ Vtiger CRM
No integrations match .
