How Meeting Follow-Up Agent Automates Meeting Prep

automated post-meeting follow-ups with action items. That single sentence captures a workflow gap that costs sales, revops, operations teams hours every week. The manual process behind what Meeting Follow-Up Agent automates is familiar to anyone who has worked in a revenue organization: someone pulls data from Google Calendar, Gmail, Notion, copies it into a spreadsheet or CRM, applies a mental checklist, writes a summary, and routes it to the next person in the chain. Repeat for every record. Every day.

Three problems make this unsustainable at scale. First, the process does not scale. As volume grows, the human bottleneck becomes the constraint. Whether it is inbound leads, deal updates, or meeting prep, a person can only process a finite number of records before quality degrades. Second, the process is inconsistent. Different team members apply different criteria, use different formats, and make different judgment calls. There is no single standard of quality, and the output varies from person to person and day to day. Third, the process is slow. By the time a manual review is complete, the window for action may have already closed. Deals move, contacts change roles, and buying signals decay.

These are not theoretical concerns. They are the operational reality for sales, revops, operations teams handling meeting prep workflows. Every hour spent on manual data processing is an hour not spent on the work that actually moves the needle: building relationships, closing deals, and driving strategy.

This is the gap Meeting Follow-Up Agent fills.

Four Agents. Every Meeting. Action Items That Actually Get Done.

Meeting Follow-Up Agent is a multiple-node n8n workflow with 4 specialized agents. Each agent handles a distinct phase of the pipeline, and the handoff between agents is deterministic — no ambiguous routing, no dropped records. The blueprint is designed so that each agent does one thing well, and the overall pipeline produces a consistent, auditable output on every run.

Here is what each agent does:

• Fetcher (Code): Dual-trigger activation: scheduled poll of Google Calendar for recently ended meetings, or webhook for on-demand processing.
• Analyst (Tier 1 Reasoning): the analysis model analyzes the meeting content and extracts action items across 5 AIC categories: decision_made (key decisions captured), task_assigned (tasks with assigned owner), follow_up_required (items needing further action), question_unresolved (open questions not resolved), and escalation_needed (issues requiring escalation).
• Writer (Tier 2 Creative): the analysis model generates a professional follow-up email summarizing the meeting outcomes, listing action items by priority, and clearly assigning ownership.
• Deliverer (HTTP + Code): Non-blocking parallel writes to Gmail and Notion.

When the pipeline completes, you get structured output that is ready to act on. The blueprint bundle includes everything needed to deploy, configure, and customize the workflow. Specifically, you receive:

• Production-ready 22-node n8n workflow — import and deploy
• Automated action item extraction from every meeting
• 5-category AIC taxonomy: decisions, tasks, follow-ups, questions, escalations
• 3-level priority scoring with owner assignment for every item
• Professional follow-up emails sent via Gmail to all attendees
• Structured Notion action log for tracking and accountability
• the analysis model analysis at $0.035/meeting — 10 meetings/day costs $0.35
• Post-meeting complement to Universal Meeting Prep (before + after coverage)
• ITP test results with 20 records and 14/14 milestones

Every component is designed to be modified. The agent prompts are plain text files you can edit. The workflow nodes can be rearranged or extended. The scoring criteria, output formats, and routing logic are all exposed as configurable parameters — not buried in application code. This means Meeting Follow-Up Agent adapts to your specific process, terminology, and integration requirements without forking the entire workflow.

Understanding how the pipeline works helps you customize it for your environment and troubleshoot issues when they arise. Here is a step-by-step walkthrough of the Meeting Follow-Up Agent execution flow.

Step 1: Fetcher

Tier: Code

Dual-trigger activation: scheduled poll of Google Calendar for recently ended meetings, or webhook for on-demand processing. Fetches event metadata, attendee list, and any attached notes or transcript data. Normalizes input from both trigger paths into a unified meeting record.

This stage is critical because it ensures that downstream agents receive structured, validated input. Each agent in the pipeline trusts the output contract of the previous agent. If Fetcher identifies an issue — a missing field, a low-confidence score, or an unexpected input format — the pipeline handles it explicitly rather than passing garbage downstream. This is the difference between a prototype and a production-grade workflow: every handoff is defined, every edge case is documented.

Step 2: Analyst

Tier: Tier 1 Reasoning

the analysis model analyzes the meeting content and extracts action items across 5 AIC categories: decision_made (key decisions captured), task_assigned (tasks with assigned owner), follow_up_required (items needing further action), question_unresolved (open questions not resolved), and escalation_needed (issues requiring escalation). Each item gets a 3-level priority score and assigned owner.

This stage is critical because it ensures that downstream agents receive structured, validated input. Each agent in the pipeline trusts the output contract of the previous agent. If Analyst identifies an issue — a missing field, a low-confidence score, or an unexpected input format — the pipeline handles it explicitly rather than passing garbage downstream. This is the difference between a prototype and a production-grade workflow: every handoff is defined, every edge case is documented.

Step 3: Writer

Tier: Tier 2 Creative

the analysis model generates a professional follow-up email summarizing the meeting outcomes, listing action items by priority, and clearly assigning ownership. The email is formatted for immediate sending — no manual editing required. Tone adapts based on meeting type (internal standup vs. client call vs. executive review).

This stage is critical because it ensures that downstream agents receive structured, validated input. Each agent in the pipeline trusts the output contract of the previous agent. If Writer identifies an issue — a missing field, a low-confidence score, or an unexpected input format — the pipeline handles it explicitly rather than passing garbage downstream. This is the difference between a prototype and a production-grade workflow: every handoff is defined, every edge case is documented.

Step 4: Deliverer

Tier: HTTP + Code

Non-blocking parallel writes to Gmail and Notion. Gmail receives the follow-up email addressed to all meeting attendees. Notion receives a structured action item log with the full AIC breakdown, priority assignments, and owner mapping. Both writes execute simultaneously — if one fails, the other completes independently.

This stage is critical because it ensures that downstream agents receive structured, validated input. Each agent in the pipeline trusts the output contract of the previous agent. If Deliverer identifies an issue — a missing field, a low-confidence score, or an unexpected input format — the pipeline handles it explicitly rather than passing garbage downstream. This is the difference between a prototype and a production-grade workflow: every handoff is defined, every edge case is documented.

The entire pipeline executes without manual intervention. From trigger to output, every decision point is deterministic: if a condition is met, the next agent fires; if not, the record is handled according to a documented fallback path. There are no silent failures. Every execution produces a traceable audit trail that you can review, export, or feed into your own reporting tools.

This architecture follows the ForgeWorkflows principle of tested, measured, documented automation. Every node in the pipeline has been validated during ITP (Inspection and Test Plan) testing, and the error handling matrix in the bundle documents the recovery path for each failure mode.

Every metric is ITP-measured. The Meeting Follow-Up Agent extracts action items from every meeting, assigns ownership and priority, and delivers professional follow-up emails with Notion documentation at $0.035/meeting.

The primary operating cost for Meeting Follow-Up Agent is the per-execution LLM inference cost. Based on ITP testing, the measured cost is: Cost per Meeting: $0.035/meeting (ITP-measured average). This figure includes all API calls across all agents in the pipeline — not just the primary reasoning step, but every classification, scoring, and output generation call.

To put this in context, consider the manual alternative. A skilled team member performing the same work manually costs $50–75/hour at a fully loaded rate (salary, benefits, tools, overhead). If the manual version of this workflow takes 20–40 minutes per cycle, that is $17–50 per execution in human labor. The blueprint executes the same pipeline for a fraction of that cost, with consistent quality and zero fatigue degradation.

Infrastructure costs are separate from per-execution LLM costs. You will need an n8n instance (self-hosted or cloud) and active accounts for the integrated services. The estimated monthly infrastructure cost is <$8/month (10 meetings/day), depending on your usage volume and plan tiers.

Quality assurance: BQS audit result is 12/12 PASS. ITP result is 20 records, 14/14 milestones PASS. These are not marketing claims — they are test results from structured inspection protocols that you can review in the product documentation.

9 files — workflow JSON, system prompts, configuration guides, and complete documentation.

When you purchase Meeting Follow-Up Agent, you receive a complete deployment bundle. This is not a SaaS subscription or a hosted service — it is a set of files that you own and run on your own infrastructure. Here is what is included:

• meeting_follow_up_agent_v1_0_0.json — The 22-node n8n workflow
• README.md — 10-minute setup guide with Google Calendar, Gmail, and Notion configuration
• system_prompt_analyst.txt — Analyst system prompt (5-category AIC taxonomy, priority scoring)
• system_prompt_writer.txt — Writer system prompt (follow-up email generation, tone adaptation)
• google_workspace_setup_guide.md — Google Calendar + Gmail OAuth2 scopes and configuration
• notion_setup_guide.md — Notion API integration token and database setup
• aic_taxonomy_reference.md — 5-category AIC taxonomy definitions and examples
• itp_results.md — ITP test results — 20 records, 14/14 milestones
• CHANGELOG.md — Version history

Start with the README.md. It walks through the deployment process step by step, from importing the workflow JSON into n8n to configuring credentials and running your first test execution. The dependency matrix lists every required service, API key, and estimated cost so you know exactly what you need before you start.

Every file in the bundle is designed to be read, understood, and modified. There is no obfuscated code, no compiled binaries, and no phone-home telemetry. You get the source, you own the source, and you control the execution environment.

Meeting Follow-Up Agent is built for Sales, Revops, Operations teams that need to automate a specific workflow without building from scratch. If your team matches the following profile, this blueprint is designed for you:

• You operate in a sales or revops or operations function and handle the workflow this blueprint automates on a recurring basis
• You have (or are willing to set up) an n8n instance — self-hosted or cloud
• You have active accounts for the required integrations: Google Workspace (Calendar + Gmail), Notion workspace
• You have API credentials available: Anthropic API, Google Calendar OAuth2, Gmail OAuth2, Notion Internal Integration
• You are comfortable importing a workflow JSON and configuring API keys (the README guides you, but basic technical comfort is expected)

This is NOT for you if:

• Does not transcribe meetings — requires existing notes, transcript, or summary data as input
• Does not record audio or video — processes text-based meeting content only
• Does not replace project management tools — creates action items in Notion, not Jira or Asana
• Does not work with Microsoft 365 — Google Workspace only (Calendar + Gmail)
• Does not send Slack notifications — delivers via Gmail and Notion only

Review the dependency matrix and prerequisites before purchasing. If you are unsure whether your environment meets the requirements, contact support@forgeworkflows.com before buying.

Deployment follows a structured sequence. The Meeting Follow-Up Agent bundle is designed for the following tools: n8n, Anthropic API, Google Calendar, Gmail, Notion. Here is the recommended deployment path:

1. Step 1: Import workflow and configure credentials. Import meeting_follow_up_agent_v1_0_0.json into n8n. Configure Google Calendar OAuth2 (with calendar.readonly scope), Gmail OAuth2 (with gmail.send scope), Notion API integration token, and Anthropic API key.
2. Step 2: Configure calendar and Notion settings. Set the target Google Calendar ID for monitoring. Configure the Notion database for action item logging. Review the AIC taxonomy reference for category definitions and priority levels.
3. Step 3: Activate and verify. Enable the workflow in n8n. Run manually for your most recent meeting. Verify the follow-up email is sent to attendees and the Notion action log is created with categorized items.

Before running the pipeline on live data, execute a manual test run with sample input. This validates that all credentials are configured correctly, all API endpoints are reachable, and the output format matches your expectations. The README includes test data examples for this purpose.

Once the test run passes, you can configure the trigger for production use (scheduled, webhook, or event-driven — depending on the blueprint design). Monitor the first few production runs to confirm the pipeline handles real-world data as expected, then let it run.

For technical background on how ForgeWorkflows blueprints are built and tested, see the Blueprint Quality Standard (BQS) methodology and the Inspection and Test Plan (ITP) framework. These documents describe the quality gates every blueprint passes before listing.

Ready to deploy? View the Meeting Follow-Up Agent product page for full specifications, pricing, and purchase.