Release Notes
October 2024
We now sync the following webhook events through the incrementally sync. Previously, we synced them through our webhooks.
Webhook | Updated parent table |
---|---|
CANDIDATE HIRED | APPLICATION_HISTORY |
JOB CREATED | JOB_HISTORY |
JOB UPDATED | JOB_HISTORY |
OFFER CREATED | OFFER_HISTORY |
OFFER UPDATED | OFFER_HISTORY |
The data previously fetched from these events will now be synced through our incrementally sync.
NOTE: This change applies only to the integrations created after 2024-07-24.
We have renamed the USER
table to USERS
. For more information, see our Schema information
August 2024
For connectors created on or after July 18, 2024, we have enabled table-level selection or deselection for the Greenhouse connector.
July 2024
We have made the following changes to the Schema tab for connectors created on or after July 18, 2024:
- We display all table names in lowercase
- We display all the tables, including the empty tables
- We no longer support table-level selection and deselection for syncing
We have made the following schema changes for connectors created on or after July 18, 2024:
- Added the
primary_email_address
column in theUSERS
table - Removed the
is_primary
column from theUSER_EMAIL
table - Renamed the
TAG
table toTAGS
- Renamed the
end
column toends
in theSCHEDULED_INTERVIEW
table - Renamed the
from
andto
columns in theEMAIL
table tofroms
andtos
- Renamed the
default
andfrom
columns in theEMAIL_TEMPLATE
table tois_default
andfroms
March 2024
We have made the following schema changes:
- added the
responsible
column to theHIRING_TEAM
table - added the
opened_at
column to theJOB
table
Be sure to re-sync the JOB
table to backfill the historical data for these tables or contact Fivetran's support team to re-sync it for you.
September 2023
We have added new Quickstart packages for the following connectors:
* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.
October 2022
We have added a new column, active
, to the JOB_STAGE
table.
January 2022
We have added a new column, job_post_id
, to the APPLICATION
table.
November 2021
We have added a new column, is_template
, to the JOB
table.
October 2021
We have added a new column, priority
, to the JOB_STAGE
table.
May 2021
You can now exclude the EEOC
table from your syncs. On your Connector Details page, go to the Schema tab and deselect the table.
April 2021
We have added a new table, DEMOGRAPHIC_ANSWER
.
We have added a new table, USER_LINKED_CANDIDATE
, which stores the user linked candidate IDs.
We have added a new column, is_primary
, to the USER_EMAIL
table.
We have added a new column, can_email
, to the CANDIDATE
table.
March 2021
We have released pre-built, dbt Core-compatible data models for Greenhouse. Find the models in Fivetran's dbt hub or data models documentation. Learn more about our dbt Core integration in our Transformations for dbt Core documentation*.
* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.
December 2020
We have added a new column, veteran_status_description
, to replace the veteran_status_message
column in the EEOC
table. We have made this change because the Greenhouse API does not send veteran_status_message
data. If you have previously synced the EEOC table, trigger a table re-sync to ensure data integrity.
We now sync Greenhouse data created on January 1, 2012 and later. Previously, we synced data created on January 1, 1970 and later. Only syncing data back to 2012 makes your historical syncs faster. Any historical syncs that you've already run will not be affected by this change.
October 2020
We have made our syncs more resilient to server failures from Greenhouse. If we can't connect to Greenhouse's servers during our syncs, we now retry the connection three times before the sync fails. Previously, our syncs failed immediately.
July 2020
If you have a Greenhouse Expert plan, we add the following tables when you grant Fivetran access to the demographics endpoint:
DEMOGRAPHIC_QUESTION_SET
DEMOGRAPHIC_QUESTIONS
DEMOGRAPHIC_ANSWER_OPTION
We have also added custom fields to the JOB_OPENING
table.
We now support syncing demographic data if you have a Greenhouse Expert plan. Fivetran requires access to the demographic endpoint to sync demographic data. To grant Fivetran access, create an API key with the demographic endpoint in Greenhouse, then enter the API key in your Fivetran connector setup form. Read Greenhouse's Harvest API Key Permissions documentation for more information.
June 2020
We now sync job opening updates with increased accuracy.
October 2019
We have added a new column, name
, to the OFFICE
table.
January 2019
Application_created
, job_created
, and offer_created
events can now create entries in the history table. The main entity will continue to be updated during periodic syncs, not during the event cycle. You can find additional details in our Greenhouse Setup Guide.
November 2018
We have added a new column, name
, to the JOB
table.
We have added two new columns, start
and end
, to the SCHEDULED_INTERVIEW
table.
October 2018
The timestamp
column now supports two new datetime formats:
- UTC (For example, '2018-06-27 23:51:40 UTC')
- Java TimeZone (For example, '2018-07-03T22:49:22.689Z')
We have renamed the id
column to tag_id
in the CANDIDATE_TAG
table.
We have changed the primary key columns for the following tables:
candidate_id
andindex
are the new primary keys for the following tables:ADDRESS
ATTACHMENT
EMAIL_ADDRESS
PHONE_NUMBER
SOCIAL_MEDIA_ADDRESS
WEBSITE_ADDRESS
scorecard_id
andindex
are the new primary keys for the following tables:SCORE_CARD_ATTRIBUTE
SCORE_CARD_QNA
application_id
andindex
are the new primary keys for theAPPLICATION_QNA
table.job_post_id
andindex
are the new primary keys for theJOB_POST_QUESTION
table.
August 2018
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.