Skip to content
ERP ⇄ Human resources

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

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

Sync the workers, org structure, and cost centers that Cin7 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. Cin7 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 Products, Inventory levels, Sales orders, Purchase orders in Cin7 with Departments and Offices, Candidates, Applications, Jobs 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 Cin7 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 Consolidate stock movements from multiple branches into one reporting database.
  • 02 Publish Cin7 inventory levels to storefronts, marketplaces, and a CRM so every channel quotes real availability.
  • 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 is the worker system of record: one employee master

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

New hires ready to transact in Cin7

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

One org structure

Departments, cost centers, and locations that both systems reference stay in agreement, so labor cost, approvals, and reporting in Cin7 roll up to the same structure Greenhouse maintains.

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

Cin7 objects Greenhouse objects How this pairing syncs
Inventory levels Stock on hand by branch or location, published outward for availability. Candidates Person records with contact details, tags, and custom fields; read and written via Harvest, often created from sourcing or enrichment pipelines. Inventory levels is specific to Cin7 and Candidates to Greenhouse — each maps to any object or custom field on the other side.
Sales orders Orders captured from all channels; the main object for fulfillment and revenue syncs. Applications Links a Candidate to a Job; carries current stage, status, and source. Movable, rejectable, and hireable through Harvest write calls. Sales orders is specific to Cin7 and Applications to Greenhouse — each maps to any object or custom field on the other side.
Purchase orders Supplier orders synced with procurement and accounting workflows. Jobs Requisitions with openings, hiring team, departments, and offices; created and patched via Harvest, read out for funnel and time-to-fill reporting. Purchase orders is specific to Cin7 and Jobs to Greenhouse — each maps to any object or custom field on the other side.
Contacts Customers and suppliers, matched to CRM records to keep account data consistent. Offers Offer records tied to an Application with status and custom offer fields; readable and patchable, commonly synced to HRIS on hire. Contacts is specific to Cin7 and Offers to Greenhouse — each maps to any object or custom field on the other side.
Branches / locations Warehouse entities that scope every stock movement and order allocation. Scorecards Interviewer feedback and ratings tied to interviews; read-only in Harvest, exported to a warehouse for interview analytics. Branches / locations is specific to Cin7 and Scorecards to Greenhouse — each maps to any object or custom field on the other side.
Stock adjustments and transfers Inventory movements read for audit and reconciliation reporting. Scheduled Interviews Interview events with interviewers, times, and rooms; full create/update/delete support for calendar and reporting syncs. Stock adjustments and transfers is specific to Cin7 and Scheduled Interviews to Greenhouse — each maps to any object or custom field on the other side.

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

Cin7 Greenhouse Sub-second propagation

DetectionCin7 notifies Stacksync of record changes through webhook events. Polling on modified-date filters.

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

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

Rate-limit considerations

  • Cin7: Subject to per-account API rate limits that differ between Cin7 Omni and Cin7 Core.
  • 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 Cin7 ⇄ Greenhouse

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Cin7 and Greenhouse connectors work

Cin7

Integration surface
REST API; note that Cin7 Omni and Cin7 Core (formerly DEAR Systems) are separate products with separate APIs
Authentication
API key credentials (paired with a username or account ID, depending on the product)
Change detection
Polling on modified-date filters; webhook support exists on some editions for order and stock events
Capabilities
read · write · webhooks
Rate limits
Subject to per-account API rate limits that differ between Cin7 Omni and Cin7 Core

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

    Choose tables

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

Cin7 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 500 integrations available for Cin7 and Greenhouse.

Popular · 8 of 500
All Cin7 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