Skip to content
Notis

Process new Coda documents with one batch command

Make intake predictable by running the same command whenever a document arrives.

Trigger

New Coda Document Trigger

Triggers when a new Coda document is created.

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

Manual intake steps vary by person and leave work half processed.

  • Standardizes intake
  • Reduces repeated terminal work
  • Leaves a clear command result

Setup

Build it in a few focused steps.

  • 1Connect Coda and Codeinterpreter once in the Notis portal.
  • 2Create an automation for new document batch processing.
  • 3Tell Notis the terminal command to run in /home/user and what document context it should use.
  • 4Pick New Coda Document as the trigger and choose where reports should go.
  • 5Test with one representative document.

Questions about this workflow

What kind of command can I run?

Any command supported by the Codeinterpreter terminal environment and your supplied files.

Can it process multiple new documents?

Each matching document event starts its own run.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Coda 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

Coda Document Deleted Trigger

Triggers when a Coda document is deleted.

TriggerPolling

Get File

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

ActionInstant

New Coda Document Trigger

Triggers when a new Coda document is created.

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

New Coda Page Trigger

Triggers when a new page is added to a Coda document.

TriggerPolling

Upload File

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

ActionInstant

Specific Coda Page Updated Trigger

Triggers when a specific page within a Coda document is updated.

TriggerPolling

Connect any two apps with Notis in the middle.

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