Docubot

Quick user guide: how to get the most value from this documentation bot

Mention the bot **where the work is happening**. The best triggers are a task tracker item, a change request, an incident postmortem, or a wiki page for a system component. In your mention, include one sentence of intent like “document this change” or “summarize what shipped and add QA notes.” If there is a specific output you want, say so directly, such as “use the Change Doc format” or “focus on user-facing behavior and validation steps.”

To get high-quality docs, make sure the page you trigger from already contains the raw ingredients. Add links to the task, screenshots, release notes, relevant fields or rules, and any “gotchas” you discovered during testing. The bot will prioritize what is already written and will only list Unknowns when details are truly missing, so pasting key snippets (error messages, decision criteria, example records) dramatically improves the result.

Where to add Notion links to authoritative sources

If you want the bot to consistently pull from “source of truth” docs, create (or reuse) a small section on the page you are triggering from called something like **Authoritative sources** or **Source of truth**, then add Notion links to the canonical wiki pages and databases (for example: Systems Wiki, Runbooks/SOPs, Changelog, Architecture docs, Task tracker, and the system’s integration inventory). When you mention the bot, tell it to “use the Authoritative sources section first.” This makes the behavior portable across workspaces, since you are defining what’s authoritative locally, rather than relying on hardcoded database names.

How to make this bot work automatically

You can also make this bot hands-off automated using Notion Automations on a database, instead of relying on @mentions. For example, in your task tracker database you can add an automation like: When Status changes to “Done” → send content to Notion AI (or ping a dedicated “Docs Queue” page) with a clear instruction such as “Generate a Change Doc and link it back to this task.” Similarly, on a documentation database, you can trigger on When a new page is created (or when a “Needs write-up” checkbox is checked) to have the bot draft the first pass automatically. The key to making automations work well is to include a consistent “Authoritative sources” property/section (links to your systems wiki, runbooks, decision logs, and related tasks) so every auto-run has the right inputs without a human needing to re-explain context.