Skip to content
Human resources ⇄ CRM

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

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

Keep the people who own accounts in Shopify in step with the workforce records in Greenhouse, so ownership, roles, and org structure stay current in both systems, in real time and in both directions.

Shopify runs on people as much as on accounts: every contact, deal, and account has an owner, and those owners are employees whose roles, teams, and status are held in Greenhouse. Greenhouse is the system of record for the workforce, from new hires to promotions to departures, and often for the candidates the business is still deciding on. When the two systems are connected only by re-keying or an overnight export, they drift apart, and the CRM ends up assigning accounts to people who have left, holding territories that no longer match the org chart, and waiting days to give a new rep access.

Stacksync syncs Abandoned Checkouts, Products, ProductMedias, ProductVariants in Shopify with Applications, Jobs, Offers, Scorecards in Greenhouse field by field, in real time, and in both directions. You decide which system owns which fields, so Greenhouse stays authoritative on roles and org structure while Shopify keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.

Common use cases

  • 01 Sync orders, customers, and inventory into Postgres for operational reporting across stores.
  • 02 Keep customer records aligned between Shopify and a CRM for segmentation and lifetime-value analysis.
  • 03 Stream Jobs, Departments, and Offices into a reporting database for recruiting funnel and time-to-fill dashboards.
  • 04 Export Scorecards and Scheduled Interviews to a data warehouse to analyze interviewer load and interview outcomes.

Common sync patterns

Where Greenhouse tracks people the business also engages: contacts stay in sync

A person recorded in Greenhouse, such as a candidate or applicant, can create or update the matching contact in Shopify, so relationship history and outreach are not rebuilt from scratch when the same individual appears in both.

New team members provisioned when they are hired

When Greenhouse records a new hire, a matching user or owner is created in Shopify, so a new rep can start working accounts without waiting on a manual setup ticket.

Ownership and territory follow the org chart

When a person changes team, manager, or region in Greenhouse, their accounts and territory assignments in Shopify update to match, so pipeline stays with the right owner.

What you can sync between Greenhouse and Shopify

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 Shopify 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. ProductVariants Synced with incremental and full sync per the Stacksync docs. Candidates is specific to Greenhouse and ProductVariants to Shopify — 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. Orders Purchase transactions; pushed to ERPs for fulfillment and billing, and read into databases for reporting. Applications is specific to Greenhouse and Orders to Shopify — 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. Customers Buyer records; matched to CRM contacts for marketing and lifetime-value analysis. Jobs is specific to Greenhouse and Customers to Shopify — 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. Abandoned Checkouts Synced with incremental and full sync per the Stacksync docs. Offers is specific to Greenhouse and Abandoned Checkouts to Shopify — 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. Products Catalog entries; often mastered in a PIM or ERP and written into Shopify. Scorecards is specific to Greenhouse and Products to Shopify — 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. ProductMedias Synced with incremental and full sync per the Stacksync docs. Scheduled Interviews is specific to Greenhouse and ProductMedias to Shopify — each maps to any object or custom field on the other side.

How changes propagate between Greenhouse and Shopify

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

Shopify Greenhouse Sub-second propagation

DetectionShopify notifies Stacksync of record changes through webhook events. Webhook topics per resource, with polling on updated_at as a fallback.

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.
  • Shopify: GraphQL uses a calculated query-cost budget; the REST API uses a leaky-bucket model.
What ships with Greenhouse ⇄ Shopify

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Greenhouse ⇄ Shopify 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 Shopify.

How the Greenhouse and Shopify 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

Shopify

Integration surface
GraphQL Admin API (primary) and REST Admin API (legacy)
Authentication
OAuth via a custom Shopify app: admin creates an app in the Shopify Dev Dashboard, enables required API scopes, sets the Stacksync redirect URL, then supplies shop name + Client ID and Client Secret to Stacksync
Change detection
Webhook topics per resource, with polling on updated_at as a fallback
Capabilities
read · write · webhooks
Rate limits
GraphQL uses a calculated query-cost budget; the REST API uses a leaky-bucket model.
Shopify setup guide
How it works

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

    Choose tables

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

Greenhouse and Shopify 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 532 integrations available for Greenhouse and Shopify.

Popular · 8 of 532
All Greenhouse integrations All Shopify 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