Put a retrospective structure in place from project start
When Jira adds a project, copy your Coda retrospective doc so the team has a known place to capture lessons as work progresses.
Trigger
New Project
Triggered when a new project is added in Jira
Action
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.
Why this helps
Retrospectives are harder to run when teams wait until the end to decide how they will collect lessons.
- Have a retrospective structure ready before project wrap-up.
- Give the team one place to add lessons over time.
- Avoid recreating reflection prompts for each project.
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 to copy your Coda retrospective doc when a Jira project is added and use available project details for the copy title.
- 4Pick the Jira New Project trigger and choose where run reports should go.
- 5Test with one real project event and confirm the copied doc is ready for later use.
Questions about this workflow
Why create a retrospective doc at project start?
It gives the team a consistent place to save lessons as the work happens, while the details are fresh.
Can the copied doc include a project name?
Ask Notis to use available project details. If the event does not provide a needed detail, supply it in the instruction or omit it.
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.