Agent skill · product strategy · jeremylongshore
granola-reference-architecture
Enterprise reference architecture for meeting management with Granola.
Why this skill is useful
Provides specific architectural patterns and integration workflows for deploying Granola in enterprise environments that the AI wouldn't reliably generate on its own.
What it needs
Requires granola, zapier account access. About 5k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
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 Step 2 — Folder-Based Routing Topology Design folder structure to drive automated routing: Folder Trigger Type Destinations Permissions -------- ------------- ------------- ------------- Sales / Discovery Auto Slack #sales + HubSpot Deal + Follow-up Email Sales team Sales / Demo Auto Slack #sales + HubSpot Contact Sales team Engineering / Sprint Auto Slack #eng + Linear tasks + Notion wiki Engineering Engineering / Architecture Auto Slack #eng-arch + Notion ADR database Senior engineers Product / Customer Feedback Auto Slack #product + Notion feedback DB Product team Leadership / All-Hands Auto Slack #general + Google Drive archive All Leadership / Board Manual only Private Notion, no Slack Executives only HR / Interviews Manual share Greenhouse scorecard Hiring managers HR / 1-on-1s None Private, no automation Individual Step 3 — Multi-Workspace Topology Step 4 — Security Architecture Step 5 — Integration Data Flow Patterns Pattern A: Standard Meeting (Parallel) Pattern B: Sales Meeting (Sequential) Pattern C: Executive Meeting (Restricted) Step 6 — Disaster Recovery & Data Export Output Complete meeting ecosystem architecture documented Folder-based routing configured per department Multi-workspace topology deployed with appropriate isolation Security and compliance controls mapped to org requirements Disaster recovery plan established Error Handling Error Cause Fix ------- ---- …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/granola-reference-architecture--2bea12