List
Read live records straight from the Greenhouse API.
Stream Greenhouse activity feed and application stages to any warehouse or AI app.
Source
Greenhouse

Overview
The Airbyte Greenhouse connector extracts data from Greenhouse and loads it into 50+ destinations such as Snowflake, BigQuery, Databricks or Postgres, with full refresh and incremental sync. It publishes 61 streams you can select per connection.
Land 61 Greenhouse tables in 50+ destinations on a schedule you control.
Query synced Greenhouse data with filters, sorting and semantic search, without spending Greenhouse API rate limits.
Pull only the records that changed since the last run instead of reloading everything.
Authenticate Greenhouse once. The same connection powers scheduled syncs and runtime actions.
61 streams
| Sync modes | FullIncr. |
|---|
| Sync modes | FullIncr. |
|---|
| Sync modes | FullIncr. |
|---|
| Sync modes | FullIncr. |
|---|
| Sync modes | FullIncr. |
|---|
| Sync modes | FullIncr. |
|---|
Setup
First, navigate to the Greenhouse source connector page on Airbyte.com.
Click on the "Create a new connection" button.
Enter a name for your connection and click "Next".
Enter your Greenhouse API key in the "API Key" field.
Click "Test Connection" to ensure that your credentials are correct and the connection is successful.
Once the connection is successful, click "Next".
Select the tables you want to replicate from Greenhouse.
Choose the replication frequency and the destination where you want to send the data.
Click "Create Connection" to save your settings and start replicating data from Greenhouse.
It is important to note that the Greenhouse source connector on Airbyte.com allows you to replicate data from Greenhouse into your data warehouse or other destination. This can be useful for analyzing your recruiting data, tracking candidate progress, and improving your hiring process. By following the steps above, you can easily set up a connection between Greenhouse and your destination of choice, and start replicating data in just a few minutes.
| Field | Type | Description |
|---|---|---|
| credentials* | object | Not documented. |
| num_workers | integer | The number of worker threads to use for syncing. Greenhouse publishes no Harvest v3 rate-limit ceiling, so the default is conservative and all threads share a single budget. Increase this only if your Greenhouse account can support higher API usage, or lower it if you see rate-limit errors. |
| start_date | string | UTC date and time in the format YYYY-MM-DDTHH:MM:SSZ. Records updated before this date will not be replicated. If omitted, the connector replicates all history. |
4 actions
Read live records straight from the Greenhouse API.
Query synced data with filters and sorting, with no API rate limits.
Natural-language search across synced Greenhouse records.
Pull the binary contents of an attachment.
Full parameter-level details live in the Greenhouse entity reference.
Hybrid deployment
The data plane runs in your environment. Records, credentials and keys stay with you; the control plane only receives configuration and job metadata.
Your environment
Airbyte control plane
Use cases
List all open jobs
Show me recent interviews
Show me recent job offers
List recent applications
Show me candidates from company who applied last month
What are the top 5 sources for our job applications this quarter?
Analyze the interview schedules for our engineering candidates this week
Compare the number of applications across different offices
Identify candidates who have multiple applications in our system
Summarize the candidate pipeline for our latest job posting
Find the most active departments in recruiting this month
FAQ
No. One Greenhouse authorization powers both the scheduled syncs that land data in your destination and the entity actions your agents call at runtime.
No. Entity actions read and write through the Greenhouse API as they are called, so they work immediately. Context store search is the exception: it queries data Airbyte has already synced, which is what lets it filter and sort without spending API rate limits.
61 streams, including activity feed, application stages, applications, applied candidate tags, approvals, approver groups, approvers, attachments and more.
Yes. The Greenhouse connector supports incremental sync on selected streams, and full refresh on every stream.
Run the Greenhouse connector on Cloud, OSS, Hybrid. Hybrid deployments keep the data plane in your environment while the control plane orchestrates syncs.
Didn't find your answer? Talk to sales
Free 14-day trial. One connection powers your scheduled syncs and your live Greenhouse actions.