How Meeting Follow-Up Agent Generates Post-Call Actions

Your sales team has 47 deals in the proposal stage. 12 have not had contact in 5+ days. Three have gone completely dark. Which ones are at risk — and which ones just have a slow procurement process? A rep answering this question manually checks Google Calendar, Gmail, Notion, cross-references email history, and makes a judgment call on each deal. At 15 minutes per deal, that is 30–60 minutes per cycle of triage before any follow-up happens.

The cost is not just time — it is revenue leakage. Deals slip because signals were missed. Pipeline reviews rely on data that was accurate two days ago. Scoring criteria drift between team members, and the CRM becomes a lagging indicator rather than an operational tool. Meeting Follow-Up Agent automates the meeting prep workflow from data extraction through analysis to structured output, with zero manual CRM entry.

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

The Meeting Follow-Up Agent pipeline runs 4 agents in sequence. Fetcher pulls data from Google Calendar and Gmail and Notion, and Deliverer delivers the output. Here is what happens at each stage and why it matters.

• 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:

• ITP-tested 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

Scoring thresholds, output destinations, and CRM field mappings are configurable in the system prompts — no workflow JSON edits required. 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

The pipeline starts here. 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 ensures all downstream agents receive clean, validated input. If this step returns incomplete data, every downstream agent works with a degraded picture.

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.

Why this step matters: This is where the pipeline applies judgment — not just data retrieval, but analysis.

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).

Every field in the output is structured for the next agent to consume without parsing.

Step 4: Deliverer

Tier: HTTP + Code

This is the final deliverable — what lands in your inbox or dashboard. 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.

The entire pipeline executes without manual intervention. From trigger to output, every decision point follows a documented path. Every execution produces a traceable audit trail.

All nodes have been validated during Independent Test Protocol (ITP) testing on n8n v2.7.5. The error handling matrix in the bundle documents the recovery path for each failure mode.

Ghost contacts, rebranded companies, missing fields — that is what ITP fixtures contain. A 524-day inactive contact is now a standard test case. You do not find out if error handling works by testing happy paths. You find out by throwing data that should not exist and verifying the pipeline does not crash.

— ForgeWorkflows Engineering

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 Independent Test Protocol (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 for a sales ops analyst at a fully loaded rate (salary, benefits, tools, overhead). If the manual version of this workflow takes 30–60 minutes per cycle, the per-execution cost in human labor is significant. 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: Blueprint Quality Standard (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.

All cost and performance figures are ITP-measured — tested against real data fixtures on n8n v2.7.5 in March 2026. See the product page for full test methodology.

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:

• CHANGELOG.md — Version history
• README.md — Setup and configuration guide
• docs/TDD.md — Technical Design Document
• meeting_follow_up_agent_v1.0.0.json — n8n workflow (main pipeline)
• system_prompts/analyst_system_prompt.md — Analyst system prompt
• system_prompts/writer_system_prompt.md — Writer system prompt

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.

Every pipeline has boundaries. These are intentional design decisions, not oversights — understanding them helps you deploy with the right expectations and plan for edge cases in your environment.

Does not transcribe meetings — requires existing notes, transcript, or summary data as input

This is intentional. We default to human-in-the-loop for actions that carry reputational or financial risk. Once your team has validated output accuracy over 20+ cycles, you can adjust the pipeline to auto-execute — the workflow JSON supports it, but the default is conservative.

Does not record audio or video — processes text-based meeting content only

We scoped this boundary after ITP testing revealed inconsistent results when the pipeline attempted this. The agents handle what they handle well — extending beyond this scope requires custom prompt engineering specific to your data shape.

Does not replace project management tools — creates action items in Notion, not Jira or Asana

This keeps the pipeline focused on a single workflow. Adding this capability would introduce branching logic that varies by organization, and the tradeoff between complexity and reliability was not worth it for a reusable blueprint. Fork the workflow JSON if your use case demands it.

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.