Connect bunq and Personio Personnel Data
Describe what you want to happen between bunq and Personio Personnel Data in plain words. HumDay writes the program, proves it on real data, and runs it — no node graph, no field mapping, and no connector to wait for.
What HumDay can do on each side
Read from each provider’s own published API description, in their words.
bunq
421 documented operations. See all bunq operations
- POSTCreate a new DeviceServer providing the installation token in the
/device-server - POSTCreate a new session for a DeviceServer
/session-server - POSTCreate a new public attachment
/attachment-public - POSTUsed to create a sandbox userPerson
/sandbox-user-person - POSTCreate a new debit card request
/user/{userID}/card-debit - POSTUsed to create a sandbox userCompany
/sandbox-user-company
Personio Personnel Data
13 documented operations. See all Personio Personnel Data operations
- POSTCreate an employee
/company/employees - POSTThis endpoint is responsible for adding absence data
/company/time-offs - POSTThis endpoint is responsible for adding attendance data
/company/attendances - DELETEThis endpoint is responsible for deleting absence period data
/company/time-offs/{id} - DELETEThis endpoint is responsible for deleting attendance data
/company/attendances/{id} - PATCHThis endpoint is responsible for updating attendance data
/company/attendances/{id}
How a bunq and Personio Personnel Data automation gets built
- Describe the outcome. Say what should happen — not which endpoints to call. HumDay works out which operations each side needs.
- Approve the contract. Before anything is built you see exactly what it will do in bunq and Personio Personnel Data, and what it will never do.
- See it proven. The program runs and shows you the result before it is allowed near either live account.
- Grant access, then go live. You approve the specific operations it may use on each side — and only those.
Related integrations
- bunq and OData for namespace microsoft.graphintegration
- OData for namespace microsoft.graph and Personio Personnel Dataintegration
- bunq and Cloudflareintegration
- Cloudflare and Personio Personnel Dataintegration
- bunq and NetBoxintegration
- NetBox and Personio Personnel Dataintegration
- bunq and GitHubintegration
- GitHub and Personio Personnel Dataintegration
- bunq and Mistintegration
- Mist and Personio Personnel Dataintegration
Questions about connecting bunq and Personio Personnel Data
- Can bunq connect with Personio Personnel Data?
- Yes. HumDay reads both providers' own published API descriptions and derives what each one can do, so neither side needs a hand-built connector before you can use it.
- How do I connect bunq to Personio Personnel Data?
- Describe the outcome you want in plain words. HumDay agrees a contract with you saying exactly what it will do, writes the program, and shows you a proof run before either account is touched.
- Do I need to write code to integrate bunq and Personio Personnel Data?
- No. There is no node graph to wire up and no field mapping to do. You say what should happen and HumDay works out which operations it needs from each side.
- What can HumDay do across bunq and Personio Personnel Data?
- bunq publishes 421 documented operations and Personio Personnel Data publishes 13. HumDay only ever uses the specific ones your approved contract needs.
- Is it safe to connect both accounts?
- Your credentials are stored encrypted and never appear in chat, code, or logs. Anything that writes to either bunq or Personio Personnel Data is held behind an approval you grant explicitly.
Where this came from
Operations are read from the published API descriptions for bunq and Personio Personnel Data. Descriptions are each provider’s own words, not ours.