InfraNestInfraNest
Notion

Notion integration

Postmortems in Notion, written for you when incidents resolve

Turn on Postmortems and, when an incident resolves, InfraNest writes the page from what it recorded: what failed, how badly and for how long, who picked it up, the timeline with your team’s notes, the issues filed for it, and what changed just before it started. Your team adds what it learned. Once you write the review in InfraNest, the page is written from it and stays up to date.

Start freeSee pricing

On Pro and up · 14-day Pro trial, no credit card · You choose which pages it can see

  • A postmortem page when an incident resolves
  • Written from your review, and kept up to date
  • Each write-up’s status on the incident
  • Tasks filed and finished by your rules
NorthwindPostmortemsPostmortem: API latency spike after a deploy

Postmortem: API latency spike after a deploy

StatusPublished

Published from the team's review in InfraNest. Change the review there: publishing again updates this page.

Open the incident in InfraNest

Summary

  • What failed: API health
  • Impact: Major
  • Started: 2026-09-28 14:54 UTC
  • Resolved: 2026-09-28 15:16 UTC
  • Lasted: 22 minutes
  • Nobody acknowledged it.

What happened

API response times climbed from about 120 ms to over 4 seconds eight minutes after release 2.31 reached production. Sam rolled the release back, and latency was normal again 22 minutes after it started.

Impact

For 22 minutes most API requests took several seconds and about 6% timed out. Checkout and the dashboard were slow but stayed up; no data was lost.

Why it happened

The release included a migration that added an index without a lock timeout. On the primary database it waited behind long-running reads and held its connections open, so the pool ran out and requests queued behind it.

What we change

  • Run schema migrations with a lock timeout, so a slow one fails instead of holding the primary database.
  • Alert when the connection pool on db-01 passes 80%, before latency reaches users.
  • Add a pre-deploy check that flags migrations expected to run longer than a minute.

A page for each incident you choose, when it resolves

Turn on Postmortems, pick the database and which incidents: all of them, only critical ones, or the monitors you choose. Each time one resolves, a page titled Postmortem: with the incident’s title appears in that database, in your workspace’s language, with a link back to the incident. The facts are already there, and a Follow-up section is left for your team. Write a test page first to see it with your own data.

  • Summary, timeline, linked issues and what changed just before
  • All incidents, only critical ones, or the monitors you choose
  • Written in your workspace’s language
  • A test page from your latest resolved incident, before any real one
Postmortem: API latency spike after a deploy
SummaryWhat failed, the impact, how long, who acknowledged it
TimelineFrom the first failure to recovery, with notes
Linked ticketsEach with a link and its last status
What changed just beforeDeploys and changes in the 30 minutes before
Follow-upLeft for your team

Write the review once, and Notion follows

The review your team writes on the incident is the record: what happened, the impact, why it happened and what you will change. When Postmortems is on, Notion is already ticked under Also publish to, and Finish review writes the page. If the switch already wrote a page for that incident, the review is written over it, so you never get two. After that, every change you save updates the page a minute later.

  • What happened, the impact, why, and what you change
  • Each follow-up listed with its issue and that issue’s state
  • One page per incident, rewritten from the review each time
  • Or publish to any database you shared, from the review
Follow-up
  • Review4 of 4 parts filled · 3 follow-ups, 1 done
    DonePriya Raghunathan
    Postmortem: API latency spike after a deployPublished

A postmortem written in Notion, linked to its incident

Some teams write the postmortem in Notion by hand. Link it from the review instead, and InfraNest shows its title, who edited it last and when, and its Status when the database has one, without copying a word of it. Either way, the incident’s Follow-up panel shows a chip that opens the page, so anyone looking at the incident can find the write-up.

  • Title, last edit and Status, never the text
  • Opened from the incident in one click
  • The database’s own Status, when it has one
  • Works for pages the connection can see
Link a write-up made elsewhere
ReviewPublish ▾ → Link a write-up made elsewhere
NotionPaste the page’s address
IncidentTitle, last edit and Status shown

The page’s text stays in Notion.

File tasks on your Notion board from any rule

If your team keeps a task board in Notion, a rule can file a task there when something happens: a certificate about to expire, a monitor going down, a domain coming up for renewal. Pick the database, write the title with values from what started the rule, and fill any column by name. A later step can comment on the task or set its Status to Done once the problem is over.

  • A task in any database you shared
  • Fill any column: dates, options, numbers, checkboxes
  • Comment on it or move it along from a later step
  • Nothing runs until you switch the rule on — see how rules are built
One rule, three Notion steps
Certificate expiringCreate Notion task
Monitor recoveredComment on Notion page
Problem overUpdate Notion page: Status Done

Built from the automation catalogue: any trigger, any of these actions.

See a postmortem of your own incident

On Pro and up, with a 14-day trial and no credit card. Connect Notion and write a test page from your latest resolved incident.

Start freeRead the setup guide

Connect Notion in about two minutes

Sign in with Notion, approve access and choose the database your postmortems go in. InfraNest only sees the pages you share with it. Then write a test page to see one with your own data.

  1. 1

    Connect your workspace

    Click Connect under Integrations → Notion and approve access, picking the database you want postmortems written in while you're there.

  2. 2

    Share the database

    In Notion, open the database, click ••• → Connections → Add connection, and pick this connection — without this step it can see nothing.

  3. 3

    Turn on postmortems

    Under Integrations → Notion, turn on Postmortems, pick the database and choose which incidents it applies to, then click Save changes.

That’s it — Notion is connected.

Full setup guide

Set up with AI

I use Notion, and I want to connect it to InfraNest (infranest.io) — it manages domains, DNS, servers and certificates across providers. InfraNest asks for: Sign in with Notion, or an installation access token. Walk me through creating that in Notion: where each setting is in the current interface, whether a read-only option exists, and how to check it works before I paste it in.

Open in Claude Open in ChatGPT

Often connected together

CloudflareCloudflareDNS · SSL · Domains · AutomationGitHubGitHubAutomationWebhookWebhookNotifications · Automation

Questions about the Notion integration

#Does this copy postmortems I already have in Notion?

No. If you already keep a write-up somewhere in Notion, you link it to the incident and InfraNest shows its title, last editor and status — it never copies the text in. Automatic postmortems are separate pages InfraNest writes itself.

#What happens if I edit the Notion page directly?

It gets overwritten. The review in InfraNest is the record, and publishing again rewrites the same page from it rather than reading back whatever you changed in Notion.

#What happens if the connection is revoked or expires?

Postmortems stop writing and the task actions start failing until it's reconnected. If you disconnect and reconnect the same workspace within 30 days, InfraNest offers to turn Postmortems back on with the same database and settings as before.

#Can InfraNest change anything in my Notion workspace on its own?

Yes, but only where you've set it up: writing postmortem pages, publishing reviews, and any task-filing automations you build create and update pages in the databases you've shared — nothing else, and nothing in databases you haven't shared.

#What do I need before connecting Notion?

A Notion connection that's been explicitly given access to the database you want to use — see the setup guide.

Start the postmortem with the facts already in it

Create your account (it starts with 14 days of Pro), connect Notion, and turn on Postmortems. Your databases stay exactly as they are.

Start free

Free plan · No credit card required · Set up in minutes