Skip to content
Accounting and finance ⇄ Human resources

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

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

Keep the employee, department, and cost records that Coupa and Greenhouse share consistent in real time, so the finance system and the people system stop drifting apart.

Coupa runs the money side of the company: who gets paid, what it costs, and which part of the business the cost belongs to. Greenhouse runs the people side: who works here, which team they sit in, and how their employment changes over time. The two overlap on the same people and the same org structure, because every employee is also a payee and every department is also a cost center. When that overlap is maintained by hand, a new hire, a transfer, or a termination has to be keyed twice, and the two systems start to disagree about who is active and where the cost lands.

Stacksync syncs Expense Reports, Requisitions, Purchase Orders, Invoices in Coupa with Offers, Scorecards, Scheduled Interviews, Users in Greenhouse bi-directionally and in real time. A person added, updated, or deactivated on either side appears on the other within seconds, with field-level mapping and conflict resolution in place of CSV exports and nightly batch jobs.

That matters most when money follows a people event. A hire that finance can pay, a leaver whose access ends, a transfer that redirects cost to the right team, all happen from one change instead of two, so headcount and spend reconcile from the same set of records.

Common use cases

  • 01 Mirror Purchase Orders and their status into an operational Postgres database for spend reporting and three-way match analytics.
  • 02 Export approved Invoices and their lines from Coupa into an accounting/ERP system to drive the AP pay cycle and GL posting.
  • 03 Export Scorecards and Scheduled Interviews to a data warehouse to analyze interviewer load and interview outcomes.
  • 04 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.

Common sync patterns

People-driven costs land in finance

Compensation, reimbursements, or other costs tied to a person on the Greenhouse side flow into Coupa for posting, so the books reflect what people actually cost without manual re-entry.

New person becomes a known record in finance

When someone is added in Greenhouse, a matching employee or payee record appears in Coupa, ready for payroll, expenses, or cost allocation without anyone rekeying the details.

One employee identity

A person's name, ID, or contact details corrected in either system update the other, so finance and HR reference the same person instead of maintaining two versions.

What you can sync between Coupa and Greenhouse

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.

Coupa objects Greenhouse objects How this pairing syncs
Users Employee and user accounts with roles and content groups; provisioned and updated from an HRIS or identity provider. Users Greenhouse users (recruiters, hiring managers); read and written, and referenced by the On-Behalf-Of header on every write. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Suppliers Supplier master records; kept aligned with an ERP vendor master and onboarding tools, synced two-way on the /suppliers resource. Scheduled Interviews Interview events with interviewers, times, and rooms; full create/update/delete support for calendar and reporting syncs. Suppliers is specific to Coupa and Scheduled Interviews to Greenhouse — each maps to any object or custom field on the other side.
Accounts Chart-of-accounts segments and GL codes; usually mastered in the ERP and written into Coupa so requisitions and invoices code correctly. Departments and Offices Org structure attached to Jobs; read and written to keep reporting hierarchies aligned with an HRIS or warehouse. Accounts is specific to Coupa and Departments and Offices to Greenhouse — each maps to any object or custom field on the other side.
Contracts Supplier contract records with terms and dates; read out for reporting or created from a CLM system. Candidates Person records with contact details, tags, and custom fields; read and written via Harvest, often created from sourcing or enrichment pipelines. Contracts is specific to Coupa and Candidates to Greenhouse — each maps to any object or custom field on the other side.
Expense Reports Employee expense reports and their lines; exported to AP or ERP for reimbursement and GL posting. Applications Links a Candidate to a Job; carries current stage, status, and source. Movable, rejectable, and hireable through Harvest write calls. Expense Reports is specific to Coupa and Applications to Greenhouse — each maps to any object or custom field on the other side.
Requisitions Employee purchase requests with lines and approval chains; read out to warehouses, or created via the API from upstream intake tools. Jobs Requisitions with openings, hiring team, departments, and offices; created and patched via Harvest, read out for funnel and time-to-fill reporting. Requisitions is specific to Coupa and Jobs to Greenhouse — each maps to any object or custom field on the other side.

How changes propagate between Coupa and Greenhouse

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.

Coupa Greenhouse Interval-based propagation

DetectionStacksync polls Coupa for changes on an incremental schedule, reading only records changed since the previous pass. Polling on updated-at and created-at filters (e.g.

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

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

Rate-limit considerations

  • Coupa: Coupa does not publish explicit rate limits or expose X-RateLimit/Retry-After headers; integrations page 50 records at a time and back off on 429/503 responses.
  • 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.
What ships with Coupa ⇄ Greenhouse

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Coupa and Greenhouse connectors work

Coupa

Integration surface
REST Core API (JSON or XML)
Authentication
OAuth 2.0 / OIDC via the client-credentials grant; scopes take the service.object.right form (e.g. core.accounting.read, core.accounting.write). Legacy API keys are being retired (no new keys since R34; API-key auth unsupported from R36). Access tokens last 24 hours.
Change detection
Polling on updated-at and created-at filters (e.g. updated-at[gt]=<timestamp>); Coupa has no native webhook subscriptions, though admins can configure outbound Call Out / external notifications.
Capabilities
read · write
Rate limits
Coupa does not publish explicit rate limits or expose X-RateLimit/Retry-After headers; integrations page 50 records at a time and back off on 429/503 responses.

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
How it works

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

    Choose tables

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

Coupa and Greenhouse 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 501 integrations available for Coupa and Greenhouse.

Popular · 8 of 501
All Coupa integrations All Greenhouse 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