Can HumDay connect to Ably Control?

Yes. HumDay reads Ably Control's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 22 operations are documented.

Do I need to write code to automate Ably Control?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Ably Control account.

What can HumDay do in Ably Control?

15 of the 22 documented operations change something in Ably Control, and 7 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Ably Control account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Ably Control is held behind that approval.

Automate Ably Control

HumDay reads Ably Control’s own published API description and derives 22 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

What Ably Control is

Use the Control API to manage your applications, namespaces, keys, queues, rules, and more. Detailed information on using this API can be found in the Ably developer documentation . Control API is currently in Beta.

API host: control.ably.net

What HumDay can do in Ably Control

15 documented operations change something in Ably Control.

POSTUpdates app's APNs info from a.p12 file/apps/{id}/pkcs12
POSTCreates a key/apps/{app_id}/keys
POSTCreates a Reactor rule/apps/{app_id}/rules
POSTCreates a queue/apps/{app_id}/queues
POSTCreates a namespace/apps/{app_id}/namespaces
POSTCreates an app/accounts/{account_id}/apps
DELETEDeletes an app/apps/{id}
PATCHUpdates an app/apps/{id}
PATCHUpdates a key/apps/{app_id}/keys/{key_id}
DELETEDeletes a Reactor rule/apps/{app_id}/rules/{rule_id}
PATCHUpdates a Reactor rule/apps/{app_id}/rules/{rule_id}
DELETEDeletes a queue/apps/{app_id}/queues/{queue_id}
DELETEDeletes a namespace/apps/{app_id}/namespaces/{namespace_id}
PATCHUpdates a namespace/apps/{app_id}/namespaces/{namespace_id}
POSTRevokes a key/apps/{app_id}/keys/{key_id}/revoke

What HumDay can read from Ably Control

These are the operations a schedule or a trigger can watch.

GETGet token details/me
GETLists app keys/apps/{app_id}/keys
GETLists Reactor rules/apps/{app_id}/rules
GETLists queues/apps/{app_id}/queues
GETLists namespaces/apps/{app_id}/namespaces
GETLists apps/accounts/{account_id}/apps
GETGets a reactor rule by rule ID/apps/{app_id}/rules/{rule_id}

How automating Ably Control works

Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
See it proven. The program runs and shows you the result before it is allowed near your live Ably Control account.
Grant access, then go live. You approve the specific Ably Control operations it may use — and only those.

Popular Ably Control integrations

Connect Ably Control to the tools people pair it with most.