Watch the walkthrough on YouTube
A Notion Custom Agent can turn Notion AI meeting notes into real tasks by watching for a meeting status change, reading the meeting summary and next steps, creating tasks in the task database, linking those tasks back to the meeting and project, and notifying the right people.
This is not about making meeting notes prettier. It is about making sure the work discussed in the meeting actually enters the operating system.
Why meeting notes still drop tasks
Notion AI meeting notes are useful. They capture the transcript, summarize the discussion, and usually pull out a list of next steps. The problem is what happens next.
If those next steps stay at the bottom of a meeting page, they are not operational. They are just text. Someone still has to copy them into a task database, connect them to the right project, add a due date, assign an owner, and make sure the team can find them later.
What the agent does
The workflow is straightforward:
- A meeting page is marked done.
- The custom agent reads the meeting notes, transcript, summary, and next steps.
- It extracts action items that should become tasks.
- It checks whether similar tasks already exist.
- It creates new tasks in the task database.
- It links each task back to the meeting and, when relevant, the related project.
- It notifies the relevant attendees or team members.
The important part is the trigger. In the video, Dave does not have the agent run immediately when a meeting ends. He uses a status change to done. That gives the team one last chance to review the notes, clean up relations, and make sure the meeting is tied to the right project before tasks are created.
Start with the meeting template
The meeting page needs enough structure for the agent to understand what it is reading. At minimum, the meeting database should include meeting title, status, attendees, meeting URL or calendar URL, related project, related client or area if useful, AI meeting notes or transcript, and a linked view of tasks filtered to that meeting.
The linked task view matters. After the agent runs, the meeting page should immediately show the tasks it created. That gives the team a review surface. If something does not belong as a task, delete it or correct it right there.
Use an instructions page
Dave separates the agent instructions into a dedicated Notion page instead of putting everything only inside the agent settings. That is the right move when you have multiple automations or agents running in the same workspace.
A good instructions page should define the agent's purpose, when it should run, which databases it can use, what counts as a valid task, what it should not create, how to handle missing assignees or due dates, how to link tasks to meetings and projects, and how to notify people after tasks are created.
Give the agent narrow access
This workflow needs edit access, but only to the right places. The agent should be able to read the Meetings database, create and edit tasks in the Tasks database, and update relations to Projects, Clients, or Areas if those databases are part of your task structure.
It does not need web access. It does not need the whole workspace. It does not need to browse unrelated pages. Narrow access makes the agent faster, safer, and easier to debug.
Use status as the trigger
The best trigger in this workflow is a property update: when meeting status changes to done, run the task extraction agent. That trigger is better than running on a schedule or immediately after every meeting because it creates a human checkpoint.
For teams, this also creates a habit: meeting is only complete when the meeting page is cleaned up and marked done.
Guardrails that matter
- Do not create duplicate tasks if a similar task already exists from the same meeting.
- Do not invent assignees if the notes do not name an owner.
- Do not invent due dates if the notes do not support one.
- If a next check-in date is mentioned, set task due dates before that meeting.
- Link every created task back to the source meeting.
- If the meeting is related to a project, link the task to the same project.
- Leave ambiguous action items for manual review instead of turning everything into tasks.
Notify the right people
A later refinement in the video is having the agent notify meeting attendees after tasks are created. That matters because creating tasks silently is not enough. The people responsible need to know that the work moved from meeting notes into the task database.
This is also a good example of how agents improve over time. You build the first workflow, watch what breaks or feels incomplete, then ask the agent to update its own instructions.
FAQ
Can Notion AI meeting notes automatically create tasks?
Not by themselves in a reliable operating workflow. A Custom Agent can read the notes and create tasks when triggered, but you need database structure, permissions, and instructions to make the output trustworthy.
What is the best trigger for creating tasks from meeting notes?
A meeting status change is usually best. When the meeting is marked done, the agent can run after someone has reviewed the notes and connected the meeting to the right project or client.
Should every next step become a task?
No. Some checklist items are too vague, already complete, or not worth tracking. The agent should create tasks only when the action item is specific enough to belong in the task database.
The Workcraft take
The meeting is not done when the call ends. The meeting is done when the decisions, owners, and next steps have entered the system where work actually happens.
This is where Notion Custom Agents are useful: not as a flashy AI demo, but as a bridge between conversation and execution. If your meetings create work, your workspace needs a clean path from notes to tasks.