HiBob connector: jobProfileId and Job Catalog not available, though HiBob says its API exposes them
AnsweredHello Fivetran Support,
We are missing job profile data from the HiBob connector, and we would like your help understanding why and what our options are. We have copied our contacts at HiBob, who have confirmed the details below from their side.
Connector: HiBob (connection ID: nutshell_apostolic)
Schema: hibob
Destination: Prod_DW (Redshift)
What we are seeing
- The hibob.employee table has no jobProfileId column, and neither does the work history table (hibob.employee_work_history).
- The Job Catalog is not available as a table in the connector, so there is nothing for us to enable.
- HiBob has confirmed that jobProfileId and the Job Catalog are exposed through the same API the connector uses. This looks like a gap in connector coverage rather than a permissions or configuration problem on our side.
Why it matters
Our People team needs job profile data for reporting in our internal data warehouse, and we cannot build it from what the connector syncs today.
Questions
1. Does the HiBob connector support jobProfileId and the Job Catalog? If yes, how do we enable them?
2. If not, is support planned? Is there a roadmap item or feature request we can add ourselves to?
3. If it is not planned, what do you recommend? We are considering a narrow custom pull for only the missing pieces, built with the Fivetran Connector SDK, so that it lands in the same destination without duplicating the standard sync. Is that the supported route?
We can share a screenshot of the connector's schema tab and the current column list for hibob.employee if that would help.
Thank you,
Rishabh Gupta
Juniper Square
-
Official comment
Hi Rishabh,
Thank you for reaching out and providing detailed information. We've added your request for jobProfileId and Job Catalog support in the HiBob connector to our active backlog. This feature will be prioritized based on demand, and we will keep you updated on any progress.
Best,
Sanjeevv Maniram
Please sign in to leave a comment.
Comments
1 comment