> ## Documentation Index
> Fetch the complete documentation index at: https://docs.incident.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Export follow-ups to Notion

> Turn incident follow-ups into Notion database pages, with status, assignee, and priority sync back to incident.io.

If your team tracks work in a Notion database, you can export [follow-ups](/post-incident/follow-ups) there the same way you would to Jira or Linear. Choose a database (like choosing a Jira project), map the fields you care about, and keep working in Notion while status, assignees, and priorities stay in sync.

This is separate from [exporting post-mortems to Notion](/integrations/notion). You can use both: post-mortems for write-ups, and a tasks database for follow-up work.

## What can you do?

* **Export** follow-ups into a Notion database as new pages
* **Connect** an existing Notion page by pasting its URL
* **Sync** title, description, status, assignee, and priority back from Notion
* **Export templates** and [auto-export](/integrations/auto-export-follow-ups) rules, with the database as the project equivalent

Notion does not offer page-change webhooks, so sync runs when someone opens the follow-ups view (about once a minute while you're looking) and once a day for open exports as a safety net.

## Set up

1. [Install the Notion integration](/integrations/notion) if you have not already.
2. Open [Settings → Integrations → Notion](https://app.incident.io/~/settings/integrations) and turn on **Use as issue tracker**.
3. In Notion, share the task database (and its teamspace if needed) with the incident.io connection. See [Grant access to specific pages](/integrations/notion#grant-access-to-specific-pages).
4. Confirm the database has a **Status** property. Databases without one cannot be used for follow-up export.

## Database conventions

As a Notion database is completely free-form, we have a few built-in conventions to enable follow-ups to sync back into incident.io from Notion.

### Required: Status

The database must include a **Status** property. We use the first Status column from left to right, and rely on that to drive the status in incident.io.

Follow-up status comes from the Notion **status group** the option sits in, not from the option's display name:

| Notion status group | Follow-up status in incident.io |
| ------------------- | ------------------------------- |
| To-do               | Open                            |
| In progress         | Open                            |
| Complete            | Completed                       |

Exception: Complete options named `cancelled`, `declined`, or `not doing` (case-insensitive) sync as **not doing**.

### Optional: Assignee or Owner

A **People** property named **Assignee** or **Owner** (case-insensitive) syncs the follow-up owner.

If the database has no such column, we leave the follow-up assignee unchanged.

### Optional: Priority or Urgency

A **Select** column named **Priority** or **Urgency** (case-insensitive; Priority wins if both exist) can be filled on export from the follow-up's priority. We write the priority **option name** into Notion.

Priority changes in Notion sync back to incident.io, as long as the option names match your [follow-up priorities](/post-incident/follow-up-priorities).

### Title and description

* **Title** is required when creating a page.
* A **Description** rich-text property exports and syncs both ways when present.

### Other properties

Once you pick a database, the export form and templates list the writable properties in database order. You can map strings, numbers, checkboxes, URLs, emails, phones, dates, selects, multi-selects, status options, and people. Unwritable property types are skipped.

## Export a follow-up

1. Open the [follow-ups](https://app.incident.io/~/follow-ups) page, or an incident's follow-ups.
2. Choose **Export** (or create a new ticket) and select **Notion**.
3. Pick the database, then fill any fields your template or form requires.
4. Confirm. We create a page in that database and link it to the follow-up.

You can also set up [export templates and auto-export](/integrations/auto-export-follow-ups) under [Settings → Follow-ups](https://app.incident.io/~/settings/follow-ups). On a Notion template, choose the database first; the rest of the fields come from that database's schema.

## Connect an existing Notion page

Paste a Notion page URL into the incident channel, or use **Connect to existing** on the follow-up. Deep links with query strings or `#fragments` work. The page must be one the integration can access.

## What syncs

| Direction                        | Fields                                                            |
| -------------------------------- | ----------------------------------------------------------------- |
| Notion → incident.io             | Title, description, status (via groups above), assignee, priority |
| incident.io → Notion (on export) | Title, description, mapped template fields (including priority)   |

## FAQs

<AccordionGroup>
  <Accordion title="Why can't I select my Notion database?">
    It needs a Status property, and the incident.io connection must have access to that database (and its teamspace). Share it under Notion **Settings → Connections**, or reconnect the integration and select the right pages.
  </Accordion>

  <Accordion title="Why isn't status updating in incident.io?">
    Notion has no page webhooks. Open the [follow-ups](https://app.incident.io/~/follow-ups) page to trigger a sync, or wait for the daily catch-up. Confirm the page's status sits in the Complete group if you expect the follow-up to complete.
  </Accordion>

  <Accordion title="Can I use the same Notion install for post-mortems and follow-ups?">
    Yes. Post-mortem export and follow-up export share the Notion connection. Turn on **Use as issue tracker** only when you want follow-up export offered in the product.
  </Accordion>
</AccordionGroup>