.png)
Connect Greenhouse and Rippling to automate the handoff from offer acceptance to day-one readiness — triggering payroll setup, benefits enrollment, IT provisioning, and onboarding tasks from a single hire event.
The first thing we do is map every field in the client's Greenhouse offer templates to the corresponding Rippling employee attributes. Standard fields — name, email, start date, title, department, manager, compensation — are straightforward, but most mid-market companies have custom offer fields that need to be explicitly mapped or they'll arrive in Rippling as blank attributes that require manual correction later.
We then configure the Harvest API key in Greenhouse with the correct permissions, connect the integration in Rippling's App Shop, and design the onboarding workflow that fires on the hire event — including payroll entity routing, benefits enrollment triggers, IT provisioning rules, and onboarding task assignment. For companies with multiple entities or international hiring, we build routing logic that directs each hire to the correct entity, payroll schedule, and benefits configuration automatically.
Before go-live, we run the integration through a set of test hire scenarios — including at least one international hire, one contractor, and one edge case like a rehire or a hire into an unusual employment type — to confirm the workflow handles each correctly before it processes real candidates.
For US companies hiring across multiple states, confirm that state-specific fields (work location, tax state) are captured in the Greenhouse offer before the integration fires — these drive payroll entity routing and state tax configuration in Rippling and are frequently missing from default offer templates. For Canadian and ROW companies, international hires must route to the correct legal entity and payroll schedule in Rippling based on work location; the Canadian entity must be fully configured in Rippling before the Greenhouse integration is enabled, and entity-routing logic must be explicitly built into the provisioning rules — otherwise all hires default to the US primary entity.
The integration is triggered when a candidate reaches the designated hire stage in Greenhouse — typically when an offer is accepted and the candidate is marked as hired. At that point, Greenhouse pushes the candidate's name, email, phone, address, job title, start date, manager, department, and compensation fields into Rippling, where an employee record is created and the onboarding workflow begins. Payroll setup, benefits enrollment, IT provisioning, and onboarding task assignment all trigger from this single event.
The standard integration is a one-way sync from Greenhouse to Rippling — candidate and offer data flows into Rippling at the hire event, but Rippling does not push data back into Greenhouse for standard setups. Some organizations configure custom workflows to push offboarding or status signals back to Greenhouse for reporting purposes, but this requires custom development beyond the native integration.
Yes — any custom offer fields or job fields configured in Greenhouse can be mapped to custom attributes in Rippling during the integration setup. This is important for organizations that capture role-specific data in Greenhouse offers — equity details, sign-on bonuses, variable comp structures — that need to flow into the Rippling employee record accurately. Custom field mapping requires validation during setup to confirm field types and required values match on both sides.
Rippling extends the Greenhouse hire event beyond HR into IT and finance. When a candidate is marked as hired in Greenhouse, Rippling can automatically provision their email account, Slack, and other applications, order and ship a pre-configured laptop to their home address, enroll them in the correct benefits plan, and add them to the right payroll run — all triggered from a single hire event in Greenhouse. No other HRIS integration with Greenhouse automates this full scope from one trigger.
Yes — the Greenhouse-to-Rippling handoff is one of the most impactful configurations we set up for clients that use both platforms. We handle the Harvest API key setup in Greenhouse, field mapping between the two systems, onboarding workflow design in Rippling triggered by the hire event, and testing with a handful of simulated hires before go-live. We also design the provisioning rules so that international hires route to the correct entity and payroll configuration automatically.
