Route incoming files to a Python workspace
Give external systems one simple webhook and let Notis place each incoming file in Codeinterpreter.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Upload File
Upload a file to the sandbox environment. the files should be uploaded to the /home/user folder.
Why this helps
Files arriving from forms or services often require a manual handoff before analysis can begin.
- Creates a single intake path
- Removes manual transfers
- Starts processing faster
Setup
Build it in a few focused steps.
- 1Connect Codeinterpreter in Notis.
- 2Create an automation named Webhook file intake.
- 3Describe the outcome: upload the incoming webhook file to /home/user and report the saved filename.
- 4Choose a Notis webhook trigger and copy its endpoint into the sending system.
- 5Choose a report channel and test with one real file.
Questions about this workflow
What must the webhook send?
It should include the file or a supported file reference and any context needed to name it safely.
Can it accept multiple files?
Yes, if the sending system and your instruction define how each file should be handled.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link One drive to Codeinterpreter. A trigger fires from one place; an action lands in another.
One drive 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.
Onedrivebasetrigger
Base trigger for OneDrive changes using Gmail-style state management. Subclasses override `filter_changes(...)` to extract only the relevant items.
Get File
Get a file from the sandbox and returns the file. the files should be read from /home/user folder.
OneDrive File Created Trigger
Triggers when a new file is created in OneDrive. Uses Gmail-style state management for reliable duplicate prevention.
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.
File Updated
Trigger that fires when a OneDrive file's content or metadata changes. Returns file ID, last modified time, and modifier info.
Upload File
Upload a file to the sandbox environment. the files should be uploaded to the /home/user folder.
OneDrive Folder Created Trigger
Triggers when a new folder is created in OneDrive. Uses Gmail-style state management for reliable duplicate prevention.
OneDrive Item Deleted Trigger
Triggers when a file or folder is deleted in OneDrive. Uses Gmail-style state management for reliable duplicate prevention.
Item Moved or Renamed
Triggers when a file or folder is moved to a different path or renamed in OneDrive. Includes both old and new path/name data in the payload.
Connect any two apps with Notis in the middle.
One drive 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.