Connect Slack and Spinitron
Describe what you want to happen between Slack 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.
Slack
174 documented operations. See all Slack operations
- POSTUploads or creates a file
/files.upload - POSTSends an ephemeral message to a user in a channel
/chat.postEphemeral - POSTAdds a file from a remote service
/files.remote.add - POSTDeletes an existing comment on a file
/files.comments.delete - POSTPins an item to a channel
/pins.add - POSTAdds a star to an item
/stars.add
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 Slack 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 Slack 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 Slackintegration
- OData for namespace microsoft.graph and Spinitronintegration
- Cloudflare and Slackintegration
- Cloudflare and Spinitronintegration
- NetBox and Slackintegration
- NetBox and Spinitronintegration
- GitHub and Slackintegration
- GitHub and Spinitronintegration
- Mist and Slackintegration
- Mist and Spinitronintegration
Questions about connecting Slack and Spinitron
- Can Slack 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 Slack 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 Slack 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 Slack and Spinitron?
- Slack publishes 174 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 Slack or Spinitron is held behind an approval you grant explicitly.
Where this came from
Operations are read from the published API descriptions for Slack and Spinitron. Descriptions are each provider’s own words, not ours.