Keep weekly analysis files in a predictable place
Give each week's review a consistent starting point, with the report folder created for you.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
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.
Why this helps
Repeatedly deciding where to put analysis files adds small setup work and makes later retrieval harder.
- Creates a known folder structure on schedule.
- Makes weekly outputs easier to organize consistently.
- Saves a few setup decisions each review cycle.
Setup
Build it in a few focused steps.
- 1Connect Tripo3D and Codeinterpreter to Notis once in the portal.
- 2Create an automation through Automations or ask Notis in plain language.
- 3Write one instruction asking Codeinterpreter to run a safe terminal command that creates a dated weekly report folder under /home/user.
- 4Choose a weekly schedule and where Notis should report runs.
- 5Test once and confirm the folder path is suitable for your workflow.
Questions about this workflow
Does it create report contents too?
This workflow creates the folder. A separate instruction can generate reports when the relevant records are available.
Where is the folder created?
The prompt specifies the Codeinterpreter sandbox path under /home/user.
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.