granola-webhooks-events

# Granola Webhooks & Events ## Overview Granola does not expose raw webhook endpoints. All event-driven automation flows through Zapier, which provides two trigger events. This skill covers the event model, webhook payload structure, event filtering, processing patterns, and building custom event handlers. ## Prerequisites - Granola Business plan (for Zapier access) - Zapier account (Free for basic Zaps, Paid for multi-step) - Optional: custom webhook endpoint (Express.js, FastAPI, or serverless function) ## Instructions ### Step 1 — Understand the Event Model Granola fires events through Zapier triggers, not direct webhooks. Two triggers are available: | Trigger | When It Fires | Use Case | |---------|--------------|----------| | **Note Added to Granola Folder** | A note is placed in a specific folder (automatic) | Auto-route by meeting type | | **Note Shared to Zapier** | You manually click Share > Zapier on a note | Selective sharing for important meetings | ### Step 2 — Webhook Payload Structure When a Zapier trigger fires, Granola sends this data: ```json { "title": "Sprint Planning — Q1 Week 12", "creator_name": "Sarah Chen", "creator_email": "sarah@company.com", "attendees": [ {"name": "Sarah Chen", "email": "sarah@company.com"}, {"name": "Mike Johnson", "email": "mike@company.com"}, {"name": "Alex Kim", "email": "alex@external.com"} ], "calendar_event_title": "Sprint Planning", "calendar_event_datetime": "2026-03-22T10:00:00Z", "no...