Skip to content
Human resources ⇄ ERP

Greenhouse to SAP S/4HANA integration — real-time, two-way sync

Keep Greenhouse and SAP S/4HANA 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 SAP S/4HANA

Sync the workers, org structure, and cost centers that SAP S/4HANA and Greenhouse share in real time, so the people Greenhouse manages stay current in the system that runs finance and operations.

Greenhouse is the system of record for people: who was hired, which department and location they sit in, who they report to, and how they are paid. SAP S/4HANA runs finance and operations, and much of what it does depends on that same information, from booking labor cost to approving an expense report to staffing a project. Where the two are bridged by re-keying or an overnight file, each side spends the day out of step, with new hires missing from the systems they need and leavers still active where they should not be.

Stacksync syncs Sales Orders, Purchase Orders, Products / Materials, Billing Documents (Invoices) in SAP S/4HANA with Jobs, Offers, Scorecards, Scheduled Interviews in Greenhouse field by field, in real time, and in both directions. You decide which system owns which fields, so the people side stays authoritative for worker data while SAP S/4HANA keeps its own accounting and operational detail, and every change made in one is reflected in the other within seconds instead of at the next batch run.

Common use cases

  • 01 Push closed-won CRM opportunities into S/4HANA as sales orders without manual re-keying.
  • 02 Surface invoice and payment status from S/4HANA inside the CRM so account teams see open balances.
  • 03 Write enriched or sourced Candidates from external tools into Greenhouse and keep contact fields refreshed as data changes.
  • 04 Stream Jobs, Departments, and Offices into a reporting database for recruiting funnel and time-to-fill dashboards.

Common sync patterns

Where Greenhouse runs payroll: labor cost in the books

Pay and compensation data from Greenhouse posts into SAP S/4HANA as labor cost, so finance sees workforce spend without re-entering it by hand.

Where Greenhouse is the worker system of record: one employee master

When a worker is hired, moved, or offboarded in Greenhouse, the matching employee record in SAP S/4HANA is created, updated, or deactivated, so the business system reflects the workforce as it actually is.

New hires ready to transact in SAP S/4HANA

A new person set up in Greenhouse becomes an employee record in SAP S/4HANA in time to submit expenses, enter time, or approve a purchase, without waiting on manual setup.

What you can sync between Greenhouse and SAP S/4HANA

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 SAP S/4HANA objects How this pairing syncs
Scorecards Interviewer feedback and ratings tied to interviews; read-only in Harvest, exported to a warehouse for interview analytics. Deliveries Outbound delivery status synced to customer-facing systems for order tracking. Scorecards is specific to Greenhouse and Deliveries to SAP S/4HANA — 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. Journal Entries Financial postings read into warehouses and consolidation tools for reporting. Scheduled Interviews is specific to Greenhouse and Journal Entries to SAP S/4HANA — each maps to any object or custom field on the other side.
Users Greenhouse users (recruiters, hiring managers); read and written, and referenced by the On-Behalf-Of header on every write. Customer / Supplier Roles Role-specific views of Business Partners mapped to CRM account types. Users is specific to Greenhouse and Customer / Supplier Roles to SAP S/4HANA — each maps to any object or custom field on the other side.
Departments and Offices Org structure attached to Jobs; read and written to keep reporting hierarchies aligned with an HRIS or warehouse. Production Orders Manufacturing order status surfaced in planning and operations tools. Departments and Offices is specific to Greenhouse and Production Orders to SAP S/4HANA — each maps to any object or custom field on the other side.
Candidates Person records with contact details, tags, and custom fields; read and written via Harvest, often created from sourcing or enrichment pipelines. Business Partners Unified customer and supplier master records, the anchor entity for CRM-to-ERP account syncs. Candidates is specific to Greenhouse and Business Partners to SAP S/4HANA — 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. Sales Orders Order headers and line items synced to CRMs and fulfillment systems as they are created or amended. Applications is specific to Greenhouse and Sales Orders to SAP S/4HANA — each maps to any object or custom field on the other side.

How changes propagate between Greenhouse and SAP S/4HANA

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 SAP S/4HANA 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 SAP S/4HANA through its API, with automatic retries and rate-limit backoff.

SAP S/4HANA Greenhouse Interval-based propagation

DetectionStacksync polls SAP S/4HANA for changes on an incremental schedule, reading only records changed since the previous pass. Polling on change timestamps exposed by the OData services.

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.
  • SAP S/4HANA: Subject to the platform's API rate limits, which vary by edition and communication arrangement.
What ships with Greenhouse ⇄ SAP S/4HANA

Connect Greenhouse and SAP S/4HANA for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Greenhouse–SAP S/4HANA connection.

Real-time

Two-way sync

Changes in Greenhouse or SAP S/4HANA instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Greenhouse or SAP S/4HANA 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 SAP S/4HANA record.

Observability

Monitoring

Track your Greenhouse ⇄ SAP S/4HANA 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 SAP S/4HANA.

How the Greenhouse and SAP S/4HANA 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

SAP S/4HANA

Integration surface
OData REST APIs (v2/v4), with SOAP, BAPI/RFC, and IDoc interfaces on on-premise editions
Authentication
OAuth 2.0 with communication arrangements on cloud editions; basic auth or certificate-based on-premise
Change detection
Polling on change timestamps exposed by the OData services; business events can be emitted through SAP's event infrastructure on cloud editions
Capabilities
read · write
Rate limits
Subject to the platform's API rate limits, which vary by edition and communication arrangement
How it works

How to connect Greenhouse to SAP S/4HANA — 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 SAP S/4HANA 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
    SAP S/4HANA connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Greenhouse and SAP S/4HANA 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 509 integrations available for Greenhouse and SAP S/4HANA.

Popular · 7 of 509
All Greenhouse integrations All SAP S/4HANA 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