Two-way sync
Changes in Greenhouse or Sysaid instantly reflect in both systems. No stale data, no manual imports.
Keep Greenhouse and Sysaid in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Each tool in Sysaid keeps its own list of who can use it: users, members, or agents, along with the team they sit on and whether they are still active. Greenhouse is the authoritative record of the same people as employees, with their department, manager, and employment status. When those two are connected only by manual account admin or a periodic export, the work tools drift: new hires wait days for access, team and manager changes never catch up, and people who have left keep standing accounts.
Stacksync syncs Custom Fields, Incidents, Service Requests, Problems in Sysaid with Jobs, Offers, Scorecards, Scheduled Interviews in Greenhouse bi-directionally and in real time. A person added, moved, or offboarded in Greenhouse creates or updates the matching user in Sysaid within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Sysaid captures details of its own, such as a corrected contact or a login identity, those can flow back to Greenhouse in whichever direction you configure.
Because the sync is field-level, each system keeps its own extras; only the shared facts, who a person is, which team they belong to, and whether their access should be on, are held in agreement.
A new hire recorded in Greenhouse creates the matching user in Sysaid with the right team and manager already set, so people can start working without waiting on a provisioning ticket.
When someone is marked as leaving in Greenhouse, the matching account in Sysaid is deactivated or flagged, so departures do not leave open access behind.
A person's name, title, contact details, or status corrected in either system updates the other, so both sides stop maintaining separate copies of the same person.
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 | Sysaid objects | How this pairing syncs | |
|---|---|---|---|
| Users Greenhouse users (recruiters, hiring managers); read and written, and referenced by the On-Behalf-Of header on every write. | Users End users and admins on the /users endpoint; synced with an HRIS or identity source to keep requester and agent records current. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Applications Links a Candidate to a Job; carries current stage, status, and source. Movable, rejectable, and hireable through Harvest write calls. | Changes Change records (type=change) with approval and scheduling fields; synced two-way to drive CAB review and deployment workflows. | Applications is specific to Greenhouse and Changes to Sysaid — 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. | Assets Hardware and software inventory; read out to a warehouse or written from a discovery or CMDB source of truth. | Jobs is specific to Greenhouse and Assets to Sysaid — 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. | Configuration Items (CIs) CMDB entries and their relationships; synced with an external CMDB or asset database for one inventory view. | Offers is specific to Greenhouse and Configuration Items (CIs) to Sysaid — 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. | Companies Customer and department organizations that scope tickets and users; mapped to Accounts in a CRM or org tables in a database. | Scorecards is specific to Greenhouse and Companies to Sysaid — 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. | Custom Fields Org-specific fields on service records, discoverable through the API so mappings can be generated without hardcoding names. | Scheduled Interviews is specific to Greenhouse and Custom Fields to Sysaid — each maps to any object or custom field on the other side. |
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.
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 Sysaid through its API, with automatic retries and rate-limit backoff.
DetectionSysaid notifies Stacksync of record changes through webhook events. Webhooks (beta) push sr.created and sr.updated events with changed-field diffs and an X-Sysaid-Signature.
DeliveryEach detected change is written to Greenhouse through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Greenhouse–Sysaid connection.
Changes in Greenhouse or Sysaid instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Greenhouse or Sysaid data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Greenhouse or Sysaid record.
Track your Greenhouse ⇄ Sysaid sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Greenhouse and Sysaid.
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.
Authenticate Greenhouse and Sysaid with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Greenhouse and Sysaid 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Greenhouse and Sysaid: authenticate both systems, choose the objects to sync (such as Greenhouse's Users and Applications), map fields visually, and changes propagate both ways in milliseconds — no code required.
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. Sysaid: REST API (JSON). Authentication: Client-credentials app keys: an application key (clientId/clientSecret) is created via /v1/application-keys, then exchanged at /v1/access-tokens for a bearer token (default 24h, up to 30 days); an x-sysaid-accountid header scopes the account. Legacy V0 uses session-cookie login. Stacksync manages authentication, retries, and rate limits on both sides.
Sysaid: Incidents, service requests, problems, and changes all share the /api/v1/sr endpoint and are distinguished by a type parameter rather than separate resources. Greenhouse: Harvest API keys are permission-scoped per endpoint, so a sync only reaches the objects the key is explicitly granted. Stacksync's field mapping accounts for these differences between Greenhouse and Sysaid without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Greenhouse and Sysaid records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Greenhouse and Sysaid connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Greenhouse–Sysaid integration in-house.
Yes — Stacksync ships production-grade connectors for both Greenhouse and Sysaid. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 511 integrations available for Greenhouse and Sysaid.