| name | granola-reference-architecture |
| description | Enterprise reference architecture for meeting management with Granola.
Use when designing org-wide meeting workflows, planning integration topology,
or architecting meeting-to-action pipelines across departments.
Trigger: "granola architecture", "granola enterprise design",
"granola system design", "meeting system architecture".
|
| allowed-tools | Read, Write, Edit |
| version | 1.13.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","granola","architecture","enterprise"] |
| compatibility | Designed for Claude Code, also compatible with Codex and OpenClaw |
Granola Reference Architecture
Overview
Enterprise reference architecture for deploying Granola as the meeting intelligence platform across an organization. Covers the core capture pipeline, Zapier middleware routing, multi-workspace topology, security layers, and integration patterns for Slack, Notion, CRM, and task management.
Prerequisites
- Granola Enterprise plan ($35+/user/month)
- Zapier Professional or higher (for multi-step Zaps and Paths)
- Destination systems provisioned (Slack, Notion, CRM, Linear/Jira)
- IT architecture review completed
Instructions
Step 1 — Core Pipeline Architecture
┌─────────────────────────────────────────────────────────┐
│ MEETING PLATFORMS │
│ Zoom | Google Meet | Microsoft Teams | Slack Huddle│
└──────────────────────┬──────────────────────────────────┘
│ System audio capture (no bot)
▼
┌─────────────────────────────────────────────────────────┐
│ GRANOLA PLATFORM │
│ │
│ ┌──────────┐ ┌──────────────┐ ┌─────────────────┐ │
│ │ Audio │→ │ Transcription │→ │ AI Enhancement │ │
│ │ Capture │ │ (GPT-4o/ │ │ (Notes + Trans- │ │
│ │ (local) │ │ Claude) │ │ cript merge) │ │
│ └──────────┘ └──────────────┘ └────────┬────────┘ │
│ │ │
│ ┌────────────────┐ ┌──────────────────┐ │ │
│ │ People & │ │ Folders │ │ │
│ │ Companies │ │ (routing rules) │←─┘ │
│ │ (built-in CRM) │ └────────┬─────────┘ │
│ └────────────────┘ │ │
└───────────────────────────────┼─────────────────────────┘
│
┌───────────────────┼───────────────────┐
│ ZAPIER MIDDLEWARE │
│ │
│ ┌─────────┐ ┌─────────┐ ┌──────┐ │
│ │ Filter │→ │ Route │→ │ Act │ │
│ │ (type/ │ │ (paths │ │ │ │
│ │ attendee)│ │ /rules) │ │ │ │
│ └─────────┘ └─────────┘ └──────┘ │
└──────┬──────────┬──────────┬─────────┘
│ │ │
┌──────────┴──┐ ┌────┴────┐ ┌───┴────────┐
│ COMMUNICATE │ │ ARCHIVE │ │ ACT │
│ Slack │ │ Notion │ │ Linear/Jira│
│ Email │ │ Drive │ │ Asana │
│ Teams │ │ GCS/S3 │ │ HubSpot │
└─────────────┘ └─────────┘ └────────────┘
Step 2 — Folder-Based Routing Topology
Design folder structure to drive automated routing:
