Skip to content
Notis

Make project risks visible from the beginning

Give each new project a Coda risk register so assumptions, risks, and mitigations have a clear home from the start.

Trigger

New Project

Triggered when a new project is added in Jira

Action

Create doc

Creates a new coda doc, optionally copying an existing doc. note that creating a doc requires you to be a doc maker in the applicable workspace (or be auto-promoted to one).

Why this helps

Project risks often surface late because there is no shared place to record and revisit them.

  • Create a shared place to log emerging risks.
  • Make assumptions easier to revisit.
  • Support earlier discussion of mitigations.

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 create a Coda risk register doc for each new Jira project with available context and sections for risks, assumptions, and mitigations.
  • 4Pick the Jira New Project trigger and choose where run reports should go.
  • 5Test with one real project event and confirm the doc gives the team a useful starting structure.

Questions about this workflow

Does the workflow know the project's risks automatically?

No. It creates a structure and can include available project details. People need to supply and assess risks.

Can I use a preferred doc layout?

Create doc can optionally copy an existing doc. Specify it in your instruction if you want the risk register to use that structure.

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.

TriggerScheduled

Add a category for pack

Add a publishing category for a given pack.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Add a maker for pack

Set a maker for a given pack. used to display makers for a pack in the corresponding packs page.

ActionInstant

New Issue

Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.

TriggerInstant

Add a permission for pack

Create or modify user, workspace, or global permissions for a given pack.

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

Add custom domain

Add a custom domain to a published doc.

ActionInstant

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.

TriggerInstant

Add permission

Adds a new permission to the doc.

ActionInstant

Begin content export

Initiate an export of content for the given page.

ActionInstant

Content export status

Check the status of a page content export

ActionInstant

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.

ActionInstant

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.