Skip to content
Business productivity ⇄ Human resources

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

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

Keep the people, teams, and status that Gainsight 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 Gainsight 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 CTA (Call to Action), Scorecard Fact, Timeline Activity, Success Plan in Gainsight with Offers, Users, Stages, Feedback in Lever bi-directionally and in real time. A person added, moved, or offboarded in Lever creates or updates the matching user in Gainsight within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Gainsight 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 Keep Relationship records aligned with a billing system or ERP so multi-product customers map to the correct contracts and invoices.
  • 02 Read Timeline Activities and Success Plan objectives into a reporting database for churn, QBR, and CSM-productivity dashboards.
  • 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 Gainsight assigned to the right people.

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

When someone changes teams or managers in Lever, the queues, ownership, or approvals in Gainsight 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 Gainsight with the right team and manager already set, so people can start working without waiting on a provisioning ticket.

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

Gainsight objects Lever objects How this pairing syncs
Timeline Activity Logged calls, emails, and notes; usually read out into a reporting database for QBR and churn analysis. Interviews Scheduled interview panel events with times and interviewers; read for scheduling reporting and time-to-hire metrics, and creatable via the panels endpoint. Timeline Activity is specific to Gainsight and Interviews to Lever — each maps to any object or custom field on the other side.
Success Plan Account objectives with associated tasks; read out for reporting or synced with project tools tracking onboarding and adoption. 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. Success Plan is specific to Gainsight and Notes and Contacts to Lever — each maps to any object or custom field on the other side.
Task and Playbook Cockpit tasks generated from CTAs and playbooks; synced with Jira or Asana so execution happens in the team's own tool. 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. Task and Playbook is specific to Gainsight and Opportunities to Lever — each maps to any object or custom field on the other side.
Custom Objects Org-specific MDA tables with the __gc suffix; discoverable via the Describe API so field mappings can be generated automatically. 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. Custom Objects is specific to Gainsight and Postings to Lever — each maps to any object or custom field on the other side.
Company Customer/account master in Gainsight CS; two-way synced with CRM and warehouse customer tables to keep ARR, owner, and renewal fields aligned. 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. Company is specific to Gainsight and Requisitions to Lever — each maps to any object or custom field on the other side.
Person (People) Contacts associated to companies through the Company Person junction; synced two-way with CRM contacts and warehouse person records. 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. Person (People) is specific to Gainsight and Offers to Lever — each maps to any object or custom field on the other side.

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

Gainsight Lever Interval-based propagation

DetectionStacksync polls Gainsight for changes on an incremental schedule, reading only records changed since the previous pass. Polling on the ModifiedDate (GS Modified Date) system field, which is filterable and sortable on every object.

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

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

Rate-limit considerations

  • Gainsight: Synchronous APIs are capped near 100 calls/min and 50,000/day; the asynchronous Bulk API allows 10 calls/hour and 100/day. Both are fixed-window limits, and the applicable per-hour and per-day limits are returned in the x-ratelimit-limit response header.
  • 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 Gainsight ⇄ Lever

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Gainsight and Lever connectors work

Gainsight

Integration surface
REST APIs (per-object) and asynchronous Bulk REST API
Authentication
API access key passed in the 'accesskey' request header (non-expiring), generated by a Gainsight admin; M2M OAuth (Client ID/Secret) is also supported
Change detection
Polling on the ModifiedDate (GS Modified Date) system field, which is filterable and sortable on every object; Rules Engine Real-Time Rules can optionally push specific object events (e.g., a Company stage change) to an external endpoint
Capabilities
read · write
Rate limits
Synchronous APIs are capped near 100 calls/min and 50,000/day; the asynchronous Bulk API allows 10 calls/hour and 100/day. Both are fixed-window limits, and the applicable per-hour and per-day limits are returned in the x-ratelimit-limit response header.

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

    Choose tables

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

Gainsight 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 511 integrations available for Gainsight and Lever.

Popular · 8 of 511
All Gainsight 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