dusk botcollect unresolved comments from a notion page with ai
walk into the review knowing what still needs an answer. a bot reads unresolved comments on a notion page or one block and brings the questions to your chat.
it only reads, with access to that page and its comments. resolved discussions stay out. name the page or paragraph you mean, and ask it to finish the list before summarising.
fetch comments, in plain words
point to the discussion you actually want. name the page or paste its link. for a comment on one paragraph, point out that part and let the bot find it. page discussion and block discussion have different scopes.
the connection needs permission to read the page's comments. a sharing problem can look like a missing page. ask the bot to show the error instead of claiming nobody left feedback.
a routine to copy
paste this into a chat with your bot
each thursday at 14:35, read unresolved page-level comments on the notion page cresswell pavilion proposal. keep fetching batches until the results end.
list each question and its author here. say where access or an error stopped the read. show that the report covers page comments, with block comments and resolved discussions left out. never reply, resolve a discussion or rewrite the proposal. if nothing remains open, say so in one line.- when
- thursdays at 14:35
- needs
- notion read only; share the proposal page with the connection and allow comment reading
what comes back looks like this (an example)
cresswell pavilion proposal
- alice: which entrance stays open during setup?
- mateo: where is the revised equipment list?
page comment list finished. block comments and resolved discussions excluded.good jobs for it
- prepare the next proposal. collect open questions before sending another version.
- focus on a disputed paragraph. read its comments without searching every document.
- give the author a clear queue. turn unresolved feedback into questions to answer.
- get ready for the call. see which discussions remain open on the named page.
before it runs
dusk bot counts Fetch comments as a read: it looks and changes nothing. a bot you allow only to read can use it.
the permissions Notion asks for to run it: insert_content.
how to start
- keep this job read only. connect notion and allow the bot to read feedback.
- share the right page. include it among the pages the notion connection can open.
- test the scope. name the page or paragraph and ask for one read before scheduling.
- read the coverage note. it should name the page or block it covered. pause the routine when proposal review ends.
limits worth knowing
- resolved means outside this list. this action doesn't return the full history of a discussion.
- give the connection access before the review. a sharing problem can return "not found" even when the page exists.
- long discussions arrive in batches. the bot should finish them before reporting a total.
- page comments don't cover every paragraph. ask separately about a specific block when its discussion matters.
the details it works from
| input | required | what it is |
|---|---|---|
page_id | no | Identifier for a Notion page from which to fetch comments. |
block_id | no | Identifier for a Notion block from which to fetch comments. |
page_size | no | The number of comments to return in a single response page. |
start_cursor | no | A pagination cursor. |
from composio's catalog for Notion (action NOTION_FETCH_COMMENTS, read 12 november 20264). your bot fills these in from what you tell it.
try it in 2 minutes
- share one notion page with the connection
- keep the bot on read only
- ask for unresolved page comments and their authors
- name the paragraph too if you need its block comments
mistakes people make
treating an empty result as approval
confirm scope and access first. resolved or block comments can sit outside the result.
asking for everything under a page
name the paragraph when its comments matter. a page-level read does not cover nested discussions.
questions
can it reply to the reviewer as well?
not through this action. it only reads. posting a reply needs a separate action and permission.
why can the bot read the page but not its comments?
comment access can be missing. ask for the error. a failed read does not mean the discussion is empty.
sources
read next
a notion bot that keeps the next step easy to findclearer notes, with a smaller edit scope.
ask ai to read a notion page for youpage text, with its gaps made visible.
find a notion page or database by asking for its titlefind the title before reading the page.
ai agents for founders and solopreneursa starter team, and the routines to copy.
claude connectors: connect the job you actually needpick a task before you connect an app.
add a batch of notes to an existing notion pageadd the notes where they belong.
drafted with ai help from the dusk bot docs and the sources listed on this page, then checked against them. if something here is wrong or out of date, write to [email protected].