Lists queues in Ably Control
A documented Ably Control operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
Lists queues
- GETReads data · queues
control.ably.net/apps/{app_id}/queues
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Ably Control operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Other Ably Control operations
- Updates app's APNs info from a.p12 filePOST · changes data
- Creates a keyPOST · changes data
- Creates a Reactor rulePOST · changes data
- Creates a queuePOST · changes data
- Creates a namespacePOST · changes data
- Creates an appPOST · changes data
- Deletes an appDELETE · changes data
- Updates an appPATCH · changes data
Questions
- Can HumDay lists queues in Ably Control?
- Yes. This operation is published in Ably Control's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Does this change anything in my Ably Control account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Ably Control.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Ably Control account.
Where this came from
Read from a published API description for Ably Control at raw.githubusercontent.com/ably/open-specs/main/definitions/control-v1.yaml. The description above is the provider’s own wording, not ours. Last published 2021-07-26.