Skip to content
Business productivity ⇄ Human resources

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

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

Keep the people, teams, and status that Atlassian 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 Atlassian 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 Workflows and Statuses, Users and Groups, Confluence Pages, Confluence Spaces in Atlassian 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 Atlassian within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Atlassian 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 Mirror Jira projects into a SQL database for engineering throughput and SLA reporting.
  • 02 Create Jira issues from records in other systems, such as onboarding tasks generated from a closed-won CRM deal.
  • 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

Offboarding: no standing access after a departure

When someone is marked as leaving in Lever, the matching account in Atlassian is deactivated or flagged, so departures do not leave open access behind.

One employee directory

A person's name, title, contact details, or status corrected in either system updates the other, so both sides stop maintaining separate copies of the same person.

Org and team structure kept current

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

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

Atlassian objects Lever objects How this pairing syncs
Custom Fields Instance-specific fields (customfield IDs) that carry most business-specific data in syncs. Feedback Interview feedback and scorecard forms attached to Opportunities; created via POST /opportunities/:id/feedback and consolidated into a warehouse for interviewer analytics. Custom Fields is specific to Atlassian and Feedback to Lever — each maps to any object or custom field on the other side.
Workflows and Statuses Status transitions mapped to stages in the paired system. Interviews Scheduled interview panel events with times and interviewers; read for scheduling reporting and time-to-hire metrics, and creatable via the panels endpoint. Workflows and Statuses is specific to Atlassian and Interviews to Lever — each maps to any object or custom field on the other side.
Users and Groups Assignees and reporters matched to identities in other tools. 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. Users and Groups is specific to Atlassian and Notes and Contacts to Lever — each maps to any object or custom field on the other side.
Confluence Pages Documentation content readable and writable through the Confluence REST API. 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. Confluence Pages is specific to Atlassian and Opportunities to Lever — each maps to any object or custom field on the other side.
Confluence Spaces Namespaces that scope page syncs and permissions. 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. Confluence Spaces is specific to Atlassian and Postings to Lever — each maps to any object or custom field on the other side.
Jira Issues The central work item, synced two-way with CRMs, support desks, and other trackers. 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. Jira Issues is specific to Atlassian and Requisitions to Lever — each maps to any object or custom field on the other side.

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

Atlassian Lever Sub-second propagation

DetectionAtlassian notifies Stacksync of record changes through webhook events. Webhooks on issue and page events, plus JQL polling on the updated timestamp for backfill.

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

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

Rate-limit considerations

  • 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 Atlassian ⇄ Lever

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Atlassian and Lever connectors work

Atlassian

Integration surface
REST APIs per product (Jira Cloud and Confluence Cloud)
Authentication
OAuth 2.0 (3LO) for apps or API tokens with basic auth for scripts
Change detection
Webhooks on issue and page events, plus JQL polling on the updated timestamp for backfill
Capabilities
read · write · webhooks

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

    Choose tables

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

Atlassian 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 444 integrations available for Atlassian and Lever.

Popular · 8 of 444
All Atlassian 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