Skip to content
Data warehouse ⇄ Human resources

Amazon Redshift to Lever integration — real-time, two-way sync

Keep Amazon Redshift 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 Amazon Redshift and Lever

Land the people and organization records from Lever in Amazon Redshift as live tables for workforce reporting, without extract jobs, and write computed results back where Lever can use them.

Workforce data is some of the most requested data in the warehouse and some of the most awkward to move: the record types are many, the fields carry sensitive personal information, the APIs are strict, and hand-built extract jobs go stale or break quietly. Whether Lever is the system of record for employees and payroll, for candidates and applications, or for learners and course completions, the reporting belongs in Amazon Redshift next to everything else the company measures.

Stacksync syncs Opportunities, Postings, Requisitions, Offers from Lever into tables in Amazon Redshift continuously, handling API limits and schema drift as they come. The connection is bi-directional, so values computed in Amazon Redshift, such as headcount rollups, cost allocations, or attrition risk flags, can be written back to fields in Lever where the HR team acts on them. You configure which records and fields cross over, and in which direction, instead of maintaining pipeline code.

Common use cases

  • 01 Feed customer 360 tables built in Redshift to support and success platforms.
  • 02 Centralize CRM, ERP, and product data in Redshift so analysts join it with warehouse tables.
  • 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

Write-back of computed values

Segments, rollups, or risk flags computed in Amazon Redshift sync back onto the matching records in Lever, where the HR team sees them in the system they already use.

HR data in the warehouse, minus the pipeline

People and organization records from Lever arrive in Amazon Redshift as queryable tables, current within seconds instead of a day behind, replacing hand-built extract jobs.

Headcount and cost joined with everything else

Analysts combine Lever's workforce records with finance, product, or operational data already in Amazon Redshift for reporting the HR system cannot produce on its own.

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

Amazon Redshift objects Lever objects How this pairing syncs
Views SQL views readable as modeled sources for reverse syncs. Interviews Scheduled interview panel events with times and interviewers; read for scheduling reporting and time-to-hire metrics, and creatable via the panels endpoint. Views is specific to Amazon Redshift and Interviews to Lever — each maps to any object or custom field on the other side.
Materialized Views Precomputed results that downstream syncs can read for performance. 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. Materialized Views is specific to Amazon Redshift and Notes and Contacts to Lever — each maps to any object or custom field on the other side.
External Tables (Spectrum) S3-backed tables queryable through Redshift, readable in syncs. 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. External Tables (Spectrum) is specific to Amazon Redshift and Opportunities to Lever — each maps to any object or custom field on the other side.
Stored Procedures SQL procedures sometimes invoked around load steps. 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. Stored Procedures is specific to Amazon Redshift and Postings to Lever — each maps to any object or custom field on the other side.
Users and Groups Principals used to grant a sync connection scoped access. 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. Users and Groups is specific to Amazon Redshift and Requisitions to Lever — each maps to any object or custom field on the other side.
Databases Top-level containers within a cluster or serverless workgroup. 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. Databases is specific to Amazon Redshift and Offers to Lever — each maps to any object or custom field on the other side.

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

Amazon Redshift Lever Interval-based propagation

DetectionStacksync polls Amazon Redshift for changes on an incremental schedule, reading only records changed since the previous pass. Polling or query-based diffing.

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

Lever Amazon Redshift 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 Amazon Redshift as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Amazon Redshift: Bounded by cluster or serverless capacity and concurrency settings rather than API quotas.
  • 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 Amazon Redshift ⇄ Lever

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Amazon Redshift and Lever connectors work

Amazon Redshift

Integration surface
SQL over JDBC/ODBC (PostgreSQL-derived protocol); Redshift Data API over HTTPS
Authentication
Database credentials or IAM-based authentication
Change detection
Polling or query-based diffing; Redshift does not expose a transaction log for external CDC consumers
Capabilities
read · write
Rate limits
Bounded by cluster or serverless capacity and concurrency settings rather than API quotas

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

    Choose tables

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

Amazon Redshift 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 542 integrations available for Amazon Redshift and Lever.

Popular · 8 of 542
All Amazon Redshift 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