Bring a finished analysis artifact back for review
Make the result file available when you need to review or share the output of a Tripo3D analysis.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Get File
Get a file from the sandbox and returns the file. the files should be read from /home/user folder.
Why this helps
Useful charts and reports are easy to overlook when they remain buried in a sandbox after a run.
- Retrieves a named file from the sandbox for review.
- Makes the handoff from analysis to review explicit.
- Helps keep generated artifacts from being forgotten.
Setup
Build it in a few focused steps.
- 1Connect Tripo3D and Codeinterpreter to Notis once in the portal.
- 2Create an automation conversationally or from the portal.
- 3Write one instruction asking Notis to retrieve the named analysis result from /home/user when its webhook request arrives and report the returned file.
- 4Choose an incoming webhook trigger and a channel for run reports.
- 5Test after placing one real result file in the sandbox.
Questions about this workflow
Does this create the analysis file?
No. The file must already exist in the Codeinterpreter sandbox before the get-file action runs.
How does it know which file to retrieve?
Name the expected file in the prompt or include a reliable file name in the webhook request.
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.