Granola Reference Architecture
Contents
Overview
Enterprise reference architecture for meeting management using Granola as the core capture platform with Zapier middleware routing to Slack, Notion, CRM, and task management.
Prerequisites
- Granola Business or Enterprise plan
- Zapier account for middleware automation
- Destination systems configured (Slack, Notion, CRM, Linear)
Instructions
Step 1: Set Up Core Pipeline
Meeting Platforms (Google/Zoom/Teams) -> Granola (capture/transcribe/summarize) -> Zapier (route/transform) -> Destinations (Slack, Notion, CRM, Linear)
Step 2: Configure Data Flow Patterns
- Standard: Parallel notify (Slack) + archive (Notion) + create tasks (Linear)
- Client Meeting: Add CRM path (HubSpot note, contact update, follow-up)
- Executive: Private Notion, EA notification, no public Slack
Step 3: Design Multi-Workspace Structure
Separate workspaces per department with appropriate access controls and per-workspace integrations.
Step 4: Implement Security
Data classification (Confidential/Internal/PII), encryption (AES-256/TLS 1.3), RBAC + SSO, audit logging.
Step 5: Plan for Scale and DR
Size workspace by team (Pro/Business/Enterprise), set performance budgets, configure nightly exports for disaster recovery.
See detailed implementation for full architecture diagram, data flow patterns, workspace configurations, access control matrices, and disaster recovery procedures.
Output
- Meeting ecosystem architecture documented
- Zapier routing configured per meeting type
- Multi-workspace structure deployed
- Security and DR measures in place
Error Handling
| Error |
Cause |
Solution |
| Notes not routing |
Zapier trigger misconfigured |
Verify Granola-Zapier connection |
| Wrong destination |
Filter logic error |
Review Zapier filter conditions |
| Slow note delivery |
Processing queue |
Check Granola status page |
| Missing CRM update |
External attendee not detected |
Verify calendar attendee emails |
Examples
Performance Targets
| Metric |
Target |
| Note availability |
< 3 min post-meeting |
| Integration latency |
< 1 min |
| Search response |
< 500 ms |
Resources
Next Steps
Proceed to granola-multi-env-setup for multi-environment configuration.
1---2name: granola-reference-architecture3description: |4 Enterprise meeting workflow architecture with Granola.5 Use when designing enterprise deployments, planning integrations,6 or architecting meeting management systems.7 Trigger with phrases like "granola architecture", "granola enterprise",8 "granola system design", "meeting system", "granola infrastructure".9allowed-tools: Read, Write, Edit10version: 1.0.011license: MIT12author: Jeremy Longshore <jeremy@intentsolutions.io>13compatible-with: claude-code, codex, openclaw14metadata:15 source: https://skillmd.com/skills/micsapp/granola-reference-architecture16---1718# Granola Reference Architecture1920## Contents21- [Overview](#overview)22- [Prerequisites](#prerequisites)23- [Instructions](#instructions)24- [Output](#output)25- [Error Handling](#error-handling)26- [Examples](#examples)27- [Resources](#resources)2829## Overview30Enterprise reference architecture for meeting management using Granola as the core capture platform with Zapier middleware routing to Slack, Notion, CRM, and task management.3132## Prerequisites33- Granola Business or Enterprise plan34- Zapier account for middleware automation35- Destination systems configured (Slack, Notion, CRM, Linear)3637## Instructions3839### Step 1: Set Up Core Pipeline40Meeting Platforms (Google/Zoom/Teams) -> Granola (capture/transcribe/summarize) -> Zapier (route/transform) -> Destinations (Slack, Notion, CRM, Linear)4142### Step 2: Configure Data Flow Patterns43- **Standard**: Parallel notify (Slack) + archive (Notion) + create tasks (Linear)44- **Client Meeting**: Add CRM path (HubSpot note, contact update, follow-up)45- **Executive**: Private Notion, EA notification, no public Slack4647### Step 3: Design Multi-Workspace Structure48Separate workspaces per department with appropriate access controls and per-workspace integrations.4950### Step 4: Implement Security51Data classification (Confidential/Internal/PII), encryption (AES-256/TLS 1.3), RBAC + SSO, audit logging.5253### Step 5: Plan for Scale and DR54Size workspace by team (Pro/Business/Enterprise), set performance budgets, configure nightly exports for disaster recovery.5556See [detailed implementation](${CLAUDE_SKILL_DIR}/references/implementation.md) for full architecture diagram, data flow patterns, workspace configurations, access control matrices, and disaster recovery procedures.5758## Output59- Meeting ecosystem architecture documented60- Zapier routing configured per meeting type61- Multi-workspace structure deployed62- Security and DR measures in place6364## Error Handling65| Error | Cause | Solution |66|-------|-------|----------|67| Notes not routing | Zapier trigger misconfigured | Verify Granola-Zapier connection |68| Wrong destination | Filter logic error | Review Zapier filter conditions |69| Slow note delivery | Processing queue | Check Granola status page |70| Missing CRM update | External attendee not detected | Verify calendar attendee emails |7172## Examples7374### Performance Targets75| Metric | Target |76|--------|--------|77| Note availability | < 3 min post-meeting |78| Integration latency | < 1 min |79| Search response | < 500 ms |8081## Resources82- [Granola Enterprise](https://granola.ai/enterprise)83- [Security Whitepaper](https://granola.ai/security)84- [Architecture Guide](https://granola.ai/help/architecture)8586## Next Steps87Proceed to `granola-multi-env-setup` for multi-environment configuration.