Get a weekly Tripo3D usage snapshot
Make usage review a predictable small task, with totals and changes gathered into one report.
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
Usage review often gets delayed because there is no natural point in the week to open the records and calculate trends.
- Creates a regular moment to review usage.
- Can compare periods when dated records are available.
- Keeps a recurring check from depending on memory.
Setup
Build it in a few focused steps.
- 1Connect Tripo3D and Codeinterpreter to Notis once in the portal.
- 2Create an automation in the portal or ask Notis in plain language.
- 3In one instruction, ask Codeinterpreter to summarize recent Tripo3D usage records available to the automation and compare with the prior period when possible.
- 4Choose a weekly schedule and a channel for run reports.
- 5Test with one real usage sample before relying on the recurring report.
Questions about this workflow
Will a schedule retrieve usage data automatically?
The scheduled run can analyze data available to the automation. Arrange for your connected setup or backend to make current records available.
Can it make a chart?
Yes, the prompt can request a plot saved as a file, which Codeinterpreter can return through a file action.
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.