Check image dimensions against your requirements
Spot size mismatches before an image becomes the next person's problem to fix.
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
Remembering to inspect every image size adds a small but easy-to-miss review task.
- Compares supplied dimensions to the size requirement in your prompt.
- Lists which image records pass or need a closer look.
- Creates a consistent check for repeated image deliveries.
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 tell Notis what to make in plain language.
- 3In one prompt, ask Codeinterpreter to compare dimensions in each webhook payload with the image sizes you require and report mismatches.
- 4Choose an incoming webhook trigger and a run-report channel.
- 5Test with one real image record, including a passing and a mismatched size if available.
Questions about this workflow
Does the workflow download and inspect images?
This version checks dimensions included in the webhook payload. Image inspection requires accessible files and an instruction that specifies how to read them.
Where do the expected dimensions go?
State them in the automation's plain-language instruction; there is no separate field-mapping screen.
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.