Skip to content
CRM ⇄ Human resources

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

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

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

Gladly 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 Agents, Topics, Tasks, Customer profiles in Gladly with Stages, Feedback, Interviews, Notes and Contacts 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 Gladly keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.

Common use cases

  • 01 Keep customer attributes such as loyalty tier and lifetime value synced from a warehouse into Gladly profiles for routing and prioritization.
  • 02 Push conversation outcomes into a CRM so account teams see support context on their accounts.
  • 03 Consolidate Feedback, Interviews, and Notes into a warehouse for interviewer scorecard and time-to-fill reporting.
  • 04 Write enriched Sources, Tags, and Contact data back onto Opportunities from an outbound sourcing pipeline.

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

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

Gladly objects Lever objects How this pairing syncs
Conversations Each customer's continuous timeline; status and outcomes sync to CRMs and warehouses. 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. Conversations is specific to Gladly and Opportunities to Lever — each maps to any object or custom field on the other side.
Conversation items Individual messages across voice, SMS, chat, and email attached to the conversation. 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. Conversation items is specific to Gladly and Postings to Lever — each maps to any object or custom field on the other side.
Agents User records used to attribute work in CX 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. Agents is specific to Gladly and Requisitions to Lever — each maps to any object or custom field on the other side.
Topics Categorization applied to conversations; the key dimension for contact-driver reporting. 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. Topics is specific to Gladly and Offers to Lever — each maps to any object or custom field on the other side.
Tasks Follow-up work items created from external triggers or synced for workload reporting. Users Lever team members (recruiters, hiring managers) with configurable roles; can be created via POST /users, deactivated, and reactivated through the API. Tasks is specific to Gladly and Users to Lever — each maps to any object or custom field on the other side.
Customer profiles The central entity; merges identifiers like email, phone, and order IDs, which syncs use for matching. Stages Pipeline stage definitions that Opportunities move through; read to model funnel state and stage transitions in a database. Customer profiles is specific to Gladly and Stages to Lever — each maps to any object or custom field on the other side.

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

Gladly Lever Sub-second propagation

DetectionGladly notifies Stacksync of record changes through webhook events. Webhook event subscriptions for conversation and customer events, supplemented by polling and report exports.

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

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

Rate-limit considerations

  • Gladly: 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 Gladly ⇄ Lever

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Gladly and Lever connectors work

Gladly

Integration surface
REST API
Authentication
API tokens used with basic authentication tied to an agent email
Change detection
Webhook event subscriptions for conversation and customer events, supplemented by polling and report exports
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.
Lever setup guide
How it works

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

    Choose tables

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

Gladly 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 411 integrations available for Gladly and Lever.

Popular · 7 of 411
All Gladly 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