Add ownership context after a Coda document deletion
When a document disappears, capture who is running the Affinity-connected workflow.
Trigger
Coda Document Deleted Trigger
Triggers when a Coda document is deleted.
Action
Get current user
Returns metadata about the current user.
Why this helps
Deletion events can be hard to interpret without a clear operator or owner.
- Clarify event ownership
- Improve operational traceability
- Create consistent deletion reports
Setup
Build it in a few focused steps.
- 1Connect Coda and Affinity once.
- 2Create an automation for deletion audit reports.
- 3Tell Notis to retrieve the current Affinity user and include the deleted document context.
- 4Choose Coda Document Deleted as the trigger.
- 5Select a report channel and test with a controlled example.
Questions about this workflow
Does this restore the document?
No. It only retrieves the current Affinity user for reporting context.
Who receives the report?
You choose the report channel during automation setup.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Coda to Affinity. A trigger fires from one place; an action lands in another.
Coda triggers
Affinity actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get a company s list entries
Summarize company data across all lists, including list-specific fields and metadata like creation date and author. access requires "export data from lists" permission.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get a company s lists
Returns metadata for all the lists on which the given company appears.
Coda Document Deleted Trigger
Triggers when a Coda document is deleted.
Get all companies
Affinity api allows paginated access to company info and custom fields. use `fieldids` or `fieldtypes` to specify data in a request. retrieve field ids/types via get `/v2/companies/fields`. export permission needed.
New Coda Document Trigger
Triggers when a new Coda document is created.
Get all list entries on a list
Access and export essential data and metadata for companies, persons, or opportunities from a list, specifying data via `fieldids` or `fieldtypes`. "export data from lists" permission is necessary.
New Coda Page Trigger
Triggers when a new page is added to a Coda document.
Get all list entries on a saved view
Use the endpoint to access rows in a saved view with specific filters and selected fields from a web app. it doesn't maintain sort order, supports only sheet-type views, and requires export permissions.
Specific Coda Page Updated Trigger
Triggers when a specific page within a Coda document is updated.
Get all opportunities
Pagination through opportunities in affinity yields basic info but excludes field data. for field data, use specified get endpoints. "export data from lists" permission needed.
Get all persons
The affinity api offers paginated access to person data using `fieldids` or `fieldtypes`. bulk extraction needs special permissions and supports multiple parameters.
Get a person s list entries
Summary: browse rows for a person in all lists, showing field data and entry metadata like creation time and author. requires "export data from lists" permission.
Connect any two apps with Notis in the middle.
Coda and Affinity, 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 Affinity.