How Universal Meeting Prep Researches Every Attendee
The Problem
Your team runs this workflow every week: pull records from Google Calendar, Notion, cross-reference with a second source, apply judgment, format the output, and route it to 3 different stakeholders. Last Tuesday it took 30–60 minutes per cycle. This Tuesday the person who usually runs it is out sick, and nobody else knows the exact steps. The output varies by who runs it and when.
The core issue is data fragmentation. The information exists, but assembling it into actionable intelligence requires manual effort that does not scale with headcount. Universal Meeting Prep closes that gap by automating the meeting prep workflow from data extraction through structured output delivery.
Teams typically spend 30–60 minutes per cycle on the manual version of this workflow. Universal Meeting Prep reduces that to seconds per execution, with consistent quality every time.
What This Blueprint Does
Two Agents. Per-Attendee Research. Notion Brief Before You Walk In.
The Universal Meeting Prep pipeline runs 4 agents in sequence. The Researcher pulls data from Google Calendar and Notion, and The Syncer delivers the output. Here is what happens at each stage and why it matters.
- The Researcher (Tier 2 Reasoning): Runs once per attendee.
- The Analyst (Tier 1 Reasoning): Synthesizes all attendee research into a structured meeting intelligence brief.
- The Formatter (Code Only): Converts the structured analysis into Notion block format.
- The Syncer (HTTP): Creates the Notion page in your target database.
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
- Google Calendar polling — detects meetings 30 minutes before they start
- Per-attendee web research with up to 3 searches per person
- 6 meeting type classifications: sales, vendor, partnership, internal, interview, customer success
- 7-section Notion brief: Overview, Attendee Intel, Power Dynamics, Questions, Risk Flags, Outcome, Agenda Gaps
- Cost scales with attendees: ~$0.12 (1) to ~$0.37 (3) per meeting
- Built-in deduplication — same meeting never triggers twice
- Full ITP test results with 20 fixtures and cost analysis
- BQS-certified (12/12 PASS)
All scoring criteria, output formats, and routing rules are configurable in the system prompts — no workflow JSON edits required. This means Universal Meeting Prep adapts to your specific process, terminology, and integration requirements without forking the entire workflow.
Every component in this pipeline is designed for customization. Modify system prompts to change scoring logic, output format, or routing rules — no code changes required.
How the Pipeline Works
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 Universal Meeting Prep execution flow.
Step 1: The Researcher
Tier: Tier 2 Reasoning
The pipeline starts here. Runs once per attendee. Web research on seniority, company context, recent news, and LinkedIn signals. Up to 3 web searches per person. the analysis model.
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: The Analyst
Tier: Tier 1 Reasoning
Synthesizes all attendee research into a structured meeting intelligence brief. Classifies meeting type across 6 categories. Generates talking points, recommended questions, risk flags, and suggested outcomes. the primary reasoning model.
Why this step matters: This is where the pipeline applies judgment — not just data retrieval, but analysis.
Step 3: The Formatter
Tier: Code Only
Converts the structured analysis into Notion block format. Builds the 7-section intelligence page: Meeting Overview, Attendee Intelligence, Power Dynamics, Recommended Questions, Risk Flags, Suggested Outcome, Agenda Gaps. Zero LLM cost.
Every field in the output is structured for the next agent to consume without parsing.
Step 4: The Syncer
Tier: HTTP
This is the final deliverable — what lands in your inbox or dashboard. Creates the Notion page in your target database. Brief is delivered automatically — ready 30 minutes before the meeting starts. Non-blocking: if Notion fails, the intelligence data is still logged.
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.
This blueprint executes in your own n8n environment using your own API credentials. Zero external data sharing.
Why we designed it this way
7 of 20 fixtures had wrong expected values — the test author used simplified math instead of the pipeline's actual weighted formula. The fixtures said LUS 7, the pipeline correctly calculated LUS 6. We were debugging a "bug" that was actually correct behavior. Lesson: expected values must come from the same formula the pipeline uses.
— ForgeWorkflows Engineering
Cost Breakdown
Every metric is ITP-measured. Universal Meeting Prep researches attendees at $0.12–$0.37/meeting with dual LLM calls (the analysis modelresearch + the primary reasoning modelanalysis).
The primary operating cost for Universal Meeting Prep is the per-execution LLM inference cost. Based on Independent Test Protocol (ITP) testing, the measured cost is: Cost per Meeting: $0.12/meeting (1 att) | $0.27 (2 att) | $0.37 (3 att) — scales linearly with attendees. 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 an operations 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 $3–8/month, depending on your usage volume and plan tiers.
Quality assurance: Blueprint Quality Standard (BQS) audit result is 12/12 PASS. ITP result is 20/20 (100%) — U-01 through U-05, UMP-01 through UMP-09. 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.
Monthly projection: if you run this blueprint 100 times per month, multiply the per-execution cost by 100 and add your infrastructure costs. Most teams find the total is less than one hour of manual labor per month.
What's in the Bundle
9 files — everything you need to deploy the 22-node Universal Meeting Prep pipeline.
When you purchase Universal Meeting Prep, 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 historyREADME.md— Setup and configuration guideblueprint_dependency_matrix.md— Third-party service dependenciesmeeting_type_taxonomy.md— Meeting type taxonomynotion_page_template.md— Notion page templatesystem_prompt_analyst.txt— Analyst system promptsystem_prompt_researcher.txt— Researcher system promptuniversal_meeting_prep_v1_0_0.json— n8n workflow (main pipeline)
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.
Who This Is For
Universal Meeting Prep is built for 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 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 Calendar, Notion workspace
- You have API credentials available: Anthropic API, Google Calendar OAuth2, Notion API
- 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 work with calendars other than Google Calendar — no Outlook, Apple Calendar, or Calendly integration
- Does not deliver briefs outside Notion — no Slack, email, or Google Docs delivery
- Does not join or record meetings — it prepares intelligence before the meeting, not during
- Does not research attendees from internal domains — only external attendees get full web research
Review the dependency matrix and prerequisites before purchasing. If you are unsure whether your environment meets the requirements, contact support@forgeworkflows.com before buying.
All sales are final after download. Review the full dependency matrix, prerequisites, and integration requirements on the product page before purchasing. Questions? Contact support@forgeworkflows.com.
Edge cases to know about
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 work with calendars other than Google Calendar — no Outlook, Apple Calendar, or Calendly integration
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 deliver briefs outside Notion — no Slack, email, or Google Docs delivery
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 join or record meetings — it prepares intelligence before the meeting, not during
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.
The dead letter queue captures any records that fail processing. Check it after your first production run to validate data coverage.
Getting Started
Deployment follows a structured sequence. The Universal Meeting Prep bundle is designed for the following tools: n8n, Anthropic API, Google Calendar, Notion. Here is the recommended deployment path:
- Step 1: Import and configure credentials. Import universal_meeting_prep_v1_0_0.json into n8n. Configure your Anthropic API key, Google Calendar OAuth2 (calendar.readonly), and Notion integration token with database ID.
- Step 2: Configure calendar and Notion target. Set the Calendar ID (default: primary) and Notion database ID. The workflow polls every 15 minutes and delivers briefs 30 minutes before each meeting.
- Step 3: Activate and verify. Enable the workflow in n8n. Schedule a test meeting 45 minutes in the future with an external attendee. Verify the Notion brief appears with attendee research, meeting type classification, and recommended questions.
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 Universal Meeting Prep product page for full specifications, pricing, and purchase.
Run a manual test with sample data before switching to production triggers. This catches credential misconfigurations and API endpoint issues before they affect real workflows.
Frequently Asked Questions
How does the Google Calendar trigger work?+
The workflow polls your Google Calendar every 15 minutes. When it detects a meeting starting within the next 30–60 minutes, it fires automatically. No manual trigger needed — your brief is ready before you walk in. The system prompts are standalone text files — edit scoring thresholds and output formats without touching the workflow JSON.
What are the 6 meeting types?+
External Sales (prospect/customer calls), External Vendor (vendor evaluations), External Partnership (strategic partnerships, advisory boards), Internal (team syncs, 1:1s), Interview (hiring), and Customer Success (account reviews, onboarding). Intelligence adapts to each type. Check the dependency matrix in the bundle for exact version requirements and credential setup steps.
How does per-attendee research work?+
The Researcher runs once for each meeting attendee using Sonnet 4.6 with web_search. It gathers seniority, company context, recent news, and LinkedIn signals — up to 3 web searches per person. Results are assembled before the Analyst synthesizes. The README walks through configuration in under 10 minutes, including test data for validation.
What does the Notion brief contain?+
Seven sections: Meeting Overview (type, attendee count, agenda summary), Attendee Intelligence (per-person research profiles), Power Dynamics (seniority map, decision-maker identification), Recommended Questions (3–5, meeting-type-aware), Risk Flags (job changes, company news, gaps), Suggested Outcome, and Agenda Gaps. Review the error handling matrix in the bundle — it documents the recovery path for each failure mode.
How much does each meeting cost?+
ITP-measured: ~$0.12 for 1 attendee, ~$0.27 for 2, ~$0.37 for 3. Cost scales linearly because the Researcher runs once per attendee. A team processing 20 meetings/month with an average of 2 attendees spends ~$5.30/month. The ITP test results in the bundle show measured performance across edge cases, not just happy-path data.
Why two different LLM models?+
Sonnet 4.6 handles per-attendee research where speed and web search matter. Opus 4.6 handles the synthesis where reasoning depth matters — classifying meeting type, identifying power dynamics, and generating context-aware questions. This balances cost and intelligence quality. The system prompts are standalone text files — edit scoring thresholds and output formats without touching the workflow JSON.
Does the same meeting trigger twice?+
No. Built-in deduplication uses a 7-day window via n8n static data. Once a meeting has been processed, it will not trigger again even if the polling interval catches it multiple times. Check the dependency matrix in the bundle for exact version requirements and credential setup steps.
What calendar and delivery tools does this work with?+
Google Calendar for event source (OAuth2, calendar.readonly scope) and Notion for brief delivery (Integration token). It requires three credentials: Google Calendar OAuth2, Notion integration token, and Anthropic API key. The README walks through configuration in under 10 minutes, including test data for validation.
What should I do if the pipeline dead-letters a record?+
Check the dead letter output for the failure reason — the error context includes which agent failed and why. Common causes: missing input fields, API rate limits, or malformed data. Fix the underlying issue and reprocess. The error handling matrix in the bundle documents every failure mode and its recovery path.
Related Blueprints
Meeting Briefing Generator
Automated pre-meeting intelligence for every call on your calendar.
No-Show Predictor
AI scores no-show risk the moment a Calendly meeting is booked, then sends a personalized recovery email to high-risk prospects before they ghost.
Deal Intelligence Agent
Stop reviewing CRM updates. Let AI flag what matters.
RevOps Forecast Intelligence Agent
AI pulls your entire HubSpot pipeline every week, computes coverage ratio and deal velocity, and delivers a forecast brief with risks, focus areas, and rep leaderboard — to Notion and Slack.