Skip to content
Business productivity ⇄ Human resources

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

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

Keep the people, teams, and status that Asana 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 Asana 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 Projects, Sections, Custom fields, Stories in Asana 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 Asana within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Asana 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 Projects, Sections, and Portfolios into a warehouse for cross-team reporting on status, timelines, and workload without CSV exports.
  • 02 Push support tickets or intake requests from an operational database into Asana Tasks, then read completion and status Custom fields back when work finishes.
  • 03 Push Postings and Requisitions into an HRIS or warehouse to reconcile approved headcount against open roles.
  • 04 When an Opportunity is marked hired, write the candidate and its Offer into an HRIS or onboarding system to start employee provisioning.

Common sync patterns

Onboarding: access ready on day one

A new hire recorded in Lever creates the matching user in Asana with the right team and manager already set, so people can start working without waiting on a provisioning ticket.

Offboarding: no standing access after a departure

When someone is marked as leaving in Lever, the matching account in Asana 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.

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

Asana objects Lever objects How this pairing syncs
Users Members of a workspace or organization referenced by assignee and follower fields; read to resolve GIDs to names and emails. 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.
Portfolios Collections of Projects for program-level rollup; read for cross-project status and progress reporting (Business and Enterprise). Interviews Scheduled interview panel events with times and interviewers; read for scheduling reporting and time-to-hire metrics, and creatable via the panels endpoint. Portfolios is specific to Asana and Interviews to Lever — each maps to any object or custom field on the other side.
Tags Labels applied across Tasks; synced as a many-to-many attribute for filtering and categorization. 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. Tags is specific to Asana and Notes and Contacts to Lever — each maps to any object or custom field on the other side.
Teams / Workspaces Organizational containers that hold projects and members; used to scope which projects a given sync covers. 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. Teams / Workspaces is specific to Asana and Opportunities to Lever — each maps to any object or custom field on the other side.
Tasks The primary unit of work and main record; created, updated, completed, and deleted via REST and synced two-way. Subtasks are Tasks with a parent reference. 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 Asana and Postings to Lever — each maps to any object or custom field on the other side.
Projects Collections of Tasks with a layout (list, board, timeline, calendar); each project maps to a synced table scope and its custom fields define the mapping. 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. Projects is specific to Asana and Requisitions to Lever — each maps to any object or custom field on the other side.

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

Asana Lever Sub-second propagation

DetectionAsana notifies Stacksync of record changes through webhook events. Resource-scoped webhooks (established with an X-Hook-Secret handshake) POST events on create, change, and delete.

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

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

Rate-limit considerations

  • Asana: Per token: 1,500 requests/minute on paid plans, 150/minute on free; the Search API is capped at 60/minute; concurrency caps at 50 GET and 15 write requests. Exceeding a limit returns HTTP 429 with a Retry-After header, and a separate cost-based limiter applies to complex graph traversals.
  • 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 Asana ⇄ Lever

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Asana and Lever connectors work

Asana

Integration surface
REST API (app.asana.com/api/1.0, JSON responses), plus resource-scoped Webhooks and a sync-token Events API
Authentication
OAuth 2.0 for multi-user apps, Personal Access Tokens (PATs) for single-account use and testing, and organization-scoped Service Accounts (Enterprise) for admin-level access
Change detection
Resource-scoped webhooks (established with an X-Hook-Secret handshake) POST events on create, change, and delete; the sync-token Events API returns incremental changes on a task or project when webhooks are not used
Capabilities
read · write · webhooks
Rate limits
Per token: 1,500 requests/minute on paid plans, 150/minute on free; the Search API is capped at 60/minute; concurrency caps at 50 GET and 15 write requests. Exceeding a limit returns HTTP 429 with a Retry-After header, and a separate cost-based limiter applies to complex graph traversals.

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

    Choose tables

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

Asana 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 Asana and Lever.

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