a notion bot that keeps the next step easy to find

what a bot can do in Notion

a useful notion bot knows which page is the source and which page may receive new text. these actions let it read a workspace, inspect a record and add a bounded update without treating every page as a blank canvas.

composio, the connection service dusk bot uses for apps, lists 60 Notion actions (catalog version 20261101_00, read 12 november 2026⁵). dusk bot treats 24 of them as reads, 2 as sends and the other 34 as changes. an action counts as a read only when its name starts with a read word like get, list or search, so a bot you allow only to read can never call the rest. a send is anything that reaches a person outside the app or moves money, like create comment: it waits for your Allow unless you've given that bot a daily amount it may send alone.

connect Notion

1. open Connected apps in the sidebar.
2. pick Notion and sign in on Notion's own page, so your password goes to them and never to a bot.
3. choose which bots may use it, and whether each may only read or may also change things. your bookkeeper doesn't need your Notion.
4. ask in plain words. reading and drafting happen freely; sending asks you first.

connect notion through Connected apps and give access to the bot responsible for documentation. notion handles the sign-in. share a page reference in the chat and identify the destination separately. start by asking the bot to read and describe what it found before enabling any upkeep.

routines to copy

pick one source of truth for each job. the routines below keep incomplete fields, decision capture and document age as separate questions.

each monday at 2, inspect the notion project records i linked in this chat. list any missing owner, next step or target date. do not fill gaps by guessing and do not edit the records. group your findings by project.

every thursday at 4, read the acme meeting notes page in notion. collect decisions explicitly agreed this week and the reason stated for each. prepare an addition for the decision log here. ask me before you change anything in notion.

on the first monday of each month at 10, read the notion onboarding pages linked here. flag dated instructions, unresolved comments and references that need an owner to check them. explain what needs verification; do not rewrite or archive pages.

what it asks you first

notion page edits and record updates are app changes. they are not promised an Allow card by the sending rule. a read-only bot cannot make those changes, and an action restriction can narrow a writer to only the tools it needs.

if you want a writer to propose its work first, include "ask me before you change anything" in the routine. comments are posts, so sending controls apply to posting them; keep comments disabled if the job is only to review privately.

what it cannot do

• rewrite, move or archive a notion page under read-only access. a private summary of that page is a different job and does not require those changes.
• turn an absent owner or date into a fact. the records and notes have to supply that information; the routine should flag a gap for you rather than quietly assigning someone.
• maintain a workspace on schedule while the local machine is asleep. cloud hosting keeps the bot available; the desktop app needs to stay open on an awake computer.

separate the evidence from the destination

give the bot the meeting notes as a source and the decision log as a possible destination. explain which headings it may append beneath. if delivery work is tracked in linear, let the notion page link to it instead of asking the bot to infer progress from prose.

choose the place where notes belong

a connected notion workspace and an obsidian folder are different setups. the former uses app actions; the latter is a set of files on your computer. for a broader planning workflow, the product manager page connects these smaller jobs to a working week.