Notion Docs Watch Agent with OpenCode
Notion fires an update event while people are still typing, so the cost question is really about what gets dropped and how fast. Pages outside your rules end the run at the first read, and an edit that looks unfinished ends it without a message. OpenCode leaves the engine underneath to you, which is how you set the price of that reading against how noisy your workspace is.
Watch it work before it's live
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.
Set up in minutes
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 OpenCode
Preselected for this page — connect your OpenCode 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.
Why OpenCode for this agent
Silence costs one read
Excluded sections, routine edits and work in progress all finish early. On a busy workspace the majority of runs never reach the Slack call.
Reading is the whole bill
There is no write path anywhere, so what you pay for is opening blocks and judging them. Choosing an engine for that one task is the whole of the tuning available.
Before you fork
Our workspace is noisy but the pages we care about are not. Are we paying for the noise?
Partly. Any update on a page the connection can see starts a run, and the run ends quickly once the page falls outside your rules, so noise costs a cheap first read rather than a full judgement. The lever that genuinely works is sharing the connection with fewer pages, since a page it cannot see raises nothing.
Run it with a different agent
Put Notion Docs Watch Agent to work on OpenCode
Free to start. Guided setup, a test run against staged conversations, and it's live.