Connect Personio Personnel Data and Spinitron
Describe what you want to happen between Personio Personnel Data and Spinitron 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.
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}
Spinitron
9 documented operations. See all Spinitron operations
- GETReturns scheduled shows optionally filtered by {start} and/or {end}
/shows - GETReturns spins optionally filtered by {start} and/or {end} datetimes
/spins - GETGet Personas
/personas - GETReturns playlists optionally filtered by {start} and/or {end}
/playlists - GETGet a Show by id
/shows/{id} - GETGet a Spin by id
/spins/{id}
How a Personio Personnel Data and Spinitron 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 Personio Personnel Data and Spinitron, 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
- OData for namespace microsoft.graph and Personio Personnel Data11,425 operations
- OData for namespace microsoft.graph and Spinitron11,421 operations
- Cloudflare and Personio Personnel Data3,135 operations
- Cloudflare and Spinitron3,131 operations
- NetBox and Personio Personnel Data857 operations
- NetBox and Spinitron853 operations
- GitHub and Personio Personnel Data824 operations
- GitHub and Spinitron820 operations
- Mist and Personio Personnel Data781 operations
- Mist and Spinitron777 operations
Questions about connecting Personio Personnel Data and Spinitron
- Can Personio Personnel Data connect with Spinitron?
- 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 Personio Personnel Data to Spinitron?
- 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 Personio Personnel Data and Spinitron?
- 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 Personio Personnel Data and Spinitron?
- Personio Personnel Data publishes 13 documented operations and Spinitron publishes 9. 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 Personio Personnel Data or Spinitron is held behind an approval you grant explicitly.
Where this came from
Operations are read from the published API descriptions for Personio Personnel Data and Spinitron. Descriptions are each provider’s own words, not ours.