Pause Bench after a Coda document is deleted
Create a measured handoff when a source document disappears.
Trigger
Coda Document Deleted Trigger
Triggers when a Coda document is deleted.
Action
Sleep
Sleep
Why this helps
Deletion events can race cleanup or dependency checks that still need to recognize the removed document.
- Makes deletion handoffs more predictable
- Provides time for dependent checks
- Reduces rushed manual cleanup
Setup
Build it in a few focused steps.
- 1Connect Coda and Bench once in the Notis portal.
- 2Create an automation telling Notis to pause after a Coda document is deleted.
- 3Pick Coda Document Deleted Trigger as the trigger.
- 4Choose a report channel and test with one real deletion event.
Questions about this workflow
What starts the pause?
A Coda document deletion starts it.
Does this delete anything in Bench?
No. The only available Bench action is Sleep, so this workflow only adds a pause.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Coda to Bench. A trigger fires from one place; an action lands in another.
Coda triggers
Bench actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Sleep
Sleep
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Coda Document Deleted Trigger
Triggers when a Coda document is deleted.
New Coda Document Trigger
Triggers when a new Coda document is created.
New Coda Page Trigger
Triggers when a new page is added to a Coda document.
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 Bench, 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 Bench.