The message shape is strict: a linked title, then three bullets of one sentence each in a fixed order. What the page now says, where it sits and who last touched it, and whether a reader has to do anything. Codex holds a well scoped output rule like that, including the part where the third bullet plainly says there is nothing to do.
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
Runbook: payment webhook backlog
Created by Yuki Tanaka
The escalation section was replaced. It used to say page the payments on-call after 15 minutes of backlog. It now says wait for the automatic drain and only page above 50,000 queued events for 30 minutes. A callout with the Grafana link was added and the rollback steps were deleted. Owner property still reads Yuki Tanaka.
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect Notion
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Watch rules
The pages you genuinely care about, described however you would describe them to a colleague, whether that is a section, a title prefix or an owner, plus which edits you consider routine and the handful of pages where any change at all should reach the channel.
Runs on Codex
Preselected for this page — connect your Codex account during setup, or switch to NoClick's built-in models with one click.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
The instruction is to describe the instruction the page now carries rather than narrate an edit. Where the change itself was not visible, saying so is the required answer.
A page never gets two messages inside one editing session, and pages your rules exclude finish in silence. Both are rules about output that does not happen.
No, and that is a real limit worth knowing before you fork. The event carries a page id and an editor rather than the change, so the agent reports what the page currently establishes and states when the change itself was invisible to it. For pages where a true diff matters, the message is a prompt to open Notion history rather than a replacement for it.
Free to start. Guided setup, a test run against staged conversations, and it's live.