AgentSkillsCN

granola-reference-architecture

企业会议工作流架构,使用Granola。 在设计企业部署、规划集成或架构会议管理系统时使用。 可通过“granola architecture”、“granola enterprise”、“granola system design”、“meeting system”、“granola infrastructure”等短语触发。

SKILL.md
--- frontmatter
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

code
┌─────────────────────────────────────────────────────────────────┐
│                      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

PlatformRoleIntegration
Google MeetVideo conferencingCalendar sync
ZoomVideo conferencingCalendar sync
Microsoft TeamsVideo conferencingOutlook sync

Tier 2: Granola (Core)

FunctionDescription
Audio CaptureLocal device recording
TranscriptionReal-time speech-to-text
SummarizationAI-generated meeting notes
Template EngineStructured note formats

Tier 3: Middleware (Zapier)

FunctionDescription
Event RoutingDirect notes to appropriate systems
Data TransformFormat notes for target systems
FilteringRoute based on meeting type
OrchestrationMulti-step workflows

Tier 4: Destination Systems

SystemPurposeData Flow
SlackNotificationsSummary + actions
NotionDocumentationFull notes
HubSpotCRMContact updates
LinearTasksAction items
AnalyticsInsightsMetrics

Data Flow Patterns

Pattern 1: Standard Meeting

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

Pattern 2: Client Meeting

code
Meeting 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

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

Enterprise Deployment

Multi-Workspace Architecture

code
Enterprise 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

WorkspaceVisibilitySharingSSO Group
CorporatePrivateExecutive onlyexec-team
EngineeringTeamEngineering + PMengineering
SalesTeam + CRMSales + Successsales
HRConfidentialHR onlyhr-team

Integration Per Workspace

yaml
Corporate:
  - 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

Data TypeClassificationHandling
TranscriptsConfidentialEncrypted, access-controlled
SummariesInternalTeam-shared
Action ItemsInternalPublic within org
Attendee NamesPIIGDPR compliant

Encryption & Access

code
Data 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

Team SizeMeetings/MonthStorage/YearPlan
1-10100-5005-25 GBPro
10-50500-250025-125 GBBusiness
50-2002500-10000125-500 GBEnterprise
200+10000+500+ GBEnterprise+

Performance Budgets

MetricTargetMeasurement
Note availability< 3 minPost-meeting
Integration latency< 1 minZapier to destination
Search response< 500 msWithin Granola
Export time< 30 secFor any meeting

Disaster Recovery

Backup Strategy

markdown
Primary: 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

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

Resources

Next Steps

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