kombo.dev Kombo Changelog logo

Kombo Changelog

Back to Kombo Subscribe to Updates

Labels

  • All Posts
  • General
  • ATS
  • HRIS
  • Assessment
  • SFTP
  • DATEV

Jump to Month

  • May 2025
  • March 2025
  • February 2025
  • January 2025
  • December 2024
  • November 2024
  • October 2024
  • September 2024
  • August 2024
  • July 2024
  • June 2024
  • May 2024
  • April 2024
  • March 2024
  • February 2024
  • January 2024
  • December 2023
  • November 2023
  • August 2023
  • July 2023
  • June 2023
  • May 2023
  • March 2023
  • February 2023
  • January 2023
GeneralHRIS
a year ago

Mapping of any employee field, supported tools overview and partner credentials

HRIS 

  • Mapping of employee standard fields- Even when mapping all the user-defined custom fields there might be data that's not part of the Kombo standard data model but still very valuable to you.
    • That's why now you can also map the standard fields that are exposed by a specific tools to Kombo custom fields
    • You can also still use the alias-feature. Meaning that you can configure something like "map any field called 'passport' to this data point" regardless of whether it's a user-defined custom field or just a standard field. Happy mapping!

General 

  • ✔︎ Supported tools per endpoint- In addition to seeing the list of supported model for each tool ("get tools" endpoint) you can now also see all tools that support a specific endpoint.
    • Just go on the documentation page of a specific endpoint (i.e. "create application") and then click on the "Supported integrations" dropdown to see the tools that support this
  • 🤝 Partner credentials- If you have a partnership with an ATS or HRIS and want your branding, name and scopes to be used instead of those of Kombo you can share your partner credentials with us to do exactly that
    • This feature is still in private beta so reach out to us if you're interested!
  • ⚙️ Exposed scope config template for linked account- You can now see which scope config template is used for a specific connected account via the "get integration details" endpoint so that you are able to use a different mapper based on the scopes you will receive. Happy mapping!
Avatar of authorMarvin, Product Lead