Connect Notion to Rootly to automatically create and update incident retrospective pages in your Notion workspace.
Rootly’s Notion integration automatically creates retrospective pages when incidents occur. Each page is populated with incident details, timeline, and action items — giving your team a single source of truth without manual documentation.
Rootly recommends performing the installation with a service account to ensure the integration does not break if the installing user leaves the company. Ensure you are logged in as an Admin in Rootly. You will also need Editor or Owner access to the parent Notion page where Rootly will create pages.
To connect Notion to Rootly, you will authorize via OAuth and select which Notion pages Rootly is allowed to access. Rootly can only create pages within the pages you explicitly grant access to during this step.
1
Open Rootly Integrations
In Rootly, navigate to Configuration → Integrations and search for Notion.
2
Authorize in Notion
Click Setup. You will be redirected to Notion. Click Select pages to choose which pages Rootly can access.
3
Select Pages
Choose the parent pages where you want Rootly to create incident retrospective pages, then click Allow access.
4
Confirm Connection
You will be redirected back to Rootly with a success message confirming the integration is connected.
Your Notion workspace is now connected. You can verify the connection in Notion under Settings and Members → Connections — Rootly should appear in the list.
Workflows let you automate Notion page creation and updates for incident retrospectives. You can trigger page creation when an incident resolves or a retrospective begins, and populate the page with timeline data, action items, and custom template content using Liquid variables.
Action
Description
Create Notion Page
Creates a new retrospective page in a specified Notion parent page
Update Notion Page
Overwrites an existing Notion page with the latest incident data
Navigate to Workflows in Rootly and click Create Workflow.
2
Choose Workflow Type
Select the workflow type that matches your use case — Incident, Retrospective, or Pulse.
3
Configure Triggers
Triggers define when the workflow runs. Choose the event that should kick off page creation.
Trigger
When it fires
Incident Created
A new incident opens
Incident Updated
Severity, status, or other fields change
Incident Status Changed
The incident moves to a specific status
Incident Resolved
The incident is resolved
Retrospective Started
The retrospective process begins
Manual Trigger
Run on demand from the UI
4
Add Conditions (Optional)
Use conditions to control when the workflow fires after the trigger. For example, only create a Notion page for SEV-1 or SEV-2 incidents, or only for specific teams or environments.
Use this action to create a new retrospective page in Notion for an incident. The page is created under a parent page you select and is populated using the template and fields you configure.
Field
Description
Page
The parent Notion page where the new page will be created. Must be a page Rootly was granted access to during installation.
Title
The page title. Supports Liquid syntax — use the incident title or any other variable.
Set the retrospective status to published immediately rather than leaving it as draft.
Show Timeline as Table
Include the incident timeline. Uncheck if you want images to appear inline — Notion does not support images in tables.
Show Action Items as Table
Include follow-up action items. Only follow-up type items are included — tasks are excluded as they are completed during the incident, before the retrospective.
Skip on Failure
Prevent the workflow from stopping if this action fails.
Use this action to overwrite an existing Notion page with the latest incident data. This is useful for keeping the retrospective page current as the incident progresses.
This is an overwrite operation. Any manual changes made to the Notion page will be replaced when this action runs.
Field
Description
File
The Notion page to update. Use incident.notion_page_id via Liquid to reference the incident’s existing page.
Title
Updated page title. Leave blank to keep the existing title.
Post Mortem Template
Template to apply when updating. Overwrites existing content.
Show Timeline as Table
Include the incident timeline.
Show Action Items as Table
Include follow-up action items.
Skip on Failure
Prevent the workflow from stopping if this action fails.
Ensure you granted access to the specific page during OAuth. Go to Settings and Members → Connections in Notion to confirm Rootly is listed. If missing, disconnect and reconnect the integration in Rootly. Also check that the page is not in a private or restricted workspace.
No pages are available during setup
Notion only shows pages you have Editor or Owner access to. If the workspace has restricted pages, an admin must grant you access first. Try expanding parent pages in the selector to see nested pages, then restart the authorization flow.
Pages are not being created after running a workflow
Verify the parent page selected in the workflow action is one you granted access to during installation. Check workflow run logs under Workflows → Your Workflow → View Runs for error details. Re-authorize the integration if the connection has expired.
Check the workflow run log under Workflows → Your Workflow → View Runs for error details. Confirm the parent page selected in the action is one Rootly was granted access to during installation. Re-authorize the integration if the connection has expired.
Manual edits to my Notion page keep getting overwritten
The Update Notion Page action is a full overwrite. If you need to preserve manual edits, disable any workflows that trigger an update on that page, or add conditions to prevent them from running after a certain point in the incident lifecycle.
Can I use custom Liquid templates for the page content?
Notion does not support images inside tables. Uncheck Show Timeline as Table to render the timeline inline, which will allow images to display correctly.