Skip to content
CRM ⇄ Human resources

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

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

Keep the people who own accounts in Freshsales 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.

Freshsales 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 Contacts, Accounts, Deals, Tasks in Freshsales with Opportunities, Postings, Requisitions, Offers 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 Freshsales keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.

Common use cases

  • 01 Keep Freshsales accounts aligned with a billing system so plan and revenue fields stay current.
  • 02 Sync sales activities and appointments into analytics tools for rep productivity reporting.
  • 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

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 Freshsales, 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 Freshsales, so a new rep can start working accounts without waiting on a manual setup ticket.

Ownership and territory follow the org chart

When a person changes team, manager, or region in Lever, their accounts and territory assignments in Freshsales update to match, so pipeline stays with the right owner.

What you can sync between Freshsales 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.

Freshsales objects Lever objects How this pairing syncs
Deals Pipeline records synced to a warehouse for revenue 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. Deals is specific to Freshsales and Opportunities to Lever — each maps to any object or custom field on the other side.
Tasks Rep to-dos created from external triggers or synced for productivity reporting. 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. Tasks is specific to Freshsales and Postings to Lever — each maps to any object or custom field on the other side.
Appointments Scheduled meetings readable for activity analytics. 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. Appointments is specific to Freshsales and Requisitions to Lever — each maps to any object or custom field on the other side.
Notes Free-text records attached to contacts, accounts, and deals. 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. Notes is specific to Freshsales and Offers to Lever — each maps to any object or custom field on the other side.
Sales activities Configurable activity types logged against records, useful for engagement scoring. Users Lever team members (recruiters, hiring managers) with configurable roles; can be created via POST /users, deactivated, and reactivated through the API. Sales activities is specific to Freshsales and Users to Lever — each maps to any object or custom field on the other side.
Products Catalog items attached to deals for line-level revenue data. Stages Pipeline stage definitions that Opportunities move through; read to model funnel state and stage transitions in a database. Products is specific to Freshsales and Stages to Lever — each maps to any object or custom field on the other side.

How changes propagate between Freshsales 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.

Freshsales Lever Sub-second propagation

DetectionFreshsales notifies Stacksync of record changes through webhook events. Polling with updated-at filters through views.

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

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

Rate-limit considerations

  • Freshsales: Subject to per-account API rate limits that vary by Freshworks plan.
  • 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 Freshsales ⇄ Lever

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Freshsales and Lever connectors work

Freshsales

Integration surface
REST API
Authentication
API key sent as a Token authorization header
Change detection
Polling with updated-at filters through views; outbound webhooks can be configured via workflow automations
Capabilities
read · write · webhooks
Rate limits
Subject to per-account API rate limits that vary by Freshworks plan

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 Freshsales 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 Freshsales 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
    Freshsales connected
    Lever connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Freshsales 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 522 integrations available for Freshsales and Lever.

Popular · 8 of 522
All Freshsales 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