Huma HR - Twine Integrations

2026-08-21

Multi-choice custom fields can now be translated from Huma’s internal option ids to their labels, through a Custom field options metadata source in a mapping node.
Two caveats added to the integration notes: a Huma account staying active does not mean the employment is ongoing, and a terminated employee’s employment details are only available through their positions.
Your Huma custom fields can now be mapped by name. Twine reads the custom fields defined in your Huma organisation and lists each one in the property mapper, with its section and type. A field added in Huma shows up within a few minutes, or immediately via the refresh button on the integration’s new Metadata tab.
Salaries sync once the Huma integration user has permission to read them. Nothing in Twine had to change for this; the permission was the whole story.
Huma has no documents or competences API, so neither can be synced regardless of the permissions granted in Huma.

Many more Huma fields can now be mapped. On the employee: first contract start date, seniority (in company and total), children, emergency contacts, connected integrations, interests, subordinate count, account type, job title id, avatar, deactivation timestamp, and the current positions Huma reports inline. Bank accounts now carry IBAN and BIC as well as the national account number, and addresses carry their third line. None of these are mapped by default — pick the ones you need in the property mapper.
Position mappings can now reach the fields Huma only exposes per position: first and last day of work, probation end, termination notice date, and the end reason. Twine fetches each position individually only when one of those fields is mapped.
Organisational unit descriptions now sync. Huma’s unit listing carries no description, so Twine now reads each unit individually — which means a description edited in Huma is picked up on an ordinary sync, and one removed in Huma is now cleared in Twine rather than left behind.
Huma’s work schedule and seniority endpoints are not available to an integration user, so absences still cover every calendar day in their range.

Employees sync through Huma’s API, so a full re-sync can be triggered on demand or on a schedule. Webhooks are now a trigger rather than the only source of data. Absences remain webhook-only.