Stop browser sessions when their Coda document is gone
Document deletion can close the loop on browser work that no longer has a purpose.
Trigger
Coda Document Deleted Trigger
Triggers when a Coda document is deleted.
Action
Update Browser Session
Tool to update the status of a specific browser session. use when you need to request session completion before timeout to avoid additional charges.
Why this helps
Orphaned sessions keep running after a project disappears, creating extra review and potential usage costs.
- Stop unnecessary sessions
- Reduce timeout exposure
- Keep workspace state cleaner
Setup
Build it in a few focused steps.
- 1Connect Coda and Browserbase tool once in Notis.
- 2Create an automation for deleted document session completion.
- 3Tell Notis to request completion for the Browserbase session linked to the deleted Coda document and report the outcome.
- 4Pick the Coda Document Deleted trigger and choose a report destination.
- 5Test with one disposable document and session.
Questions about this workflow
Does this force immediate deletion?
It requests session completion before timeout; the resulting status should be reported.
What if there is no linked session?
The workflow should report that no reliable session id was found.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Coda to Browserbase tool. A trigger fires from one place; an action lands in another.
Coda triggers
Browserbase tool actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create a new browser context
Tool to create a new browser context. use when you need to obtain upload credentials for a custom user-data-directory in a project.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Retrieve a browser context
Tool to retrieve details of a specific browser context. use when you have a context id and need its metadata.
Coda Document Deleted Trigger
Triggers when a Coda document is deleted.
Update Browser Context
Tool to update a specific browser context. use when you need fresh upload url and encryption details for an existing context, after obtaining a valid context id.
New Coda Document Trigger
Triggers when a new Coda document is created.
Create Browser Session
Tool to create a new browser session. use when you need an isolated browser context before performing any page interactions.
New Coda Page Trigger
Triggers when a new page is added to a Coda document.
Retrieve a browser session
Tool to retrieve details of a specific browser session. use when you have a session id and need its metadata (status, urls, timestamps).
Specific Coda Page Updated Trigger
Triggers when a specific page within a Coda document is updated.
Retrieve Session Debug URLs
Tool to retrieve live debug urls for a specific session. use when you need to connect to a running session for debugging.
Download Session Artifacts
Tool to download files from a specific session. use after session completion to retrieve all generated artifacts in a zip archive.
Retrieve Session Logs
Tool to retrieve logs of a specific session. use after actions in a session to inspect network events and data exchange.
Connect any two apps with Notis in the middle.
Coda and Browserbase tool, 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 Browserbase tool.