Keep your Coda issue tracker free of stale rows
When a Jira issue changes, let Notis check your stated cleanup rule and remove matching rows from the relevant Coda table.
Trigger
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Action
Delete multiple rows
Deletes the specified rows from the table or view. this endpoint will always return a 202. row deletions are generally processed within several seconds.
Why this helps
Old tracking rows can linger after issue changes and make it harder to spot current work.
- Reduce clutter in a Coda tracker when defined conditions are met.
- Avoid repeatedly checking for obsolete records by hand.
- Keep the cleanup rule explicit in the automation prompt.
Setup
Build it in a few focused steps.
- 1Connect Jira and Coda once in the Notis portal.
- 2Create an automation from Automations, New Automation, and give it a name.
- 3Tell Notis which Coda rows are safe to delete when a Jira issue changes, using criteria that can be checked from available data.
- 4Pick the Jira Updated Issue trigger and choose where run reports should go.
- 5Test with one real example and verify the selected rows before relying on the cleanup.
Questions about this workflow
Does this trigger run for comments?
No. Updated Issue fires when an issue field changes; it does not fire for comment activity.
Can it delete rows based on arbitrary assumptions?
The deletion rule needs to be stated in your instruction and depend on information Jira or Coda provides. Do not use it for criteria that neither app exposes.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Coda. A trigger fires from one place; an action lands in another.
Jira triggers
Coda actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add a category for pack
Add a publishing category for a given pack.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add a maker for pack
Set a maker for a given pack. used to display makers for a pack in the corresponding packs page.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Add a permission for pack
Create or modify user, workspace, or global permissions for a given pack.
New Project
Triggered when a new project is added in Jira
Add custom domain
Add a custom domain to a published doc.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Add permission
Adds a new permission to the doc.
Begin content export
Initiate an export of content for the given page.
Content export status
Check the status of a page content export
Copy Document
Creates a copy of an existing coda document. this action allows you to duplicate a document while optionally specifying a new title and location for the copied document.
Connect any two apps with Notis in the middle.
Jira and Coda, 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 Coda.