Chart Ably event volume on a schedule
Make channel activity easier to review with a chart saved automatically on your chosen cadence.
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
Counting activity by hand makes it difficult to notice changes across a recurring reporting period.
- Generate a saved chart from accessible event data.
- Set the reporting period in the instruction.
- Avoid manually plotting recurring counts.
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 event data source, period, aggregation, and chart file to save.
- 4Choose notis_cron as the trigger and select where run reports should go.
- 5Test with one real period of data and confirm the chart file.
Questions about this workflow
Does Ably provide event counts automatically?
The workflow needs accessible event data or counts. Specify where they come from and which period to analyze.
Can it show week over week changes?
Yes, if the current and prior period data are available and the comparison is described in the instruction.
How is the image returned?
The code should save the chart as a file rather than calling plt.show(). Retrieve it from the sandbox when needed.
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.