Greenhouse vs Ashby as the ATS for Rippling (2026)
Last updated: November 11, 2026 | Reviewed by IntegrateStack Editorial | 2 native integrations compared
Both Greenhouse and Ashby send a hired candidate's offer details to Rippling natively. They work from opposite ends. With Greenhouse, the person onboarding the hire in Rippling imports them from Greenhouse. With Ashby, the recruiter pushes the hire out of Ashby, or Ashby does it on its own once you turn on automatic pushes.
Choose Ashby if you want hires to reach Rippling without anyone clicking. Choose Greenhouse if you need EEOC answers and referral credit to carry over, or want Rippling to manage Greenhouse logins.
Greenhouse carries EEOC data; Ashby carries equity
The field lists overlap on the basics (name, email, phone, salary, start date, title, department, location, signing bonus) and differ after that.
| Greenhouse → Rippling | Ashby → Rippling | |
|---|---|---|
| Direction | Rippling pulls candidate and offer data from Greenhouse. Rippling also provisions and suspends Greenhouse user accounts. | One-way, Ashby to Rippling |
| Trigger | In Rippling's onboarding flow: Import from my ATS › Greenhouse | Add to Rippling on a Hired candidate, or automatic push after the first manual one |
| Candidate fields | Name, email, phone, Rejected At, race/ethnicity (EEOC), gender (EEOC) | Name, email, phone |
| Offer fields | Job title, start date, salary, signing bonus, currency, work location, department | Salary and start date by default. Optional: department, equity shares, job title, signing bonus, work location |
| Other data | Employment type from the employment_type custom field; Referred By from the application's credited_to | Offer letters. File uploads don't sync. |
| Setup | Greenhouse: create a Harvest API key (partner: Rippling). Rippling: app store › Greenhouse › Connect Existing Account, paste the key. | Ashby: Admin › Integrations › Rippling › Connect to Rippling, install the app in Rippling, return and pick fields. |
| Plans | Neither vendor's integration doc states a plan requirement. | |
| Source | Greenhouse: Rippling integration. Checked Nov 2026. | Ashby: Rippling. Checked Nov 2026. |
Greenhouse hires are imported from inside Rippling
The connection lives in Rippling, keyed with a Greenhouse Harvest API key. Marking a candidate hired in Greenhouse doesn't send them anywhere. The hire arrives when whoever runs onboarding in Rippling picks Import from my ATS and selects Greenhouse, which fills the new-hire record from the candidate and offer.
Two fields need setup on the Greenhouse side or they arrive empty:
- Employment type comes from a custom field named
employment_typeon the offer or job. The value has to match a type Rippling knows, such as Full-time, Part-time, Contract, Temporary or Intern. - Referred By comes from the application's
credited_touser, and only maps if that Greenhouse user is already synced into Rippling.
The Harvest key needs read access to Applications, Candidates, Scorecards, Offers, Scheduled Interviews, Custom Locations, Jobs, Job Stages, Custom Fields and Custom Field Options. It also needs write access to Users, because the same app lets Rippling create, update and disable your team's Greenhouse logins and offer SSO into Greenhouse. If your security team questions a write-scoped key, that is the reason.
Setup notes for this pair: Rippling + Greenhouse integration.
Ashby pushes hires, by hand or automatically
Once a candidate accepts an offer and is marked Hired, their Ashby profile shows Add to Rippling. Clicking it creates the person in Rippling with data from their latest offer and logs the push in the candidate's activity feed. If Ashby is connected to more than one HRIS, you choose which ones receive the hire.
To skip the click, enable Automatically push hired candidates to HRIS integrations under Admin › Integrations › HRIS Integrations. The checkbox becomes available after you have pushed one candidate by hand.
Two things catch teams out after the push:
- The person lands in Rippling as a candidate. Someone still clicks Hire in Rippling and picks the applicant-tracking-system option to finish onboarding.
- A pushed candidate can't be pushed again. Check the offer fields before you click, and correct anything missing in Rippling itself.
Setup notes for this pair: Rippling + Ashby integration.
Common questions
Does Greenhouse integrate with Rippling?
Yes, natively. In Rippling, connect the Greenhouse app with a Greenhouse Harvest API key. When you onboard a new hire in Rippling, choose Import from my ATS and select Greenhouse to bring over the candidate and offer details. The same app lets Rippling provision and suspend Greenhouse user accounts.
Does Ashby integrate with Rippling?
Yes, natively. Install the Ashby app in Rippling from Ashby's Admin > Integrations > Rippling page and choose which fields to sync. When a candidate is marked Hired, click Add to Rippling on their profile to create them in Rippling with data from their latest offer.
Can Ashby send hires to Rippling automatically?
Yes. Turn on "Automatically push hired candidates to HRIS integrations" under Admin > Integrations > HRIS Integrations. Ashby only allows this after at least one candidate has been pushed to Rippling by hand.
What Harvest API permissions does Rippling need for Greenhouse?
Read (GET) on Applications, Candidates, Scorecards, Offers, Scheduled Interviews, Custom Locations, Jobs, Job Stages, Custom Fields and Custom Field Options, plus read and write on Users so Rippling can add, update and disable Greenhouse users. Create the key with API type Harvest and partner Rippling.
Why did employment type not import from Greenhouse to Rippling?
Rippling reads it from the employment_type custom field on the offer or job, and the value must match a known type such as Full-time, Part-time, Contract, Temporary or Intern. Any other value is not imported.
Can I push the same Ashby candidate to Rippling twice?
No. Ashby says there is no way to re-push a candidate once they have been sent to a post-hire system. Fix missing values in Rippling directly, and contact Rippling support if a field that should have been sent did not arrive.
Sources
Vendor documentation, checked November 11, 2026.