> ## 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.

# Sync Notion databases into Catalog

> Use attributes your teams already keep in Notion, like owners and RTOs, during incidents without exporting by hand.

Sync a Notion database into [Catalog](/catalog/catalog-setup) when the source of truth for services, features, or compliance attributes already lives in Notion. Each page becomes a catalog entry. Columns you choose become attributes you can use in custom fields, workflows, and incident forms.

Catalog sync uses the [Notion integration](/integrations/notion) you may already have installed, so there's nothing extra to connect. It's read-only: we copy values into incident.io and never write back to Notion.

## Set up

<Steps>
  <Step title="Install Notion and share the database">
    [Install the Notion integration](/integrations/notion) if you have not already.

    In Notion, share the database itself with the incident.io connection. Sharing a parent page does not always make child databases searchable. See [Grant access to specific pages](/integrations/notion#grant-access-to-specific-pages).
  </Step>

  <Step title="Create a catalog type from the database">
    Open [Catalog](https://app.incident.io/~/catalog) and create a new type. Choose **Notion Database**, then pick the database.

    We create a type named after the database (for example, **Notion Features**). Every page in that database becomes an entry. The page title maps to the entry name, and we always include a **URL** attribute that links back to Notion.
  </Step>

  <Step title="Import the columns you need">
    Open the type, then use **+ Import from Notion** to add columns one at a time. Only **Name** and **URL** come with the type. Extra columns are opt-in, because databases often include internal columns that do not belong in Catalog.

    Values populate on the next [sync](/catalog/resync-data) (hourly, or immediately if you press **Sync**).
  </Step>
</Steps>

Each database can back only one catalog type. If a database is missing from the picker, check whether a type already exists for it.

## Supported columns

| Notion property   | Catalog attribute                                      |
| ----------------- | ------------------------------------------------------ |
| Title (page name) | Entry name                                             |
| Rich text         | Text                                                   |
| Number            | Number                                                 |
| Select            | String                                                 |
| Multi-select      | String, multi-value                                    |
| Status            | String                                                 |
| Checkbox          | Boolean                                                |
| URL, email, phone | String                                                 |
| Date              | Timestamp                                              |
| People            | [Notion User](/catalog/connected-users)                |
| Formula           | Follows the formula result (text, number, and similar) |

Only these property types can be imported. Anything else is skipped and won't appear in **Import from Notion**.

Attributes are bound to Notion's stable property ID. Renaming a column in Notion keeps sync working. Deleting a column leaves the attribute in Catalog; it stops receiving new values until you remove it.

## Keep data current

Catalog syncs Notion database pages about once an hour. Press **Sync** on the type if you need an upstream change sooner. Hover the button to see when the type last synced.

<Tip>
  People columns resolve to Notion User entries. Link those users to incident.io users from **Connected accounts** if
  you want workflows to page or invite the right person. See [Connected users](/catalog/connected-users).
</Tip>

## FAQs

<AccordionGroup>
  <Accordion title="Why isn't my database in the picker?">
    Share the database with the incident.io connection in Notion (**Settings → Connections**, or the database's **••• →
    Connections**). Confirm the [Notion integration](/integrations/notion) is installed, and that you have not already
    created a catalog type for that database. If you have many databases, type in the picker to filter the list.
  </Accordion>

  <Accordion title="Is this the same as using Notion for Investigations or follow-ups?">
    No. [Investigations document sources](/nexus/documentation) index pages so AI can search them. [Follow-up
    export](/integrations/notion-follow-ups) creates and updates task pages. Catalog sync turns a database into entries
    and attributes you can use across incidents. You can use all three on the same Notion install.
  </Accordion>

  <Accordion title="Can I use the same database for follow-ups and Catalog?">
    Yes, as long as the integration can access it. Catalog only reads the database. Follow-up export writes pages when
    you export work.
  </Accordion>
</AccordionGroup>