turn promises in notion meeting notes into tasks
turn “i’ll get the proof to the printer” into a task while everyone remembers who said it. this routine reads the day’s meeting notes in notion and puts each commitment beside its source line in dusk chat.
review the wording there, then approve the items you want on your follow-up page.

the message
paste this into a chat with your bot
each thursday at 4pm, read today's dated section on the notion page “production meeting log”, including its nested notes. use “production follow-ups” as the follow-up page. compare new commitments with the tasks already on the follow-up page, including finished ones.
in this chat propose one checkbox per new commitment. show the action, named owner, any agreed deadline and the source sentence. mark a missing owner or date as unstated. skip suggestions and questions. stay quiet if the notes and task list are readable and nothing new qualifies. flag missing notes or a partial read.
ask me before you change anything. append only the tasks i approve to the follow-up page. reread it before appending. never edit the minutes or add the same commitment twice.- when
- thursdays at 4pm after the production meeting’s notes are ready
- needs
- notion page and block reads for the proposal, plus the append task blocks action for approved additions. use your own notes and follow-up page titles.
what comes back
an example, not a real run
proposed checkbox · deliver the revised sleeve proof to the printer
owner: harvey bell · due friday
source: “harvey bell will deliver the revised sleeve proof to the printer by friday.”
no matching task on the follow-up page. add this checkbox?make it yours
- use your meeting’s date format. give the exact heading the note-taker uses, especially when the page holds several meetings.
- keep inference out of assignments. for “we’ll bring samples,” leave the owner unstated until someone claims the job.
- start with a proposal only. set notion to read only. copy the approved task text yourself if you prefer to maintain the list.3
when it goes wrong
- a brainstorm becomes homework. look for a promise or an agreed action. “could we try a smaller run?” belongs in the discussion.
- a retry adds a second checkbox. compare the action, owner and meeting date with existing entries, including completed work.
- the notes end inside a toggle. the block read can stop at a depth or access limit. ask for the missing section before approving tasks.1
keep a promise tied to the words people heard
read the source sentence before accepting the checkbox. “get a quote by friday” and “approve the quote by friday” commit someone to different jobs. keep the verb that the meeting actually agreed on.
if nobody took notes, this routine is the wrong pick. ask the people who attended to record the decision first.
questions
does the owner become a notion assignee?
the owner appears as text on a checkbox. the routine appends task blocks to a page. it doesn’t set a person property on a database row.1
what if the same job comes up again next week?
ask whether the team agreed to new work. a reminder about last week’s promise belongs with the existing item. a new print run can justify a separate task.
sources
- composio: notion actions, checked 12 november 2026
- dusk bot docs: routines
- dusk bot docs: connected apps
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].
turn meeting notes into a decision log
meeting prep briefs for outside calls, every weekday at 8
a notion bot that keeps the next step easy to find
draft the weekly report from the work log in google docs
add a batch of notes to an existing notion page
leave a useful notion comment where it belongs