| name | granola-sdk-patterns |
| description | Zapier automation patterns and Enterprise API integration for Granola.
Use when building automated workflows, connecting Granola to 8,000+ apps via Zapier,
or querying the Enterprise API for notes and transcripts.
Trigger: "granola zapier", "granola automation", "granola API", "granola SDK".
|
| allowed-tools | Read, Write, Edit, Bash(curl:*) |
| version | 1.13.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","granola","automation","api"] |
| compatibility | Designed for Claude Code, also compatible with Codex and OpenClaw |
Granola SDK Patterns
Overview
Granola does not have a traditional SDK. Integration is achieved through three channels: Zapier (8,000+ app connections), the Enterprise API (REST, workspace-level read access), and native integrations (Slack, Notion, HubSpot, Attio, Affinity). This skill covers automation patterns for all three.
Prerequisites
- Granola Business plan ($14/user/month) for Zapier + native CRM
- Enterprise plan ($35+/user/month) for API access
- Zapier account for automation workflows
Instructions
Step 1 — Understand Zapier Triggers
Granola provides two Zapier triggers:
| Trigger | Fires When | Use Case |
|---|
| Note Added to Granola Folder | A note is placed in a specific folder | Auto-route by meeting type |
| Note Shared to Zapier | You manually share a note to Zapier | Selective sharing for important meetings |
Webhook payload data available:
title — meeting title from calendarcreator_name / creator_email — note creatorattendees[] — array of {name, email} objectscalendar_event_title — original calendar event namecalendar_event_datetime — meeting date/timenote_content — the enhanced note content (Markdown)
Step 2 — Build Common Zap Patterns
Pattern 1: Meeting Notes to Notion (auto-archive)
Trigger: Note Added to Granola Folder ("All Meetings")
Action: Notion — Create Database Item
Database: Meeting
