Keep an eye on generated output sizes
See where larger outputs are accumulating with a lightweight recurring size review.
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
Large files can consume attention later when nobody has noticed the trend or identified the biggest items.
- Totals supplied output sizes for a period or available set.
- Highlights the largest records for a closer look.
- Makes size review a repeatable part of your routine.
Setup
Build it in a few focused steps.
- 1Connect Tripo3D and Codeinterpreter to Notis once in the portal.
- 2Create the automation by asking Notis or using the portal's New Automation flow.
- 3In one instruction, ask Codeinterpreter to total available output sizes and list the largest items using the records supplied to the automation.
- 4Choose a recurring schedule and a channel for run reports.
- 5Test with records that include file sizes before setting the ongoing cadence.
Questions about this workflow
Does it measure remote storage directly?
It summarizes sizes in records available to the automation; it does not independently inspect an account unless your setup supplies that data.
Can it focus on new outputs?
Yes, if the available records include dates and your prompt specifies the period to summarize.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Tripo3D to Codeinterpreter. A trigger fires from one place; an action lands in another.
Tripo3D 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.
Tripo3D 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.