Automated Meeting Notes & Action Items

Turn any meeting transcript into structured notes with decisions and action items, and automatically create tasks in your project management tool.

OpenClaw Hermes Intermediate Copied: 0
1 resource

Requirements

  • A Jira, Linear, Todoist, or Notion integration for task creation.
  • A Slack or Discord integration for posting summaries.
  • File system access is needed when reading transcript files; pasting a transcript directly into chat does not require it.
  • Scheduling / cron is needed only for the optional follow-up reminders or automated folder-watch pipeline.
  • Optional: Otter.ai, Fireflies.ai, or Google Meet API for automatic transcript retrieval.

How to use

VTT/SRT subtitle files from Zoom or Google Meet work great as input — they include timestamps which help the agent attribute statements to speakers.

Start simple (paste transcript, get summary) and automate incrementally. Don't over-engineer the pipeline before validating the output quality.

  1. Choose your transcript source. The simplest approach is pasting the transcript directly into chat. For automation, set up a folder watch or API integration.
  2. Prompt OpenClaw:
I just finished a meeting. Here's the transcript:

[paste transcript or point to file]

Please:
1. Write a concise summary (max 5 bullet points) covering key decisions and topics.
2. Extract ALL action items. For each one, identify:
   - What needs to be done
   - Who is responsible (match names to my team)
   - Deadline (if mentioned, otherwise mark as "TBD")
3. Create a Jira ticket for each action item, assigned to the right person.
4. Post the full summary to #meeting-notes in Slack.

  1. For fully automated pipeline (transcript folder watch):
Set up a recurring task: every 30 minutes, check ~/meeting-transcripts/ for
new .txt or .vtt files. When you find one:

1. Parse the transcript into a structured summary with action items.
2. Create tasks in Linear for each action item.
3. Post the summary to #team-updates in Slack.
4. Move the processed file to ~/meeting-transcripts/processed/.

For each action item with a deadline, set a reminder to ping the assignee
in Slack one day before it's due.

  1. Customize the output format:
When writing meeting summaries, always use this structure:
- **Date & Attendees** at the top
- **Key Decisions** — numbered list of what was decided
- **Action Items** — table with columns: Task, Owner, Deadline, Status
- **Open Questions** — anything unresolved that needs follow-up

Links

Source: hesamsheikh/awesome-openclaw-usecases and its contributors. License: MIT.

Copyright (c) 2026

Translation and editorial adaptation by ClawCases.

>Resources

>Related Use Cases

>More at this level: Intermediate