Connect Bluemix IBM Containers and SlideRoom
Describe what you want to happen between Bluemix IBM Containers and SlideRoom 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.
Bluemix IBM Containers
47 documented operations. See all Bluemix IBM Containers operations
- POSTCreate a file share in a space
/volumes/fs/create - DELETEDelete a file share
/volumes/fs/{name} - POSTCreate a volume in a space
/volumes/create - POSTCreate and start a single container
/containers/create - POSTCreate and start a container group
/containers/groups - POSTShare a volume with another space
/volumes/{name}
SlideRoom
11 documented operations. See all SlideRoom operations
- POSTRequests the generation of application export files
/api/v2/application/request-export - POSTRequests the generation of a single application export file
/api/v2/application/{applicationId}/request-export - DELETEDeletes a custom attribute for an applicant
/api/v2/applicant/attributes - POSTUpdates the custom attributes for an applicant
/api/v2/applicant/attributes - DELETEDeletes a custom attribute for an application
/api/v2/application/{applicationId}/attributes - POSTUpdates the custom attributes for an application
/api/v2/application/{applicationId}/attributes
How a Bluemix IBM Containers and SlideRoom 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 Bluemix IBM Containers and SlideRoom, 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
- Bluemix IBM Containers and OData for namespace microsoft.graphintegration
- OData for namespace microsoft.graph and SlideRoomintegration
- Bluemix IBM Containers and Cloudflareintegration
- Cloudflare and SlideRoomintegration
- Bluemix IBM Containers and NetBoxintegration
- NetBox and SlideRoomintegration
- Bluemix IBM Containers and GitHubintegration
- GitHub and SlideRoomintegration
- Bluemix IBM Containers and Mistintegration
- Mist and SlideRoomintegration
Questions about connecting Bluemix IBM Containers and SlideRoom
- Can Bluemix IBM Containers connect with SlideRoom?
- 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 Bluemix IBM Containers to SlideRoom?
- 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 Bluemix IBM Containers and SlideRoom?
- 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 Bluemix IBM Containers and SlideRoom?
- Bluemix IBM Containers publishes 47 documented operations and SlideRoom publishes 11. 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 Bluemix IBM Containers or SlideRoom is held behind an approval you grant explicitly.
Where this came from
Operations are read from the published API descriptions for Bluemix IBM Containers and SlideRoom. Descriptions are each provider’s own words, not ours.