Keep Ably analysis files organized with a scheduled cleanup
Run a defined retention utility on a schedule so old analysis artifacts do not accumulate unnoticed.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
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.
Why this helps
Old analysis files build up when cleanup depends on someone remembering the retention rule and the command.
- Run an existing cleanup command consistently.
- Make the retention rule explicit in the automation.
- Capture command output and errors in the run report.
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 existing cleanup utility, target files, and retention rule.
- 4Choose notis_cron as the trigger and select where run reports should go.
- 5Test with one real example and check which files the utility affects.
Questions about this workflow
Does this delete Ably channel data?
This example concerns analysis files in the sandbox. Specify the exact files and behavior for the existing utility you intend to run.
Is the retention period built in?
No. Provide the retention rule and use an existing command or script that applies it.
Can I see what the command did?
The action returns stdout, stderr, and an error code. Have the utility report the files it considers or removes.
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.