Meeting Notes Workflow: Audio to Action Items (Obsidian + AI)

Transcribe a meeting, extract decisions and action items, and write them back into Obsidian with SystemSculpt, keeping approvals on so edits stay safe and reviewable.

Writers & CreatorsIntermediate20 min

Steps

1

Capture audio or raw notes

Record the meeting or collect rough notes into a single note so there is one source of truth.

2

Transcribe (if needed)

Run audio transcription and attach the transcript to the meeting note for search and quoting.

3

Extract decisions and actions

Ask for a concise list of decisions, action items with owners, and any open questions.

4

Write a clean recap

Generate a short recap that can be forwarded to the team without editing for tone or clarity.

5

Save back with approvals

Let SystemSculpt propose edits and approve the exact sections written into your vault.

Use this structure for your meeting note:

  • Context
  • Decisions
  • Action items
  • Open questions
  • Transcript (optional)

Inputs (copy/paste)

Before you run extraction, capture:

  • Meeting objective and attendees.
  • Raw notes or transcript text.
  • Any decisions already confirmed in call.
  • Known deadlines or follow-up expectations.

Step 1: Transcribe audio (optional)

If you have an audio recording, transcribe it first so you can search it later.

Step 2: Extract decisions and action items

Prompt idea:

  • "From this meeting note, extract decisions and action items. For action items, include owner, due date (if stated), and a one-sentence definition of done. Do not invent details."

Step 3: Produce a clean recap

Prompt idea:

  • "Write a 150 to 250 word recap that I can paste into Slack. Keep it factual and include next steps."

Step 4: Save back with Agent Mode approvals

This is where SystemSculpt pays off:

  • It proposes exact edits
  • You review diffs
  • You approve changes before anything is written

Failure modes + fixes

  • Failure mode: Action items are listed without clear owners. Fix: Require one owner name per item and reject anonymous tasks.
  • Failure mode: Recap includes invented due dates. Fix: Add "if date is missing, mark as TBD" in your extraction prompt.
  • Failure mode: Discussion noise gets mixed with final decisions. Fix: Keep Decisions and Open questions as separate sections before approval.

Definition of done

A meeting note pass is complete when:

  • Each action item has an owner and clear definition of done.
  • Decisions are separated from discussion noise.
  • Open questions are tracked in one section, not hidden in transcript text.

Next step based on your intent

If you want a reusable structure, start with the Obsidian Meeting Notes Template.

Related workflows

Get new workflows by email

Monthly workflow drops, release notes, and tips. No spam.

Try SystemSculpt

SystemSculpt runs workflows inside Obsidian with approvals, semantic search, and streaming chat.