Skip to content
Notis

Put the source file beside every new Coda document run

Start analysis with the file your workflow depends on already available in the sandbox.

Trigger

New Coda Document Trigger

Triggers when a new Coda document is created.

Action

Upload File

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

Why this helps

Analysis pauses when source files must be uploaded manually for each new document.

  • Prepares files before analysis
  • Cuts repeated uploads
  • Makes runs more consistent

Setup

Build it in a few focused steps.

  • 1Connect Coda and Codeinterpreter once in the Notis portal.
  • 2Create an automation for new document file preparation.
  • 3Tell Notis which user supplied file to upload and where it should be placed in /home/user.
  • 4Pick New Coda Document as the trigger and choose a report channel.
  • 5Test with one document and the intended source file.

Questions about this workflow

Where does the uploaded file go?

Uploads are placed in the Codeinterpreter /home/user folder.

Can the event provide a file automatically?

Only when the source context includes a usable file reference. Otherwise name the file in your prompt.

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.