> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rootly.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Notion
> 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.
## Features
Retrospective pages are created automatically when incidents resolve or retrospectives begin.
Incident timeline and follow-up action items are included in every page.
Use your own retrospective templates with Liquid variables for dynamic content.
Re-generate pages with the latest incident data at any point via workflows.
## Before You Begin
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.
## Installation
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.
In Rootly, navigate to **Configuration → Integrations** and search for **Notion**.
Click **Setup**. You will be redirected to Notion. Click **Select pages** to choose which pages Rootly can access.
Choose the parent pages where you want Rootly to create incident retrospective pages, then click **Allow access**.
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.
## Verify the Connection
After connecting, confirm in Notion that Rootly has been granted access:
1. Open the parent page you selected during authorization
2. Click the **⋯** menu → **Connections**
3. Confirm Rootly appears in the list
## Workflow Actions
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 |
### Create a Workflow
Navigate to **Workflows** in Rootly and click **Create Workflow**.
Select the workflow type that matches your use case — **Incident**, **Retrospective**, or **Pulse**.
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 |
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.
Click **Add Action** and search for **Notion**.
### Create Notion Page
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. |
| **Post Mortem Template** | A pre-built retrospective template from [Retrospective Templates](https://rootly.com/account/retrospective-steps?tab=documents). |
| **Mark Post Mortem as Published** | 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. |
| **Enabled** | Toggle this action on or off for testing. |
### Update Notion Page
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. |
| **Enabled** | Toggle this action on or off for testing. |
## Variable Reference
Use these variables in page titles and templates. Use the [Liquid Variable Explorer](https://rootly.com/account/help/liquid-explorer) to test variables with real incident data.
### Incident Variables
| Variable | Description |
| ------------------------- | ---------------------------------- |
| `incident.title` | Incident title |
| `incident.summary` | Incident summary |
| `incident.severity` | Severity level (for example, SEV1) |
| `incident.status` | Current status |
| `incident.started_at` | When the incident started |
| `incident.resolved_at` | When the incident was resolved |
| `incident.commander.name` | Incident commander name |
| `incident.url` | Link to the incident in Rootly |
### Notion Variables
| Variable | Description |
| -------------------------- | ------------------------------------------------------------ |
| `incident.notion_page_id` | ID of the incident's Notion page — used in the Update action |
| `incident.notion_page_url` | URL to the Notion page |
## Uninstall
**In Rootly:**
1. Go to **Configuration → Integrations** and find **Notion**
2. Click the **Connected** button to reveal the disconnect option
3. Click **Delete**
**In Notion** (to fully revoke access):
1. Go to **Settings and Members → Connections**
2. Find **Rootly** and click **Disconnect**
Disconnecting from Rootly does not remove existing Notion pages created by Rootly. Those pages remain in your Notion workspace.
## Frequently Asked Questions
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.
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.
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.
### Workflow Questions
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.
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.
Yes — define a custom retrospective template in [Retrospective Templates](https://rootly.com/account/retrospective-steps?tab=documents) and select it in the Post Mortem Template field. Use the [Liquid Variable Explorer](https://rootly.com/account/help/liquid-explorer) to build and test your template.
Notion does not support images inside tables. Uncheck **Show Timeline as Table** to render the timeline inline, which will allow images to display correctly.
## Related Resources
* [Workflows](/workflows/workflows)
* [Retrospectives](/retrospectives/retrospectives)
* [Integrations overview](/integrations/overview)