Skip to content
Notis

Catch spreadsheet issues as soon as a CSV lands in Drive

Get a quick data quality readout without opening a notebook or inspecting every column by hand.

Trigger

New File Matching Query

Triggers when a new Google Drive file matches a provided query. This is the legacy query-centric trigger: it preserves Drive API query config such as ``corpora`` / ``driveId`` aliases and emits the historical ``file_matching_query`` event type. ``FileCreatedTrigger`` covers the broader "new file" case and emits ``file_created``.

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

A new CSV can look fine at a glance while hiding missing values or duplicated records that skew later decisions.

  • Spot missing values and duplicate rows early
  • Get a concise report from a new matching CSV
  • Reduce manual spreadsheet inspection

Setup

Build it in a few focused steps.

  • 1Connect Google Drive and Codeinterpreter once in the Notis portal.
  • 2Create an automation and name it for your CSV quality check.
  • 3Describe the outcome in one instruction, including which columns or checks matter to you.
  • 4Pick New File Matching Query as the trigger and choose where run reports go.
  • 5Test with one real CSV that matches your query.

Questions about this workflow

What can the check report?

Ask Notis to run Python checks such as row counts, missing values, duplicate rows, and column summaries on the matching CSV.

Can it judge whether a value is unusual?

Yes, if you describe the expected ranges or rules in your instruction. Notis cannot infer business rules that you have not supplied.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Google Drive to Codeinterpreter. A trigger fires from one place; an action lands in another.

Google Drive triggers

Codeinterpreter actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

Comment Added (Docs/Sheets/Slides)

Triggers when a new comment is added to Google Docs, Sheets, or Slides.

TriggerPolling

Get File

Get a file from the sandbox and returns the file. the files should be read from /home/user folder.

ActionInstant

File Created

Triggers when a new file is created in Google Drive.

TriggerPolling

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.

ActionInstant

File Deleted or Trashed

Triggers when a file is moved to trash or permanently deleted in Drive.

TriggerPolling

Upload File

Upload a file to the sandbox environment. the files should be uploaded to the /home/user folder.

ActionInstant

File Shared (Permissions Added)

Triggers when new sharing permissions are granted to a file or folder. Uses Drive's `changes.list` endpoint with inline `permissions` in the `fields` mask so each change carries the file's current permission set provider-atomically. We diff that against `seen_permission_keys` to identify newly added grants. Drive page tokens are the primary cursor; if Drive rejects a stored token, the trigger raises `PollingTriggerError` without clearing state rather than silently re-baselining and dropping events. Limitation: truly ephemeral permissions (added and revoked between two polls without any other file modification in between) are not detected. Drive Activity API would catch those but requires an additional OAuth scope and a different payload contract.

TriggerPolling

File Updated

Triggers when a file's metadata or content changes in Google Drive.

TriggerPolling

Google Drive Changes

Triggers when changes are detected in a Google Drive.

TriggerPolling

Connect any two apps with Notis in the middle.

Google 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.