Meeting Summary & Action Item Tracker
Send meeting transcripts via webhook to get AI-extracted summaries, prioritized action items, and automated updates across Slack.
What it does
Get clear meeting summaries and prioritized action items instantly by sending transcripts via webhook. You receive formatted updates directly in Slack and Notion while email owners get notified of their tasks. The system also sets calendar reminders for deadlines so you never miss a follow-up.
Step by step
- Set up a webhook endpoint to receive raw transcript payloads from the meeting platform.
- Configure the OpenAI API client with specific system prompts for extraction tasks.
- Implement logic to map extracted action items to user IDs in Slack and Notion.
Where the LLM does the work
- Generate concise executive summaries that capture key decisions without losing nuance.
- Assign priority scores based on context clues like urgency markers or stakeholder seniority.
- Draft personalized email notifications for task owners to ensure clear assignment communication.
Watch out for
Tools that fit
The agent brief
You are helping me build the following AI agent workflow. ## Goal Meeting Summary & Action Item Tracker: Send meeting transcripts via webhook to get AI-extracted summaries, prioritized action items, and automated updates across Slack. ## Specification - What it does: Get clear meeting summaries and prioritized action items instantly by sending transcripts via webhook. You receive formatted updates directly in Slack and Notion while email owners get notified of their tasks. The system also sets calendar reminders for deadlines so you never miss a follow-up. - Trigger: Triggered by an event (Webhook · on meeting transcript) - Autonomy: Fully hands-off - Expected setup effort: about an afternoon - Tools/services involved: - OpenAI: Transcript analysis and extraction - Slack: Posting summaries and notifications - Notion: Storing meeting notes and tasks - Gmail: Sending email notifications to owners - Google Calendar: Creating due date reminders ## Known pitfalls, handle each one explicitly in your implementation 1. Transcript length may exceed token limits so split the input into chunks before sending to the API. 2. Slack user IDs change over time so verify identity mapping against your directory regularly. 3. Notion database schemas must match exactly or the integration will fail silently on write operations. 4. OpenAI costs can spike with long transcripts so implement a token budget check before processing. ## Reference implementation https://n8n.io/workflows/10286 (workflow template) Fetch and inspect this before building. If it matches my stack, adapt it; if not, rebuild the pattern with my tools. ## Process requirements 1. Before building: ask me which of the listed tools I actually use and what my platform is (n8n / Make / code / other). Do not assume. 2. Adapt the pattern to my answers; do not force the reference stack. 3. Address every pitfall above; tell me how you handled each. 4. Provide a test plan I can run before letting this touch real data. 5. Ask before any step that sends messages, modifies data, or spends money. Source: https://usecasesforagents.com/use-case/automated-meeting-summary-action-item-tracker/ via usecasesforagents.com
Frequently asked questions
Can I use a different LLM than OpenAI?
Yes. OpenAI is only the example LLM in this recipe. The same flow works with Anthropic, Cohere, DeepSeek and Google Gemini. Swap the LLM connection and keep the rest of the setup as written.
Want this running in your business?
Who it's for
Built for Ops-IT teams who need one more recurring task off a human's plate.
Developers can adapt this to their own repo or ticket queue with the same trigger and tools.