Greenhouse
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.
Features
| Feature Name | Supported | Notes |
|---|---|---|
| Capture deletes | check | APPLICATION, CANDIDATE, DEPARTMENT, SCHEDULED_INTERVIEW, JOB, JOB_POST, JOB_STAGE, OFFER, OFFICE, and SCORECARD tables<br/> |
| History mode | ||
| Custom data | check | APPLICATION, CANDIDATE, JOB, and OFFER tables |
| Data blocking | check | |
| Column hashing | check | |
| Re-sync | check | |
| API configurable | check | API configuration |
| Priority-first sync | ||
| Fivetran data models | check | |
| Private networking | ||
| Authorization via API | check |
Setup guide
Follow our step-by-step Greenhouse setup guide to connect Greenhouse with your destination using Fivetran connectors.
Sync overview
Fivetran syncs Greenhouse data created on January 1, 2012 and later.
Sync note
The Greenhouse API provides the attachments through temporary URLs. These URLs are valid for 30 days and expire after 7 days of accessing them. Due to the ephemeral nature of these URLs, we recommend that you download the attachments as soon as you get the URLs as they may not be available for future use. For more information, see Greenhouse's documentation.
Schema information
This schema applies to all Greenhouse connections created before July 24, 2024.
To zoom, open the ERD in a new window.This schema applies to all Greenhouse connections created on or after July 24, 2024.
To zoom, open ERD in new window
Webhook to table mapping
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 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 DELETED | JOB |
| JOB POST DELETED | JOB_POST |
| JOB STAGE DELETED | JOB_STAGE |
| 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 limitation
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.
UTC conversion
We don't convert source timestamps to Universal Time Coordinated (UTC) but use the Greenhouse account's time zone to store the data in your destination.