Skip to content
Business productivity ⇄ Human resources

Adobe Sign to Lever integration — real-time, two-way sync

Keep Adobe Sign 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 Adobe Sign and Lever

Keep the people, teams, and status that Adobe Sign 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 Adobe Sign 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 Agreement Form Field Data, Agreement Events, Library Templates, Widgets in Adobe Sign with Opportunities, Postings, Requisitions, Offers in Lever bi-directionally and in real time. A person added, moved, or offboarded in Lever creates or updates the matching user in Adobe Sign within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Adobe Sign 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 Stream the per-agreement Agreement Events audit trail into a compliance database for retention and who-signed-what reporting.
  • 02 Read Widget submissions from embedded web signing forms into a database to trigger onboarding or contract-fulfillment workflows.
  • 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

Org and team structure kept current

Department, team, and reporting-line changes from Lever keep the groups, queues, or projects in Adobe Sign assigned to the right people.

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

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

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

Adobe Sign objects Lever objects How this pairing syncs
Users Account users; provisioned and updated two-way from an HR system or identity provider. Users Lever team members (recruiters, hiring managers) with configurable roles; can be created via POST /users, deactivated, and reactivated through the API. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Agreements The core e-signature transaction; created and sent from other systems, then read back for status (out-for-signature, signed, cancelled) and the completed PDF. 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. Agreements is specific to Adobe Sign and Offers to Lever — each maps to any object or custom field on the other side.
Agreement Form Field Data Merge fields prefilled at send and values captured from signers; read into a database so contract terms and inputs are queryable. Stages Pipeline stage definitions that Opportunities move through; read to model funnel state and stage transitions in a database. Agreement Form Field Data is specific to Adobe Sign and Stages to Lever — each maps to any object or custom field on the other side.
Agreement Events Per-agreement audit trail of every action (viewed, delegated, signed); read-only, synced into compliance stores. Feedback Interview feedback and scorecard forms attached to Opportunities; created via POST /opportunities/:id/feedback and consolidated into a warehouse for interviewer analytics. Agreement Events is specific to Adobe Sign and Feedback to Lever — each maps to any object or custom field on the other side.
Library Templates Reusable document templates (libraryDocuments); referenced when creating Agreements and synced for template governance. Interviews Scheduled interview panel events with times and interviewers; read for scheduling reporting and time-to-hire metrics, and creatable via the panels endpoint. Library Templates is specific to Adobe Sign and Interviews to Lever — each maps to any object or custom field on the other side.
Widgets Reusable web signing forms with a public URL; submissions read out to trigger downstream onboarding or fulfillment. 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. Widgets is specific to Adobe Sign and Notes and Contacts to Lever — each maps to any object or custom field on the other side.

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

Adobe Sign Lever Sub-second propagation

DetectionAdobe Sign notifies Stacksync of record changes through webhook events. Webhooks (REST v6 webhook subscriptions) fire near-real-time on agreement events such as created, action requested, completed, and cancelled.

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

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

Rate-limit considerations

  • Adobe Sign: Per-user throttling at minute, hour, and day tiers shared between web UI and API traffic; exceeding a tier returns HTTP 429 with a Retry-After header. Exponential backoff with jitter is recommended.
  • 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 Adobe Sign ⇄ Lever

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Adobe Sign and Lever connectors work

Adobe Sign

Integration surface
REST API v6 (JSON)
Authentication
OAuth 2.0 authorization-code flow with granular per-resource scopes (agreement_read, agreement_write, agreement_send, user_read, user_write, webhook_read, webhook_write); legacy Integration Keys also supported
Change detection
Webhooks (REST v6 webhook subscriptions) fire near-real-time on agreement events such as created, action requested, completed, and cancelled; polling GET /agreements by modifiedDate is the fallback
Capabilities
read · write · webhooks
Rate limits
Per-user throttling at minute, hour, and day tiers shared between web UI and API traffic; exceeding a tier returns HTTP 429 with a Retry-After header. Exponential backoff with jitter is recommended.

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

    Choose tables

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

Adobe Sign 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 Adobe Sign and Lever.

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