Release Notes

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 or . Learn more about our dbt Core integration in our *.

* 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

We now support syncing demographic data if you have a . 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 . Read Greenhouse's for more information.

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.

June 2020

We now sync job opening updates with increased accuracy.

October 2019

We have added a new field, 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

November 2018

The JOB table now includes the field name.
The SCHEDULED_INTERVIEW table now includes the fields start and end.

October 2018

The timestamp field now supports two new datetime formats, UTC (ex. '2018-06-27 23:51:40 UTC') and Java TimeZone (ex. '2018-07-03T22:49:22.689Z').

We have changed the id column in the CANDIDATE_TAG table to tag_id.

We have created a number of new primary keys:

candidate_id and index are the new primary keys for the following tables:
- PHONE_NUMBER
- EMAIL_ADDRESS
- WEBSITE_ADDRESS
- ATTACHMENT
- SOCIAL_MEDIA_ADDRESS
- ADDRESS
scorecard_id and index are the new primary keys for the following tables:
- SCORE_CARD_ATTRIBUTE
- SCORE_CARD_QNA
application_id and index are the new primary keys for the APPLICATION_QNA table.
job_post_id and index are the new primary keys for the JOB_POST_QUESTION table.

August 2018

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.