Create an analysis space for new Drive files
Give every new file a clear next step.
Trigger
File Created
Triggers when a new file is created in Google Drive.
Action
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.
Why this helps
New files arrive without a consistent place for inspection or analysis.
- Starts analysis consistently
- Creates a dedicated working context
- Reduces setup friction
Setup
Build it in a few focused steps.
- 1Connect Google Super and Codeinterpreter in Notis.
- 2Create an automation named New Drive file analysis space.
- 3Tell Notis to create a sandbox and prepare an analysis checklist from the file metadata.
- 4Pick File Created as the trigger and choose a report channel.
- 5Test it with one real Drive file.
Questions about this workflow
Can the sandbox read the file contents?
Only when the file content is available to the workflow or uploaded during a later step.
Can I customize the checklist?
Yes, describe the checks in the automation instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Super to Codeinterpreter. A trigger fires from one place; an action lands in another.
Google Super 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.
Aggregate Metric Changed
Triggers when an aggregate metric (SUM/COUNT/AVG/MIN/MAX) changes in a Google Sheets spreadsheet. This trigger monitors an aggregate calculation on a target column (optionally filtered by a search column/value) and fires when the calculated result changes.
Get File
Get a file from the sandbox and returns the file. the files should be read from /home/user folder.
Attendee Response Changed
Polling trigger that fires when any attendee's RSVP changes to accepted, declined, or tentative. Returns attendee info and current status.
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.
Cell Range Values Changed
Triggers when values in a specified A1 range change in Google Sheets. This trigger monitors a specific cell or range of cells and fires when any values change.
Upload File
Upload a file to the sandbox environment. the files should be uploaded to the /home/user folder.
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
Conditional Format Rule Changed
Triggers when conditional formatting rules change in a Google Spreadsheet. Detects when rules are added, updated, or removed. Uses snapshot-based diffing to detect changes between polls.
Data Validation Rule Changed
Triggers when data validation rules change (added/updated/removed) in a Google Spreadsheet. Uses snapshot-based diffing to detect changes between polls.
Connect any two apps with Notis in the middle.
Google Super 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.