Greenhouse is retiring Harvest API v1 and v2 on August 31, 2026. If you use Greenhouse with Zapier, you must update your Zaps before August 26, 2026 to avoid disruption.
What is changing
Greenhouse is deprecating triggers, actions, and searches that rely on their older Harvest API. Zapier is releasing Greenhouse version 2.0.0, which uses Harvest v3 and OAuth 2.0 authentication.
- New Greenhouse Zaps: After version 2.0.0 is promoted, new Zaps must connect to Greenhouse through the new OAuth 2.0 flow. Your current Greenhouse connection will not appear when you create a new Zap.
- Existing Greenhouse Zaps: Existing Zaps will remain on version 1.5.1 until you update them. You will not be able to reconnect with a new API key.
Why this is happening
Greenhouse is modernizing their API to improve performance, security, and reliability. The Harvest v3 API offers better efficiency and follows current API best practices.
For more technical details, review Greenhouse's Harvest API overview.
Which Greenhouse steps are affected
If you use any of the following triggers, actions, or searches in your Zaps, you must update them:
- New Candidate Application
- New Job Post
- Candidate Hired
- New Scheduled Interview
- Job Updated
- New Scorecard Due
- API Request (Beta)
- Create Candidate Note
- Create Candidate
- Create Prospect
- Update Candidate
- Find Candidate
- Find Due Scorecard
What you need to do
You must update your Zaps before August 26, 2026 to avoid disruption. After this date, Zaps using deprecated steps will stop working.
Find your affected Zaps
- Log into Zapier and go to My Apps.
- In the search box, enter Greenhouse and select it to view your Greenhouse Zaps.
- Click each Zap and check whether a step name matches the affected steps listed above.
Update your Zaps
For each affected Zap, in the Zap editor:
- Click the affected Greenhouse step.
- In the Setup tab, click Change to update to the newest Greenhouse integration version.
- Click Reconnect to connect your Greenhouse account using the new OAuth 2.0 flow.
- In the Account dropdown menu, select your new Greenhouse connection.
- In the Setup tab, review and reconfigure the step's fields. Available fields or output mappings may have changed.
- Remap your fields in all downstream steps (later Zap steps that use this output).
- Click Test step to pull in the latest data.
- Click Publish to save your changes.
- Click the toggle switch to turn your Zap back on.
Update API Request or custom action steps
If you use the API Request action or custom action, you must migrate your request to the Harvest v3 API:
- Update the URL field to use the new Harvest v3 endpoint.
- Update the Headers and Body fields to match the Harvest v3 API requirements.
- Reconfigure any authentication parameters as needed.
Review Greenhouse's Harvest v3 partner integration guidance for endpoint and authentication changes.
Timeline
| Phase | Date | What happens |
|---|---|---|
| Action required | Before August 26, 2026 | Update and reconnect your Greenhouse Zaps |
| Zapier deprecation | August 26, 2026 | Greenhouse version 1.5.1 stops working |
| Greenhouse API cutoff | August 31, 2026 | Harvest API v1 and v2 are retired |
Need help?
- Review how to get started with Greenhouse on Zapier for an overview of available triggers, searches, and actions.
- Check common problems with Greenhouse on Zapier for troubleshooting tips.
- Contact Zapier Support if you need assistance updating your Zaps.
NoteThis information was accurate at the time of publication. Check the latest product update notes for any updates or changes.