Skip to content
Database ⇄ Human resources

Dynamo DB to Lever integration — real-time, two-way sync

Keep Dynamo DB 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 Dynamo DB and Lever

Put your workforce data where your apps can reach it: Dynamo DB and Lever share the same people, positions, and org structure in real time.

Lever is the system of record for the people side of the business — employees, candidates, roles, and the org structure around them. Dynamo DB is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Users, Stages, Feedback, Interviews in Lever need to exist as queryable Global Tables, Tables, Items, Attributes in Dynamo DB before an app can act on them. When that bridge is a nightly export or a hand-run CSV, every downstream system spends the day working from a roster that has already moved on.

Stacksync syncs Global Tables, Tables, Items, Attributes in Dynamo DB with Users, Stages, Feedback, Interviews in Lever field by field, in real time. You decide which system owns which fields — Lever typically owns identity and org attributes, while operational or computed values can flow back the other way — and Stacksync keeps every copy consistent, matching records on a stable key and resolving conflicts by rules you set.

The result is one live picture of the workforce on both sides: HR keeps its source of truth, and the database keeps a current mirror that internal apps, reports, and access controls can trust without a batch window in between.

Common use cases

  • 01 Stream item changes from DynamoDB application tables into a Postgres or warehouse copy for SQL analytics.
  • 02 Sync customer records between DynamoDB-backed services and a CRM so support and sales see live application state.
  • 03 When an Opportunity is marked hired, write the candidate and its Offer into an HRIS or onboarding system to start employee provisioning.
  • 04 Consolidate Feedback, Interviews, and Notes into a warehouse for interviewer scorecard and time-to-fill reporting.

Common sync patterns

Mirror people records into the database

Records maintained in Lever land as queryable Global Tables, Tables, Items, Attributes in Dynamo DB, so internal apps and dashboards read live data instead of a periodic export.

One directory of record

When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.

Reporting and analytics on current data

Users, Stages, Feedback, Interviews replicate into Dynamo DB where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.

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

Dynamo DB objects Lever objects How this pairing syncs
Global Secondary Indexes Alternate access paths used when sync queries filter on non-key attributes. 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. Global Secondary Indexes is specific to Dynamo DB and Postings to Lever — each maps to any object or custom field on the other side.
DynamoDB Streams Ordered item-level change records consumed for incremental sync. 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. DynamoDB Streams is specific to Dynamo DB and Requisitions to Lever — each maps to any object or custom field on the other side.
Global Tables Multi-region replicas relevant when syncs must read from a specific region. 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. Global Tables is specific to Dynamo DB and Offers to Lever — each maps to any object or custom field on the other side.
Tables The top-level containers a sync targets; each table is addressed independently. Users Lever team members (recruiters, hiring managers) with configurable roles; can be created via POST /users, deactivated, and reactivated through the API. Tables is specific to Dynamo DB and Users to Lever — each maps to any object or custom field on the other side.
Items Schemaless records keyed by partition (and optional sort) key, mapped to rows or SaaS objects in syncs. Stages Pipeline stage definitions that Opportunities move through; read to model funnel state and stage transitions in a database. Items is specific to Dynamo DB and Stages to Lever — each maps to any object or custom field on the other side.
Attributes Per-item fields, including nested maps and lists, flattened or mapped during sync. Feedback Interview feedback and scorecard forms attached to Opportunities; created via POST /opportunities/:id/feedback and consolidated into a warehouse for interviewer analytics. Attributes is specific to Dynamo DB and Feedback to Lever — each maps to any object or custom field on the other side.

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

Dynamo DB Lever Sub-second propagation

DetectionChanges in Dynamo DB are captured at the source via change data capture — no polling loop against its API. Item-level change streams via DynamoDB Streams or Kinesis Data Streams integration.

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

Lever Dynamo DB 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 applied to Dynamo DB as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Dynamo DB: Throughput is governed by the table's provisioned or on-demand capacity mode.
  • 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 Dynamo DB ⇄ Lever

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Dynamo DB and Lever connectors work

Dynamo DB

Integration surface
Proprietary JSON-over-HTTPS API accessed through AWS SDKs; PartiQL supported for SQL-like queries
Authentication
AWS IAM credentials with SigV4 request signing
Change detection
Item-level change streams via DynamoDB Streams or Kinesis Data Streams integration
Capabilities
read · write · CDC
Rate limits
Throughput is governed by the table's provisioned or on-demand capacity mode

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

    Choose tables

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

Dynamo DB 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 450 integrations available for Dynamo DB and Lever.

Popular · 7 of 450
All Dynamo DB 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