Review deletion follow ups with a Python retention check
A deletion event can require more than cleanup. Run the same retention review every time.
Trigger
Coda Document Deleted Trigger
Triggers when a Coda document is deleted.
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
Deletion follow ups are easy to miss when rules live in someone's memory.
- Makes review rules repeatable
- Surfaces items needing attention
- Creates an auditable result
Setup
Build it in a few focused steps.
- 1Connect Coda and Codeinterpreter once in the Notis portal.
- 2Create an automation for deletion retention checks.
- 3Tell Notis to run your Python rules against the deletion context and report files or records needing review.
- 4Pick Coda Document Deleted as the trigger and choose the run report destination.
- 5Test with one controlled deletion example.
Questions about this workflow
Does the event provide a full archive inventory?
No. Supply the inventory or lookup data your retention rules need.
Can it make the retention decision for me?
It can apply the rules in your prompt and return findings for your review.
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.
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.
Coda Document Deleted Trigger
Triggers when a Coda document is deleted.
Get File
Get a file from the sandbox and returns the file. the files should be read from /home/user folder.
New Coda Document Trigger
Triggers when a new Coda document is created.
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.
New Coda Page Trigger
Triggers when a new page is added to a Coda document.
Upload File
Upload a file to the sandbox environment. the files should be uploaded to the /home/user folder.
Specific Coda Page Updated Trigger
Triggers when a specific page within a Coda document is updated.
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.