granola-reference-architecture

Granola Reference Architecture

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "granola-reference-architecture" with this command: npx skills add jeremylongshore/claude-code-plugins-plus-skills/jeremylongshore-claude-code-plugins-plus-skills-granola-reference-architecture

Granola Reference Architecture

Contents

  • Overview

  • Prerequisites

  • Instructions

  • Output

  • Error Handling

  • Examples

  • Resources

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

  • Granola Enterprise

  • Security Whitepaper

  • Architecture Guide

Next Steps

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

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

backtesting-trading-strategies

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

svg-icon-generator

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

performance-lighthouse-runner

No summary provided by upstream source.

Repository SourceNeeds Review