Meeting notes often contain decisions, ideas, and commitments in the same paragraph. Sending every sentence to a task tracker creates cleanup work. This n8n workflow uses notes someone has chosen to share, extracts suggested tasks, and lets a reviewer approve them before they reach the tracker.

1. Start with notes someone can review

For the first version, use a Manual Trigger and an Edit Fields node. Paste a short set of sample notes into a notes field and assign a stable meeting_id, such as weekly-ops-2026-11-12. Once the workflow works with sample data, replace the manual input with your team’s approved source for Teams notes.

Use a small test case with both commitments and discussion items:

Aisha will send the revised onboarding checklist by 18 November 2026. Omar will compare two reporting tools. The team discussed redesigning the dashboard.

2. Extract structured tasks

Give the extraction step four fields per item: task, owner, due_date, and source_excerpt. Instruct it to include only explicit commitments, preserve the source excerpt, and use null for missing fields. In the example, Aisha and Omar each get a suggested task. Omar’s due date stays null. The dashboard discussion stays in the meeting notes.

Validate the result before passing it on. Send items with a missing owner or deadline to a review queue so a person can supply the missing information. Keep the original excerpt visible in the queue. It’s the fastest way for a reviewer to tell whether a suggested task reflects the conversation.

3. Approve before creating tasks

Keep the review step separate from task creation. For a simple first version, save each suggestion to a table with a pending status, then use a second workflow to create tasks after a reviewer changes the status to approved.

Save the created task ID with the suggestion. A stable key based on the meeting ID and the source commitment helps a rerun find an existing suggestion instead of adding another one. If the tracker supports an idempotency key, pass that same key when creating the task so a retry can recover from a timeout without duplicating the task.

Before connecting real notes, run three checks:

  • Process the same sample twice and confirm you still have two suggestions.
  • Approve Aisha’s task and confirm that only her task reaches the tracker.
  • Leave Omar’s deadline blank and confirm the reviewer can see the original commitment and choose what to do with it.

This walkthrough was prepared for 9 Falcons.