Skip to main content

Community

Connector Improvement: BambooHR Salary Data

Please sign in to leave a comment.

Comments

4 comments

  • Official comment

    Hi Chetan

    Thank you for reaching out to us and for sharing your valuable feedback regarding the BambooHR connector. We appreciate your input and the specific use case you've highlighted, as it helps us understand the diverse needs of our users.

    After careful consideration, we want to inform you that while implementing the requested feature is not currently on our immediate timeline, we have added it to our backlog for future consideration. The prioritization of features is based on the demand from our user community.

    Regarding your suggestion about pulling in Salary information, we understand the importance of this data for your organization. We are actively exploring options to enhance our connector's functionality and would greatly appreciate any additional insights you can provide.

    In that context, if you're comfortable sharing, could you provide more information about the data subprocessors you mentioned that offer similar capabilities? Any details you can provide about their functionalities or specific features would be incredibly valuable as we work towards improving our connector.

    Additionally, to ensure we align our development efforts with your organization's needs, could you please share details about a potential API endpoint where we might retrieve salary data?

    Your feedback is crucial in shaping the direction of our product, and we genuinely appreciate your contribution. We will keep you updated on any developments and prioritize this feature if we observe a growing demand from our user base.

    Thank you once again for your understanding and collaboration.

    Regards
    Sandeep Preetam
    Technical Product Owner

    Here is the API endpoint:
    https://documentation.bamboohr.com/reference/get-employee


    The description is as follows: This is suitable for getting basic employee information, including current values for fields that are part of a historical table, like job title, or compensation information

    In terms of the other data subprocessors, I can confirm that Merge.dev offers compensation information from BambooHR as part of their integration. 

    With Fivetran, I think our connector could pick up compensation info in the custom data fields. It's hard to know from the BambooHR APIs which are all the standard fields available and which are custom per each client. Perhaps Merge is abstracting away that complexity and just offering it as a "standard" endpoint in their own services, but on the BambooHR side it could not exist for certain customers depending on how their instance is configured? 

    Sandeep, example of what Chetan is saying about Merge.dev's BambooHR integration from below
    https://docs.merge.dev/integrations/hris/bamboohr/provider-interactions/