Find Ably channels with no recent activity
Get a weekly list of quiet channels based on the activity data you make available.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Execute Code
Execute python code in a sandbox and return any result, stdout, stderr, and error. use /home/user folder to write/read files. try to not use plt.show() as the code is executed remotely. use files for image/chart output instead.
Why this helps
Quiet channels can go unnoticed when activity is spread across many places and nobody owns a regular check.
- Identify channels with no activity in a defined window.
- Make a recurring review visible in a report channel.
- Use supplied activity data instead of checking each channel manually.
Setup
Build it in a few focused steps.
- 1Connect Ably and Codeinterpreter once in the Notis portal.
- 2Create an automation in the portal or tell Notis in plain language from any channel.
- 3Describe the channel activity source, lookback period, and definition of inactive.
- 4Choose notis_cron as the trigger and select where run reports should go.
- 5Test with one representative activity dataset.
Questions about this workflow
Does Ably provide a list of inactive channels?
The workflow needs accessible activity data and a list of channels to evaluate. Specify those sources.
How is inactive defined?
Set the lookback period and any activity threshold in your instruction.
Can it recommend which channels to remove?
It can list channels matching your criteria. A removal decision requires your own context and judgment.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Ably to Codeinterpreter. A trigger fires from one place; an action lands in another.
Ably triggers
Codeinterpreter actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Sandbox
Create a sandbox to execute python code in a jupyter notebook cell. this is useful for agents to communicate, execute code, see output, read files, write files, etc. it's like you own personal computer, but in the cloud. use /home/user folder to write/read files.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Execute Code
Execute python code in a sandbox and return any result, stdout, stderr, and error. use /home/user folder to write/read files. try to not use plt.show() as the code is executed remotely. use files for image/chart output instead.
Get File
Get a file from the sandbox and returns the file. the files should be read from /home/user folder.
Run Terminal Command
Run a command in the terminal and returns the stdout, stderr, and error code. use /home/user folder to write/read files.
Upload File
Upload a file to the sandbox environment. the files should be uploaded to the /home/user folder.
Connect any two apps with Notis in the middle.
Ably and Codeinterpreter, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Codeinterpreter.