---

name: granola-reference-architecture description: | Enterprise meeting workflow architecture with Granola. Use when designing enterprise deployments, planning integrations, or architecting meeting management systems. Trigger with phrases like "granola architecture", "granola enterprise", "granola system design", "meeting system", "granola infrastructure". allowed-tools: Read, Write, Edit version: 1.0.0 license: MIT author: Jeremy Longshore jeremy@intentsolutions.io

Granola Reference Architecture

Overview

Enterprise reference architecture for meeting management using Granola as the core capture platform.

Architecture Diagram

Copy┌─────────────────────────────────────────────────────────────────┐
│                      MEETING ECOSYSTEM                           │
├─────────────────────────────────────────────────────────────────┤
│                                                                  │
│  ┌─────────────┐    ┌─────────────┐    ┌─────────────┐         │
│  │   Google    │    │   Zoom      │    │   Teams     │         │
│  │  Calendar   │    │             │    │             │         │
│  └──────┬──────┘    └──────┬──────┘    └──────┬──────┘         │
│         │                  │                  │                 │
│         └─────────────────┬┴─────────────────┘                 │
│                           │                                     │
│                    ┌──────▼──────┐                              │
│                    │   GRANOLA   │                              │
│                    │   (Core)    │                              │
│                    │             │                              │
│                    │ • Capture   │                              │
│                    │ • Transcribe│                              │
│                    │ • Summarize │                              │
│                    └──────┬──────┘                              │
│                           │                                     │
│                    ┌──────▼──────┐                              │
│                    │   ZAPIER    │                              │
│                    │ (Middleware)│                              │
│                    └──────┬──────┘                              │
│                           │                                     │
│    ┌──────────┬───────────┼───────────┬──────────┐             │
│    │          │           │           │          │             │
│    ▼          ▼           ▼           ▼          ▼             │
│ ┌──────┐ ┌───────┐ ┌─────────┐ ┌────────┐ ┌──────────┐        │
│ │Slack │ │Notion │ │HubSpot  │ │ Linear │ │Analytics │        │
│ │      │ │       │ │(CRM)    │ │(Tasks) │ │  (BI)    │        │
│ └──────┘ └───────┘ └─────────┘ └────────┘ └──────────┘        │
│                                                                  │
└─────────────────────────────────────────────────────────────────┘

Component Responsibilities

Tier 1: Meeting Platforms

Tier 2: Granola (Core)

Tier 3: Middleware (Zapier)

Tier 4: Destination Systems

Data Flow Patterns

Pattern 1: Standard Meeting

CopyMeeting Ends
     ↓
Granola Processes (2 min)
     ↓
Zapier Trigger
     ↓
┌────────────────────┐
│ Parallel Actions   │
├────────────────────┤
│ → Slack notify     │
│ → Notion archive   │
│ → Linear tasks     │
└────────────────────┘

Pattern 2: Client Meeting

CopyMeeting Ends (external attendee detected)
     ↓
Granola Processes
     ↓
Zapier Trigger + Filter
     ↓
┌────────────────────┐
│ CRM Path           │
├────────────────────┤
│ → HubSpot note     │
│ → Contact update   │
│ → Deal activity    │
│ → Follow-up task   │
└────────────────────┘
     +
┌────────────────────┐
│ Standard Path      │
├────────────────────┤
│ → Notion archive   │
│ → Slack notify     │
└────────────────────┘

Pattern 3: Executive Meeting

CopyMeeting Ends (VP+ attendee)
     ↓
Granola Processes
     ↓
Special Handling:
     ↓
┌────────────────────┐
│ High-Touch Path    │
├────────────────────┤
│ → Private Notion   │
│ → EA notification  │
│ → Action tracking  │
│ → No public Slack  │
└────────────────────┘

Enterprise Deployment

Multi-Workspace Architecture

CopyEnterprise Granola Deployment
├── Corporate Workspace
│   ├── Executive Team
│   ├── Leadership
│   └── Board Meetings
├── Engineering Workspace
│   ├── Sprint Planning
│   ├── Tech Reviews
│   └── Team Syncs
├── Sales Workspace
│   ├── Client Calls
│   ├── Demos
│   └── QBRs
└── HR Workspace
    ├── Interviews
    ├── Reviews
    └── Training

Access Control Matrix

Integration Per Workspace

CopyCorporate:
  - Notion (private database)
  - Slack (#exec-team private)
  - No CRM

Engineering:
  - Notion (engineering wiki)
  - Slack (#dev-meetings)
  - Linear (auto-tasks)
  - GitHub (PR references)

Sales:
  - Notion (sales playbook)
  - Slack (#sales-updates)
  - HubSpot (full sync)
  - Gong (call coaching)

HR:
  - Notion (confidential)
  - Slack (HR DMs only)
  - Greenhouse (if recruiting)

Security Architecture

Data Classification

Encryption & Access

CopyData at Rest: AES-256
Data in Transit: TLS 1.3
Access Control: RBAC + SSO
Audit: Full logging enabled
Retention: Configurable per workspace

Scalability Considerations

Volume Planning

Performance Budgets

Disaster Recovery

Backup Strategy

CopyPrimary: Granola cloud storage
Secondary: Nightly export to company storage
Tertiary: Weekly archive to cold storage

Recovery Points:
- RPO: 24 hours (daily export)
- RTO: 4 hours (restore from export)

Failover Procedures

CopyIf Granola unavailable:
1. Manual notes during meeting
2. Record with backup tool
3. Transcribe post-meeting
4. Manual upload when restored

Resources

• Granola Enterprise
• Security Whitepaper
• Architecture Guide

Next Steps

Proceed to granola-multi-env-setup for multi-environment configuration.