Make failed task details easier to act on
Get the relevant failure context into one short note, ready for your next troubleshooting step.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
When a task fails, reconstructing what happened from scattered details can stall a project.
- Collects supplied error text and task identifiers into a readable report.
- Includes timestamps when they are present in the payload.
- Makes a failure easier to revisit without reassembling its context.
Setup
Build it in a few focused steps.
- 1Connect Tripo3D and Codeinterpreter to Notis once in the portal.
- 2Create the automation in the portal or tell Notis what it should do conversationally.
- 3Use one instruction asking Codeinterpreter to organize error details and task identifiers from each incoming webhook record into a concise troubleshooting note.
- 4Choose an incoming webhook trigger and a channel for run reports.
- 5Test with one failed task record that includes an error detail.
Questions about this workflow
Will this retry a failed task?
No. This workflow summarizes the failure details supplied to the webhook.
Can it suggest what to check?
Ask the prompt to offer cautious next checks based only on the error information provided.
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.