Real-time
Two-way sync
Changes in Greenhouse or Linnworks instantly reflect in both systems. No stale data, no manual imports.
Human resources ⇄ ERP
Greenhouse to Linnworks integration — real-time, two-way sync
Keep Greenhouse and Linnworks 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 Linnworks
Sync the workers, org structure, and cost centers that Linnworks 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. Linnworks 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 Open Orders, Processed Orders, Stock Items, Stock Levels in Linnworks 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 the people side stays authoritative for worker data while Linnworks 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 Sync orders from Linnworks into an ERP or accounting system as they are processed, without CSV exports
- 02 Keep stock levels consistent between Linnworks and external systems so multichannel listings stay aligned with sellable stock
- 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
New hires ready to transact in Linnworks
A new person set up in Greenhouse becomes an employee record in Linnworks 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 Linnworks roll up to the same structure Greenhouse maintains.
Reporting lines drive approvals
Manager and reporting-hierarchy changes in Greenhouse keep expense and purchase approval chains in Linnworks pointed at the right people.
What you can sync between Greenhouse and Linnworks
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 | Linnworks 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. | Locations Warehouse and fulfillment location records scope stock data during mapping. | Candidates is specific to Greenhouse and Locations to Linnworks — 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. | Purchase Orders Replenishment POs sync with suppliers and accounting systems. | Applications is specific to Greenhouse and Purchase Orders to Linnworks — 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. | Suppliers Vendor records keep procurement data consistent across tools. | Jobs is specific to Greenhouse and Suppliers to Linnworks — 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. | Channel Listings Marketplace and webstore listing mappings tie channel products to internal SKUs. | Offers is specific to Greenhouse and Channel Listings to Linnworks — 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. | Returns & Refunds Post-sale records flow to finance and support systems. | Scorecards is specific to Greenhouse and Returns & Refunds to Linnworks — 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. | Shipping Services Carrier and service definitions support label and tracking data in order syncs. | Scheduled Interviews is specific to Greenhouse and Shipping Services to Linnworks — each maps to any object or custom field on the other side. |
How changes propagate between Greenhouse and Linnworks
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 Linnworks 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 Linnworks through its API, with automatic retries and rate-limit backoff.
Linnworks Greenhouse Interval-based propagation
DetectionStacksync polls Linnworks for changes on an incremental schedule, reading only records changed since the previous pass. Polling on order and stock endpoints.
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.
- Linnworks: Per-endpoint rate limits apply on the Linnworks API.
What ships with Greenhouse ⇄ Linnworks
Connect Greenhouse and Linnworks for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Greenhouse–Linnworks connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Greenhouse or Linnworks 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 Linnworks record.
Observability
Monitoring
Track your Greenhouse ⇄ Linnworks 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 Linnworks.
How the Greenhouse and Linnworks 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.
Linnworks
- Integration surface
- REST API
- Authentication
- Application credentials and an install token exchanged for a session token
- Change detection
- Polling on order and stock endpoints
- Capabilities
- read · write
- Rate limits
- Per-endpoint rate limits apply on the Linnworks API
How it works
How to connect Greenhouse to Linnworks — 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.
- 01
Connect your apps
Authenticate Greenhouse and Linnworks with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Greenhouse
connected
Linnworks
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Greenhouse and Linnworks 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.
objects · Greenhouse ⇄ LinnworksCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Greenhouse LinnworksCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Greenhouse and Linnworks integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Greenhouse and Linnworks: authenticate both systems, choose the objects to sync (such as Greenhouse's Candidates and Applications), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Linnworks side: Open Orders, Processed Orders, Stock Items, Stock Levels, plus custom fields where Linnworks exposes them. On the Greenhouse side: Applications, Jobs, Offers, Scorecards. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Greenhouse and Linnworks: New hires ready to transact in Linnworks; One org structure; Reporting lines drive approvals. A new person set up in Greenhouse becomes an employee record in Linnworks in time to submit expenses, enter time, or approve a purchase, without waiting on manual setup.
-
Greenhouse: 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. Linnworks: REST API. Authentication: Application credentials and an install token exchanged for a session token. Stacksync manages authentication, retries, and rate limits on both sides.
-
Linnworks: The Linnworks API uses a token-exchange model: application credentials plus a per-account install token are exchanged for a session token that authorizes subsequent calls. Greenhouse: Every write (POST, PATCH, DELETE) requires an On-Behalf-Of header carrying a valid Greenhouse user ID for the audit trail. Stacksync's field mapping accounts for these differences between Greenhouse and Linnworks without custom code.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 504 integrations available for Greenhouse and Linnworks.
Popular · 4 of 504
No integrations match .
