Skip to main content
Sync a Notion database into Catalog 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 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

1

Install Notion and share the database

Install the Notion integration 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.
2

Create a catalog type from the database

Open 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.
3

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 (hourly, or immediately if you press Sync).
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

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.

Filter entries before syncing

By default, every page in the database becomes an entry. To import only some pages, edit the catalog type and turn on Filter entries before syncing. Then pick the properties to filter on and the values to keep.
  • Select, status and checkbox properties can be used as filters.
  • A page is imported when it matches any of the values for a property, and every property you filter on.
As you edit, incident.io shows some example pages that match. Notion can’t count matching pages, so you won’t see a total. When you save, the next sync imports only matching pages and archives entries that no longer match.

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

FAQs

Share the database with the incident.io connection in Notion (Settings → Connections, or the database’s ••• → Connections). Confirm the Notion integration 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.
No. Investigations document sources index pages so AI can search them. Follow-up export 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.
Yes, as long as the integration can access it. Catalog only reads the database. Follow-up export writes pages when you export work.