Google Calendar Meeting Load Analyzer

AI-powered weekly team meeting load analysis — overload risk, deep work erosion, meeting bloat, schedule patterns, and capacity distribution scored per-person across 5 dimensions.

Analyzes Google Calendar events weekly across your team to compute per-person Calendar Health Scores. Identifies overloaded team members, eroded deep work time, bloated meetings, back-to-back chains, and uneven capacity distribution. Generates a Notion calendar health brief and Slack overload digest. 24-node n8n workflow with Monday scheduler. Blueprint Quality Standard (BQS) 12/12 certified. This came from a manager who felt his team was in too many meetings but had no data. The analyzer measures meeting load per person — total hours, fragmentation, recurring vs. ad-hoc — and flags when schedules cross healthy thresholds.

Last updated March 18, 2026

Knowledge workers spend 15-25 hours per week in meetings, with 30-60 minutes of prep per external meeting. Meeting notes live in personal documents, disconnected from the CRM and project management tools where decisions need to be tracked. Automated meeting intelligence eliminates prep time and ensures decisions reach the systems of record.

triggerSchedule01FetcherCalendar API02Assembler5 CHS Dims03AnalystLoad Scoring04FormatterBrief + DigestNotionHealth BriefSlackLoad Digest

Four Agents. Weekly Meeting Load Scoring. Per-Person Health.

The Fetcher

Step 1The Fetcher

Code-only

Retrieves calendar event data from Google Calendar API for all configured team members over the previous 7 days — event times, durations, attendee counts, recurring vs. one-off flags, and free/busy status. Pulls per-person event lists for individual load scoring.

The Assembler

Step 2The Assembler

Code-only

What does The Assembler actually decide? Computes 5 Calendar Health Score (CHS) dimensions per person: overload risk (total meeting hours vs. available hours), deep work erosion (longest uninterrupted block length), meeting bloat (average attendee count and duration trend), schedule patterns (morning vs. afternoon concentration, back-to-back chains), and capacity distribution (internal vs. external vs. recurring ratio).

The Analyst

Step 3The Analyst

Tier 2 Classification

This step exists because raw data alone is not enough. Scores each CHS dimension per person with evidence-based ratings. Identifies individuals at overload risk, flags teams with eroding deep work time, and surfaces systemic patterns like recurring meeting creep or back-to-back scheduling. Generates per-person health scorecards with prioritized recommendations.

The Formatter

Step 4The Formatter

Tier 3 Creative

Without this step, upstream analysis sits idle. Generates a Notion weekly meeting load brief with per-person scorecards, team-level CHS summary, and trend comparisons, plus a Slack digest with top 3 calendar health actions and at-risk individuals.A non-idempotent re-run turned a 32-node workflow into 44 nodes. Every build script now removes existing nodes before adding fresh ones.

That's the full pipeline. Here's what it intentionally does NOT do — and why those boundaries exist.

What It Does NOT Do

×

Does not create, modify, or delete calendar events — read-only analysis of existing events

×

Does not enforce meeting policies — it identifies overload and patterns for human decision-making

×

Does not integrate with meeting tools like Zoom or Teams — it analyzes calendar event metadata only

×

Does not provide real-time alerts — weekly batch analysis optimizes for actionable patterns over noise

×

Does not replace calendar management tools — it provides health scoring intelligence for team leads

With those boundaries clear, here's everything that ships when you purchase.

The Complete Customer Success Bundle

6 files.

google_calendar_meeting_load_analyzer_v1_0_0.jsonMain workflow (24 nodes)
google_calendar_meeting_load_analyzer_scheduler_v1_0_0.jsonScheduler workflow (3 nodes)
README.md10-minute setup guide
docs/TDD.mdTechnical Design Document
system_prompts/analyst_system_prompt.mdAnalyst prompt (calendar health scoring)
system_prompts/formatter_system_prompt.mdFormatter prompt (Notion + Slack)

The technical specifications below are ITP-measured, not estimated.

Tested. Measured. Documented.

Weekly meeting load analysis with per-person Calendar Health Scores across 5 dimensions, back-to-back chain detection, and deep work erosion tracking delivered via Notion and Slack.

Tested on n8n v2.7.5, March 2026

Google Calendar Meeting Load Analyzer v1.0.0──────────────────────────────────────────Nodes:        24 main + 3 scheduler (27 total)Agents:       4 (Fetcher, Assembler, Analyst, Formatter)LLM Calls:    2 per run (Analyst + Formatter)Model:        Sonnet 4.6 (SINGLE-MODEL)Trigger:      Schedule (weekly Monday 7:00 UTC) + WebhookPattern:      AGGREGATE (weekly meeting load analysis)Tool A:       Google Calendar API (OAuth2) — event data per team memberTool B:       Notion (httpHeaderAuth) — weekly meeting load briefTool C:       Slack (httpHeaderAuth) — digest with top 3 calendar health actionsITP:          8/8 records, 14/14 milestonesBQS:          12/12 PASSCost:         $0.03–$0.10 per run

What You'll Need

Platform

n8n 2.7.5+

Est. Monthly API Cost

Weekly cost ~$0.03-0.10/run (~$0.12-0.40/month)

Credentials Required

  • Anthropic API
  • Google Calendar (OAuth2)
  • Slack (Bot Token, httpHeaderAuth Bearer)
  • Notion (httpHeaderAuth Bearer)

Services

  • Google Calendar (Google Workspace with OAuth2)
  • Anthropic API key
  • Notion workspace
  • Slack workspace (Bot Token with chat:write)

Setup Track

Quick Start

~15 min

All credentials live, n8n running

Full Setup

1–2 hrs

Needs API config + tables

From Scratch

2–4 hrs

No n8n, no credentials

Google Calendar Meeting Load Analyzer v1.0.0

$199

one-time purchase

What you get:

  • ITP-tested n8n workflow (24 nodes + 3-node scheduler)
  • 5-dimension Calendar Health Score per person (overload risk, deep work erosion, meeting bloat, schedule patterns, capacity distribution)
  • Per-person scorecards with individual health ratings and coaching recommendations
  • Team-level CHS summary with week-over-week trend comparison
  • Back-to-back meeting chain detection and deep work block analysis
  • Internal vs. external vs. recurring meeting ratio breakdown
  • Notion weekly meeting load brief with full dimension analysis
  • Slack digest with top 3 calendar health actions and at-risk individuals
  • Configurable: team member list, overload thresholds, deep work minimum, lookback period
  • Full technical documentation and system prompts

Frequently Asked Questions

What are the 5 Calendar Health Score dimensions?+

Overload risk measures total meeting hours vs. available hours. Deep work erosion tracks the longest uninterrupted block.

How many team members can it analyze?+

The workflow processes all team members configured in the scheduler payload. Each member needs a Google Calendar accessible via the configured service account or OAuth2 credential. Typical deployments cover 5-50 team members.

Does it modify calendar events?+

No. This is a read-only analysis tool. It retrieves event data from Google Calendar API but never creates, modifies, or deletes any events.

Is there a refund policy?+

All sales are final after download. Review the Blueprint Dependency Matrix and prerequisites before purchase. Questions?

Read the full guide →

Related Blueprints