Connector Improvement: Greenhouse Application History ReSync and New Fields
AnsweredThe application_history table is one of the most important tables that we use to create metrics in recruiting data analytics.
Right now, that history can only exist back to when we set up the webhooks in Greenhouse. It's crucial that we get the rest of the history from our Greenhouse instance. I can try to muscle my way through calling the API myself and then appending this to the application_history table you provide, but if you're able to do this it would be much more clean.
I would also love it if you can give the entered_on and exited_on fields like they do in the Greenhouse ERD.
Thank you!
-
Official comment
Hi Chris,
For the APPLICATION_HISTORY table is built using webhooks, as you mentioned, Greenhouse does not provide a way to get the history of changes to a record. We do have an APPLICATION table, which captures the last modified status of the record. If a greenhouse provided a way, we would be able to support it.
Regarding entered_on and exited_on - This data is available in their v3 API, which they released recently.
We will be upgrading our connector to v3 APIs later this year - and we will be able to add APPLICATION_STAGE table with that information - https://harvestdocs.greenhouse.io/reference/get_v3-application-stages
-
Hi @Vishal Ray. We are experiencing the same issue as Chris. This data is crucial for our reporting. What is the status of the upgrade to v3 of the Greenhouse API? We are especially interested in the entered_on and exited_on fields.
-
Hi David,
We understand this is an important update. However, due to other priorities, the API upgrade has been pushed to Q1, and we are targeting completion around April–May. We will definitely reach out once this is ready for early rollout.
Best regards,
Vishal -
Hi @Vishal Ray,
I am David Wasserman's colleague. I understand the v3 API has been released by FiveTran, but when I connect and review the schema, I do not see the APPLICATION_STAGE table or the addition of the entered_on and exited_on fields in any other table.
Can you please advise on where/if this information is captured in the v3 API update? Thank you
Please sign in to leave a comment.
Comments
4 comments