Skip to content
Human resources ⇄ Business productivity

Greenhouse to Lemlist integration — real-time, two-way sync

Keep Greenhouse and Lemlist 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 Greenhouse and Lemlist

Keep the people, teams, and status that Lemlist and Greenhouse share aligned in real time, so a hire, role change, or departure recorded in one reaches the other within seconds.

Each tool in Lemlist 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. Greenhouse 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 Unsubscribes, Webhooks, Team Members, Campaigns in Lemlist with Candidates, Applications, Jobs, Offers in Greenhouse bi-directionally and in real time. A person added, moved, or offboarded in Greenhouse creates or updates the matching user in Lemlist within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Lemlist captures details of its own, such as a corrected contact or a login identity, those can flow back to Greenhouse 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 Propagate unsubscribes and bounces back to the CRM and other outreach tools for suppression compliance
  • 02 Stop or pause sequences automatically when a reply converts to a deal in the CRM
  • 03 Two-way sync Candidates and Applications with Postgres so recruiting-ops apps read and update stage, status, and custom fields in SQL while recruiters stay in Greenhouse.
  • 04 Write enriched or sourced Candidates from external tools into Greenhouse and keep contact fields refreshed as data changes.

Common sync patterns

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

When someone changes teams or managers in Greenhouse, the queues, ownership, or approvals in Lemlist update to match, so work reaches whoever holds the role now.

Onboarding: access ready on day one

A new hire recorded in Greenhouse creates the matching user in Lemlist 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 Greenhouse, the matching account in Lemlist is deactivated or flagged, so departures do not leave open access behind.

What you can sync between Greenhouse and Lemlist

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.

Greenhouse objects Lemlist objects How this pairing syncs
Candidates Person records with contact details, tags, and custom fields; read and written via Harvest, often created from sourcing or enrichment pipelines. Activities Engagement records such as opens, clicks, replies, and bounces sync to CRM timelines. Candidates is specific to Greenhouse and Activities to Lemlist — each maps to any object or custom field on the other side.
Applications Links a Candidate to a Job; carries current stage, status, and source. Movable, rejectable, and hireable through Harvest write calls. Unsubscribes Opt-out records propagate to other outreach tools and the CRM for compliance. Applications is specific to Greenhouse and Unsubscribes to Lemlist — each maps to any object or custom field on the other side.
Jobs Requisitions with openings, hiring team, departments, and offices; created and patched via Harvest, read out for funnel and time-to-fill reporting. Webhooks Hook subscriptions define which activity events are pushed to external endpoints. Jobs is specific to Greenhouse and Webhooks to Lemlist — each maps to any object or custom field on the other side.
Offers Offer records tied to an Application with status and custom offer fields; readable and patchable, commonly synced to HRIS on hire. Team Members Sender and seat records map outreach activity to reps in other systems. Offers is specific to Greenhouse and Team Members to Lemlist — each maps to any object or custom field on the other side.
Scorecards Interviewer feedback and ratings tied to interviews; read-only in Harvest, exported to a warehouse for interview analytics. Campaigns Outreach campaigns are the container leads are pushed into from CRMs and list-building workflows. Scorecards is specific to Greenhouse and Campaigns to Lemlist — each maps to any object or custom field on the other side.
Scheduled Interviews Interview events with interviewers, times, and rooms; full create/update/delete support for calendar and reporting syncs. Leads Per-campaign prospect records sync in from enrichment sources and back out with status. Scheduled Interviews is specific to Greenhouse and Leads to Lemlist — each maps to any object or custom field on the other side.

How changes propagate between Greenhouse and Lemlist

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.

Greenhouse Lemlist Sub-second propagation

DetectionGreenhouse notifies Stacksync of record changes through webhook events. HMAC-SHA256 signed webhooks for candidate, application, job, and interview events, plus polling list endpoints with created_after / updated_after /.

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

Lemlist Greenhouse Sub-second propagation

DetectionLemlist notifies Stacksync of record changes through webhook events. Webhooks on outreach activity events, plus polling.

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

Rate-limit considerations

  • Greenhouse: Harvest enforces a per-integration limit over a rolling 10-second window (X-RateLimit-Limit, commonly 50 requests / 10s for approved integrations); responses carry X-RateLimit-Remaining and, on a 429, X-RateLimit-Reset and Retry-After.
  • Lemlist: Subject to the platform's API rate limits.
What ships with Greenhouse ⇄ Lemlist

Connect Greenhouse and Lemlist for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in Greenhouse or Lemlist instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Greenhouse or Lemlist 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 Greenhouse or Lemlist record.

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Greenhouse and Lemlist.

How the Greenhouse and Lemlist connectors work

Greenhouse

Integration surface
Harvest REST API (plus read-only Job Board API and the Ingestion API for bulk candidate import)
Authentication
HTTP Basic Auth with a Harvest API key (key as username, blank password, colon appended then Base64-encoded); write calls require an On-Behalf-Of header naming the Greenhouse user
Change detection
HMAC-SHA256 signed webhooks for candidate, application, job, and interview events, plus polling list endpoints with created_after / updated_after / last_activity_after filters
Capabilities
read · write · webhooks
Rate limits
Harvest enforces a per-integration limit over a rolling 10-second window (X-RateLimit-Limit, commonly 50 requests / 10s for approved integrations); responses carry X-RateLimit-Remaining and, on a 429, X-RateLimit-Reset and Retry-After.
Greenhouse setup guide

Lemlist

Integration surface
REST API
Authentication
API key
Change detection
Webhooks on outreach activity events, plus polling
Capabilities
read · write · webhooks
Rate limits
Subject to the platform's API rate limits
How it works

How to connect Greenhouse to Lemlist — 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 Greenhouse and Lemlist 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
    Greenhouse connected
    Lemlist connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Greenhouse and Lemlist 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 391 integrations available for Greenhouse and Lemlist.

Popular · 7 of 391
All Greenhouse integrations All Lemlist 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