Document every key decision made in Slack, automatically
Zero monitors your Slack channels and captures decisions as they happen. It scans threads, identifies what was decided, and writes each one to Notion with context, links, and category so nothing gets buried in the noise.
Zero connects:
Why important decisions disappear into Slack threads
A product call wraps up. Three decisions were made: one feature gets cut, the launch date moves two weeks, and the pricing model changes. Someone says they'll write it up. A week later, the document still does not exist, the engineer built the cut feature anyway, and two people have different memories of what was decided. Zero watches the channel. When a decision happens, it logs it immediately, with the thread link, who said it, and why.
How to ask Zero to capture decisions from Slack
@Zero monitor #product and #eng. Any time a key decision is made, capture it in the Decisions database in Notion. Include who decided it, a one-line summary, and a link to the thread.
How Zero finds, interprets, and logs decisions to Notion
Zero reads the channel
Zero scans recent threads in the specified Slack channels and looks for signals of a decision: agreements, approvals, scope changes, date commitments, and policy calls.
Zero extracts and categorizes each decision
For each decision found, Zero writes a one-line summary, records who made it, timestamps it, and links back to the original Slack thread for full context.
Logged to Notion instantly
Zero creates a new page or row in your Notion database for each decision, organized by category. The log stays current without any manual input.
Review, categorize, and share your decision log
Required integrations: Slack and Notion
Slack
Zero reads messages from specified channels to find and extract decisions. Requires read access.
Notion
Zero writes each decision to your Notion database with summary, context, and thread link.
Best practices for automated decision capture
Name the Notion database and property fields you want Zero to use. The more specific you are, the cleaner the output.
Point Zero at high-signal channels like #product, #eng, or #leadership. Avoid noisy channels like #random.
Pair this with the standup use case: start the day knowing what was decided yesterday without reading every thread.