See mesh trends without rebuilding the chart
Turn recurring mesh measurements into a chart that is ready when you sit down to review them.
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
Repeatedly collecting values and rebuilding the same chart creates friction that makes trend review easy to defer.
- Plots a metric from dated records available to the run.
- Saves the chart as an output file rather than opening a remote window.
- Creates a repeatable visual review across periods.
Setup
Build it in a few focused steps.
- 1Connect Tripo3D and Codeinterpreter to Notis once in the portal.
- 2Create the automation in Automations or ask Notis in plain language.
- 3In one instruction, name the mesh metric to chart from available dated records and ask Codeinterpreter to save the plot as a file without using plt.show().
- 4Choose a monthly schedule and a channel for run reports.
- 5Test with a small real dataset and review the saved chart.
Questions about this workflow
Will it automatically collect historical metrics?
It charts records available to the automation. Arrange for dated records to be supplied to the scheduled run.
Where does the chart go?
Codeinterpreter can save the plot as a file in its sandbox for retrieval or review.
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.