Agent skill · marketing growth · jeremylongshore
granola-webhooks-events
Build event-driven automations with Granola''s Zapier webhook triggers.
Why this skill is useful
Provides specific event-driven automation patterns and webhook payload structures that the AI wouldn't reliably generate on its own.
What it needs
Requires granola, zapier account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
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: Key fields for filtering and routing: attendees[].email — detect internal vs. external meetings calendareventtitle — match meeting type patterns notecontent — search for action items, decisions, keywords Step 3 — Event Filtering Patterns Use Zapier Filter steps to route events: Filter: Only External Meetings Filter: Only Meetings with Action Items Filter: Only Sales Calls (by title keywords) Filter: Long Meetings Only (> 30 min) Step 4 — Build a Custom Webhook Handler Forward Granola events from Zapier to your own endpoint: Express.js handler: Python FastAPI handler: Step 5 — Processing Patterns Pattern When to Use Implementation --------- ------------ ---------------- Immediate Time-sensitive follow-ups Direct Zapier actions, ~2 min latency Batch Reduce noise, aggregate Queue to SQS/Redis, process every 15 min Conditional Route by meeting type Zapier Paths or custom webhook with routing logic Idempotent Prevent duplicate processing Store processed note IDs, skip duplicates S …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/granola-webhooks-events--e78835