Create a Retention Notice from a Deleted Coda Document
A deletion event can trigger the communication needed to close the loop.
Trigger
Coda Document Deleted Trigger
Triggers when a Coda document is deleted.
Action
Create Transactional Campaign
This tool creates a new transactional campaign within a specified brand in bigmailer. it allows users to programmatically create new transactional campaigns by using the provided parameters (brandid, name, subject, fromname, fromemail, htmlcontent, etc.). the api endpoint returns details such as campaignid, name, status, and created at when a campaign is successfully created.
Why this helps
Document removal can leave customers or collaborators without context about what changed.
- Turns a destructive event into a controlled communication step
- Makes archive or replacement messaging repeatable
- Helps teams close loops after cleanup
Setup
Build it in a few focused steps.
- 1Connect Coda and Bigmailer once in the Notis portal.
- 2Create an automation describing the notice and audience in one instruction.
- 3Choose the Coda Document Deleted trigger.
- 4Select a report channel and test with one real deletion event.
Questions about this workflow
What information is available after deletion?
The event may provide limited document details. Put any required replacement link or explanation in your instruction or retained Coda context.
Can this notify every deletion?
Yes, if the trigger is configured for the documents you want monitored and the campaign outcome is appropriate.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Coda to Bigmailer. A trigger fires from one place; an action lands in another.
Coda triggers
Bigmailer actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Transactional Campaign
This tool creates a new transactional campaign within a specified brand in bigmailer. it allows users to programmatically create new transactional campaigns by using the provided parameters (brandid, name, subject, fromname, fromemail, htmlcontent, etc.). the api endpoint returns details such as campaignid, name, status, and created at when a campaign is successfully created.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get User Information
This tool retrieves information about the authenticated user in bigmailer using the get /me endpoint. it requires only authentication and no additional parameters, making it ideal for verifying api connectivity and retrieving essential user details.
Coda Document Deleted Trigger
Triggers when a Coda document is deleted.
List All Brands
This tool retrieves a list of all brands associated with the authenticated bigmailer account. it allows users to view and manage their brands. the operation is executed via a simple get request to the /brands endpoint and requires proper authentication using the x-api-key header. the response is a json array containing information such as brand id, brand name, and other related details.
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 Bigmailer, 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 Bigmailer.