Greenhouse is an applicant tracking system and recruiting software designed to optimize your entire recruiting process. Find better candidates, conduct more focused interviews, and make data-driven hiring decisions.
Featureslink
| Feature Name | Supported | Notes |
|---|---|---|
| Capture deletes | check | APPLICATION, CANDIDATE, DEPARTMENT, INTERVIEW, JOB, JOB_POST, JOB_STAGE, OFFER, OFFICE, and SCORECARD tables |
| Custom data | check | APPLICATION, CANDIDATE, JOB, and OFFER tables |
| Data blocking | check | Column level |
| Column hashing | check | |
| Re-sync | check | Connector level |
| History | check | |
| API configurable | check | API configuration |
| Priority-first sync | ||
| Fivetran data models | check | Get the models: source / transform |
| Private networking |
Setup guidelink
Follow our step-by-step Greenhouse setup guide to connect Greenhouse with your destination using Fivetran connectors.
Sync overviewlink
Fivetran syncs Greenhouse data created on January 1, 2012 and later.
Schema informationlink
This schema applies to all Greenhouse connections.
To zoom, open the ERD in a new window.
Webhook to table mappinglink
While most Greenhouse tables are updated through the Greenhouse API, some are updated through a combination of the API and webhooks. Webhooks allow Fivetran to capture state changes which are not available through the Greenhouse API. That lets us capture deletes and history.
| Webhook | Parent Table(s) Updated |
|---|---|
| APPLICATION CREATED | APPLICATION_HISTORY |
| APPLICATION DELETED | APPLICATION |
| CANDIDATE HIRED | APPLICATION_HISTORY |
| CANDIDATE MERGED | CANDIDATE |
| CANDIDATE STAGE CHANGED | APPLICATION_HISTORY |
| CANDIDATE UNHIRED | APPLICATION_HISTORY |
| CANDIDATE REJECTED | APPLICATION_HISTORY |
| CANDIDATE UNREJECTED | APPLICATION_HISTORY |
| CANDIDATE DELETED | CANDIDATE |
| DEPARTMENT DELETED | DEPARTMENT |
| INTERVIEW DELETED | INTERVIEW |
| JOB CREATED | JOB_HISTORY |
| JOB UPDATED | JOB_HISTORY |
| JOB DELETED | JOB |
| JOB POST DELETED | JOB_POST |
| JOB STAGE DELETED | JOB_STAGE |
| OFFER CREATED | OFFER_HISTORY |
| OFFER UPDATED | OFFER_HISTORY |
| OFFER DELETED | OFFER |
| OFFICE DELETED | OFFICE |
| SCORECARD DELETED | SCORECARD |
We create an entry in the parent history table in the destination for events such as APPLICATION CREATED, JOB CREATED, and OFFER CREATED. We update the history table during the periodic sync and not as part of the event cycle.
We sync the updated data into the history table. However, some table-level updates may not be available in the history table due to a lack of information from the source API.
Greenhouse webhooks limitationlink
Greenhouse doesn’t trigger webhooks if you use the Bulk Actions option to reject candidates. We can’t capture bulk rejection updates because of this limitation, and you may observe data discrepancies.