Operations & execution

Turn Meeting Notes into a Project Task Database with Notion AI

Summary

Cihan's view: Open Notion Agent from the sidebar or bottom-right icon, paste your meeting notes, and ask it to create a task database with columns for task, owner, due date, and status. Notion AI will extract action items, populate the database, and you can then review, adjust, and share it with your team.

Choose another work task →

Who this is for and the question

You just finished a project kickoff meeting with six people. The notes are a mix of decisions, open questions, and action items scattered across a page. You need a clean task database — task name, owner, due date, status — that the team can filter and update, without spending an hour copying rows by hand.

Question: How do you turn unstructured meeting notes into a structured, shareable task database using Notion AI?

Complete fictional input

Below is a realistic but fictional set of meeting notes from a Q4 Website Redesign Kickoff meeting. Copy this into a new Notion page to follow along.

# Q4 Website Redesign Kickoff — Meeting Notes
Date: 2026-11-10
Attendees: Maya (PM), Raj (Design), Priya (Frontend), Sam (Backend), Lena (Content), Tom (SEO)

## Decisions
- New homepage launches 2026-12-15; full site by 2027-01-31.
- Design system v2 (tokens, components) ships first — blocker for frontend.
- SEO requirements baked into component library, not retrofitted.
- Content freeze 2026-12-01 for homepage; 2027-01-10 for rest.

## Action items
- Maya: Finalize project brief and share with stakeholders by 2026-11-12.
- Raj: Deliver design system v2 tokens (colors, spacing, type) by 2026-11-19.
- Raj: Create homepage high-fidelity mockups in Figma by 2026-11-26.
- Priya: Set up Next.js repo with design-system package by 2026-11-19.
- Priya: Build component library Storybook by 2026-12-03.
- Sam: Design API contracts for CMS and search by 2026-11-26.
- Sam: Implement preview deployment pipeline by 2026-12-10.
- Lena: Audit existing content and map to new IA by 2026-11-26.
- Lena: Write homepage copy (hero, value props, CTAs) by 2026-12-01.
- Tom: Define SEO component specs (meta, schema, headings) by 2026-11-19.
- Tom: Provide redirect map for legacy URLs by 2026-12-10.

## Open questions
- Do we need a staging environment separate from preview deployments? (Sam to confirm)
- Should the blog migrate now or phase 2? (Lena/Maya to decide by 2026-11-15)
- Accessibility audit scope — WCAG AA only or AAA for key flows? (Raj/Tom to propose)

Step-by-step instructions

  1. Create a new Notion page and paste the meeting notes above into it. Give the page a clear title like “Q4 Website Redesign Kickoff — Notes.”

  2. Open Notion Agent. Click the circular face icon in the bottom-right corner of the page, or press Shift + Ctrl + J (Windows) / Shift + Cmd + J (Mac) to open the Agent in a full-page view. The Agent sidebar appears on the right.

  3. Ask Notion Agent to extract action items and build a database. In the Agent chat, enter this prompt:

    Read the meeting notes on this page. Extract every action item with its owner and due date. Create a new database on this page called “Q4 Redesign Tasks” with these properties: Task (Title), Owner (Person), Due Date (Date), Status (Select with options: Not started, In progress, Done, Blocked). Populate the database with one row per action item. Set Status to “Not started” for all rows.

    Press Enter. Notion Agent will read the page, parse the action items, create the database, and fill in the rows.

  4. Review the created database. The Agent will show a preview of the database it created. Check that:

    • All 11 action items appear as rows.
    • Owner names match attendees (Maya, Raj, Priya, Sam, Lena, Tom).
    • Due dates match the notes (e.g., 2026-11-12, 2026-11-19, etc.).
    • Status column shows “Not started” for every row.
  5. Accept or refine. If the database looks correct, accept the result in the Agent chat. If something is missing or wrong, type a follow-up prompt such as:

    “Add the two open questions as tasks with Status ‘Blocked’ and Owner ‘TBD’.” “Change Raj’s design system tokens due date to 2026-11-18.” Then accept when satisfied.

  6. Adjust the Owner column to a Person property (optional). By default the Owner column may be plain text. To make it a true Person property so teammates receive notifications, change the column type to Person and select the matching workspace member for each row.

  7. Add a grouped view for each owner. Create a new table view, then group it by the Owner property. Now each owner sees their own section.

  8. Share the page with the team. Use the page sharing option, add your teammates, and give them edit access so they can update their task status directly.

Illustrative output (example)

Q4 Redesign Tasks — Database (11 rows)

Task Owner Due Date Status
Finalize project brief and share with stakeholders Maya 2026-11-12 Not started
Deliver design system v2 tokens (colors, spacing, type) Raj 2026-11-19 Not started
Create homepage high-fidelity mockups in Figma Raj 2026-11-26 Not started
Set up Next.js repo with design-system package Priya 2026-11-19 Not started
Build component library Storybook Priya 2026-12-03 Not started
Design API contracts for CMS and search Sam 2026-11-26 Not started
Implement preview deployment pipeline Sam 2026-12-10 Not started
Audit existing content and map to new IA Lena 2026-11-26 Not started
Write homepage copy (hero, value props, CTAs) Lena 2026-12-01 Not started
Define SEO component specs (meta, schema, headings) Tom 2026-11-19 Not started
Provide redirect map for legacy URLs Tom 2026-12-10 Not started

This table is an illustrative example of the database Notion Agent creates. Your actual output will be an interactive Notion database on the page.

Acceptance checks

  • A database titled “Q4 Redesign Tasks” exists on the page.
  • The database has exactly four properties: Task (Title), Owner, Due Date (Date), Status (Select).
  • All 11 action items from the notes appear as rows.
  • Each row has an Owner name matching an attendee.
  • Each row has a Due Date matching the notes.
  • All Status values are “Not started” (or your refined values).
  • Teammates can open the page, see the database, and edit Status.

Troubleshooting

Symptom Likely cause Fix
Agent says it cannot create a database Workspace plan does not include Notion AI database creation, or AI features are disabled Check Settings → Notion AI → ensure database creation is enabled; Business/Enterprise plans required for full Agent actions
Owner column stays as plain text Agent created a Text property instead of Person Change the column type to Person and assign workspace members
Due dates show as text not Date chips Agent used a Text property Change the column type to Date
Missing action items Notes format was ambiguous (no clear owner/date pattern) Add a follow-up prompt: “Also include the open questions as tasks with Owner TBD and Status Blocked”
Agent cannot see the notes Notes are on a different page or in a toggle that is closed Ensure notes are on the same page and toggles are open; or @-mention the page in your prompt

Closing

This workflow turns a raw meeting transcript into a live, filterable task board in under five minutes — no copy-paste marathon required. The database stays in Notion, so status updates, comments, and notifications all work natively. Next time you leave a meeting with a page of notes, hand the extraction to Notion Agent and get straight to execution.

Want more practical AI-for-work tutorials like this? Subscribe at https://www.cihanuygur.com/#signup

Sources

About Cihan

Creator and operator focused on practical AI for business professionals. Background and editorial approach →