Summarize meeting notes and extract actions in Notion
Meeting notes are written fast and read by nobody. An Orkeste agent reads the notes page in Notion, adds a short summary with the decisions, the owners and the deadlines, and posts the action items to the team's Slack channel.
The problem
Actions agreed in a meeting live in a page nobody reopens. A week later, everyone remembers a different decision.
How the workflow runs
Runs: When you start it after a meeting, or every day for new notes pages.
Find the page: The agent searches Notion for the notes page, up to ten pages per search.
Read it: It reads the notes as written.
Extract: It lists the decisions, the action items, their owners and their deadlines.
Approve: The summary can wait in Validations for the meeting host.
Add it to the page: The summary is added at the end of the page under a clear heading.
Post the actions: The action items are posted to the team's Slack channel.
With approval on, the summary is added and shared only after the meeting host approves it.
Who does what
Notes summariser: Extracts decisions and actions from the notes.
Meeting host (human): Checks the summary before it is shared.
What this workflow does not do
Adds the summary to the page; it does not reorganise the notes.
Does not join or record meetings.
Posts to a channel; it does not send direct messages to owners.