Skip to main content
After your incident is over, it can be useful to dig into what happened in an incident, why, and how it can be prevented in the future. Our Notion integration lets you export post-mortems into Notion so you can collaborate with your team. You can also turn on Notion as a follow-up issue tracker and export follow-ups into a Notion database, or sync a database into Catalog so attributes your teams already maintain there are available during incidents. A post-mortem exported into Notion, with severity, affected teams and key timestamps filled in

Installation

Go to Settings → Integrations, search for Notion and click its card. The Notion card on Settings → Integrations, alongside other integration cards It’s important to know that when the integration is installed, the connection to incident.io will belong to the user who installed it. Notion connections like this, which use OAuth, belong to a specific user. For this reason, you may wish to set up a dedicated service or “bot” account. Click Install in Notion, and you’ll be redirected to the install flow within Notion. Review the permissions we’re requesting, and click Next Notion permission screen listing the access incident.io is requesting, with a Next button We also need to install a template for the pages we create. Click Use a template provided by the developer, and then Allow access Notion asking how to share pages, with Use a template provided by the developer highlighted

You’re done

Congratulations, it’s been installed You’ll find the page in your private Notion space – move it to somewhere that suits you, and that can be accessed by everyone. Configure Notion integration dialog confirming the connection and linking to the new post-mortem database

Sync a database into Catalog

If a Notion database is already the source of truth for services, features, or compliance attributes, create a catalog type from it. Pages become entries; columns you import become attributes for custom fields and workflows. See Sync Notion databases into Catalog for setup, supported columns, and sync behavior.

Exporting your first post-mortem

  1. Open an incident and go to its Post-incident tab
  2. In the Post-mortem section, click Create post-mortem
The Post-incident tab of an incident, with Create post-mortem next to the Post-mortem heading
  1. The Create post-mortem modal will appear
  • Select Notion from the destinations
  • Select your template
  • Select which timezone should be used
  • Click Create and wait a few seconds
  • Your post-mortem document has been created, and it’ll be linked to the incident page

Grant access to specific pages

You can also connect Notion pages and databases as document sources for investigations. When you add a page there and see this error, the URL is usually fine:
We couldn’t find this Notion page or database. Check the URL, or share it with the incident.io integration in Notion.
The integration can only read the pages and teamspaces you select in Notion, so a newly created page or teamspace stays invisible to us until you grant access to it. To grant access, open Notion and go to Settings → Connections, select incident.io, and under Page access add the pages or teamspaces you want to sync, including the one that failed. There’s no need to reconnect from incident.io.

Grant access via reconnect

If the above doesn’t work, reconnect the integration and select the pages you need on Notion’s consent screen:
  1. Go to Settings → Integrations and open Notion.
  2. Click Reconnect.
  3. On Notion’s consent screen, under View pages you select, choose every page or teamspace you want to sync, including the one that failed.
  4. Click Allow access.
The Notion consent screen where you select which pages incident.io can access
If Notion asks you to install the post-mortem template again, choose Skip. Your existing post-mortem database stays connected as long as its teamspace is still selected.