TL;DR Short answer: the best Greenhouse ETL tools are the ones already on Harvest v3. Greenhouse removed Harvest API v1 and v2 on 31 August 2026, so any connector still using API keys and the old endpoints has stopped working. Harvest v3 uses OAuth 2.0, cursor-based pagination and new schemas, which changes how pipelines authenticate and backfill. Seven Greenhouse ETL tools compared:
Airbyte Fivetran Workato Prismatic Merge Greenhouse reports Custom code with the Harvest API The Greenhouse constraint: Harvest v1/v2 is gone, Harvest v3 needs OAuth credentials and has different schemas, and v3 cursors only move forward, so migrated pipelines usually need a fresh backfill. Greenhouse ETL tools and Greenhouse integrations move candidates, applications, jobs, interviews, scorecards and offers out of Greenhouse and into a cloud data warehouse , BI tool or HR system. Talent and people analytics teams use them to measure time to hire, funnel conversion and recruiter capacity alongside HRIS and finance data.
What changed with the Greenhouse Harvest API? Greenhouse deprecated Harvest API v1 and v2 and removed them on 31 August 2026. Harvest v3 replaces Basic authentication with API keys by OAuth 2.0, returns opaque cursors with only a next link, and changes response schemas, for example by moving some nested objects to their own endpoints. Integrations had to move to v3 credentials and actions, and data pipelines usually needed a new backfill into new tables.
Why use Greenhouse ETL tools instead of Greenhouse reports? Greenhouse reports and Report Builder cover pipeline, time to fill, source effectiveness and interviewer activity inside Greenhouse. Talent teams usually need more: hiring data joined with HRIS records, offer data next to compensation bands, recruiter capacity against budget, and trends that survive changes to jobs and stages. That needs Greenhouse data in a warehouse, which is what Greenhouse ETL tools are for.
How do the Greenhouse ETL tools compare? Tool Best for Harvest v3 auth Deployment Pricing model Airbyte Warehouse analytics OAuth via Airbyte partner app Airbyte Cloud Volume-based on Cloud Fivetran Managed warehouse pipeline Check current setup Cloud, hybrid Monthly active rows Workato Automation and recipes OAuth 2.0 authorization code Cloud Platform subscription Prismatic Embedded customer integrations OAuth 2.0 client credentials Cloud Platform subscription Merge Unified ATS API for products Handled by Merge Cloud Subscription by linked accounts Greenhouse reports In-app recruiting reports Not needed Inside Greenhouse Included, by plan Custom code Exact control Your own OAuth setup Wherever you run it Free, engineering time
Which Greenhouse ETL tools should you consider? Seven Greenhouse ETL tools, from warehouse ELT to Greenhouse's own reports:
1. Airbyte Airbyte is one of the leading open-source ELT tools , with 700+ connectors, and among Greenhouse ETL tools it was early to move to Harvest v3. Version 1.0.0 of its Greenhouse source authenticates through Airbyte's registered Greenhouse partner application: a Greenhouse Site Admin approves the consent flow, and Airbyte stores and rotates the refresh token. Because it depends on those partner credentials, the connector is available on Airbyte Cloud.
The move to v3 was a breaking change: Airbyte recommends a new connection writing to a new namespace or table prefix, keeping existing Harvest v1 tables as history, because v3 schemas and identifiers differ.
Pros Cons Already on Harvest v3 with managed OAuth Available on Airbyte Cloud for v3 Token rotation handled for you Migration needs a new backfill and tables Greenhouse next to HRIS and 700+ sources v3 schemas differ from v1 tables
2. Fivetran Fivetran is one of the managed Greenhouse ETL tools: its Greenhouse connector loads recruiting data into a warehouse, and Fivetran's Greenhouse dbt package models it into analysis-ready tables for funnels and time to hire. Confirm how your connection authenticates after the Harvest v3 change before relying on it. Fivetran completed its merger with dbt Labs in June 2026.
Pros Cons Fully managed, with a dbt package Confirm Harvest v3 setup Analysis-ready recruiting models Monthly active row pricing Hybrid deployment option Connector behaviour cannot be modified
3. Workato Workato is one of the Greenhouse ETL tools aimed at operations teams: its Greenhouse connector supports Harvest v3 through OAuth 2.0 authorization code authentication, with v3 actions and triggers, while API key connections only reach the retired v1/v2 actions. It suits automated workflows, such as syncing hires to an HRIS, more than warehouse analytics.
Pros Cons v3 actions and triggers Automation platform, not a warehouse pipeline OAuth 2.0 authorization code Platform subscription pricing Connects Greenhouse to many systems v1/v2 recipes needed rebuilding
4. Prismatic Prismatic is an embedded integration platform for SaaS companies. Its Greenhouse connector added full Harvest v3 support in June 2026, including an OAuth 2.0 client credentials connection, v3 actions for applications, candidates, jobs and users, and a polling trigger based on last activity with cursor pagination.
Pros Cons Full Harvest v3 action coverage Built for software vendors, not internal analytics Client credentials connection Platform subscription pricing Cursor-aware polling trigger Requires building integrations
5. Merge Merge is a unified API platform for product teams: its ATS API normalises candidates, applications, jobs and interviews from Greenhouse and other applicant tracking systems into one schema, and handles authentication and API changes such as Harvest v3. Teams pairing an ATS with an HRIS should also see our guides to BambooHR ETL tools and Workable ETL tools .
Pros Cons One API for many ATS platforms Built for product integrations, not analytics Absorbs Greenhouse API changes Subscription by linked accounts Normalised recruiting models Less detail than raw Harvest fields
6. Greenhouse reports Before choosing Greenhouse ETL tools, check the built-in options. Greenhouse includes standard recruiting reports and Report Builder for custom views of pipeline, offers and interviewer activity, and reports can be exported to Excel or CSV. They answer most day-to-day hiring questions, but cannot be joined with HRIS or finance data automatically.
Pros Cons Built in, with no API changes to manage Manual exports Report Builder for custom views Cannot be joined with other data automatically Export to Excel or CSV Depth depends on your plan
7. Custom code with the Harvest API When no Greenhouse ETL tools fit a narrow need, you can call the API yourself. Harvest v3 uses OAuth 2.0 bearer tokens, cursor-based pagination with only a next link, and new endpoints for objects that v1 nested, while Greenhouse webhooks notify you of candidate and application events. You own token handling, cursors and schema changes.
Pros Cons Full control over endpoints and fields OAuth and cursor handling are on you Webhooks for recruiting events v3 schemas differ from v1 code No licence cost Ongoing maintenance
How do you get Greenhouse data into a warehouse after the v3 change? Use a connector that already supports Harvest v3, authenticate with OAuth as a Greenhouse Site Admin, and load into new tables rather than overwriting v1 history. Run a full backfill, then incremental syncs, and rebuild models against the v3 schema. Load your HRIS in the same warehouse so hires join to employee records; see our guides to Ashby ETL tools and Snowflake ETL tools .
What should you check before syncing Greenhouse? Whichever Greenhouse ETL tools you choose, most problems now come from the v3 migration and sensitive candidate data. Check these first:
Harvest v3 support: confirm your tool uses Harvest v3. Anything still on v1/v2 API keys stopped working on 31 August 2026.OAuth and Site Admin access: v3 needs OAuth credentials created or approved by a Greenhouse Site Admin. Keep scopes to the objects you need.New tables, not overwrites: v3 schemas and identifiers differ from v1. Write v3 data to new tables and keep v1 data as history.Cursor pagination: v3 cursors are opaque and only move forward. Do not store them long term, and restart failed backfills cleanly.Candidate privacy: candidate data includes personal details, resumes and feedback. Respect deletion requests and restrict warehouse access.Webhooks: Greenhouse webhooks signal events but do not replay history. Pair them with scheduled syncs.The Greenhouse Harvest API exposes recruiting data, including:
Candidates and applications: people, sources, stages, rejections and hires. Jobs and openings: requisitions, departments, offices and hiring teams. Interviews and scorecards: scheduled interviews and interviewer feedback. Offers: offer details, approvals and status. Users: recruiters, coordinators and interviewers. Custom fields: company-specific attributes on candidates, jobs and offers. How do you start pulling data from Greenhouse? If you decide to test Airbyte, setting up a Greenhouse pipeline on Harvest v3 takes three steps.
Step 1: Set up Greenhouse as a source In Airbyte Cloud, open Sources, choose New source and select Greenhouse . Click Authenticate and approve the Greenhouse consent flow as a Site Admin; Airbyte stores and rotates the refresh token.
Step 2: Set up a destination Pick where your Greenhouse data should land, such as Snowflake, BigQuery or Databricks, and use a new namespace or table prefix if you previously synced Harvest v1 data.
Step 3: Configure the connection Select candidates, applications, jobs, interviews, scorecards and offers, run a full backfill, and schedule daily runs. Start on Airbyte Cloud , where the Greenhouse partner authentication is available, or read the Airbyte Open Source docs for other connectors.
Which Greenhouse ETL tool should you choose? The right Greenhouse ETL tools are the ones on Harvest v3 that fit your use case. For recruiting analytics in a warehouse, use Airbyte for managed v3 OAuth and broad destinations, or Fivetran for a managed connector with a dbt package once you have confirmed its v3 setup. Workato suits automated workflows, Prismatic and Merge suit product teams building integrations, and Greenhouse reports cover day-to-day hiring questions. For spreadsheet reporting, see our guide to Google Sheets ETL tools .
For a wider view of the market, see our guide to the best data integration tools .
Sync Greenhouse to your warehouse with Airbyte Airbyte is one of the open-source Greenhouse ETL tools, already on Harvest v3. Replicate candidates, applications, jobs and offers next to your HRIS and 700+ other sources on Airbyte Cloud.
Try Airbyte Cloud free for 14 days or talk to our team .
Frequently Asked Questions (FAQs) 1. What are the best Greenhouse ETL tools? The best Greenhouse ETL tools now support Harvest v3. Airbyte and Fivetran suit warehouse analytics, Workato suits automated workflows, Prismatic and Merge suit product integrations, and Greenhouse reports cover in-app needs.
2. Is the Greenhouse Harvest API v1 still available? No. Greenhouse removed Harvest API v1 and v2 on 31 August 2026. Integrations must use Harvest v3, which uses OAuth 2.0 instead of API keys.
3. How do you authenticate with the Greenhouse API? Harvest v3 uses OAuth 2.0 bearer tokens. Credentials are created or approved by a Greenhouse Site Admin, and some tools, such as Airbyte, use a partner application so you approve access through a consent flow.
4. Does Greenhouse support webhooks? Yes. Greenhouse webhooks notify another system about events such as new candidates, application changes and hires. They do not replay history, so pair them with scheduled syncs.
5. Do I need to re-sync Greenhouse data after moving to Harvest v3? Usually, yes. Harvest v3 changes schemas and identifiers, so most tools recommend a fresh backfill into new tables while keeping v1 data as history.
Suggested reads BambooHR ETL Tools
Workable ETL Tools
Ashby ETL Tools
Snowflake ETL Tools
