From granola-pack
Guides setup of Granola integrations for Slack, Notion, HubSpot, Attio, Affinity, and Zapier including configuration, testing, and Zapier automation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/granola-pack:granola-deploy-integrationThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Granola offers native integrations with Slack, Notion, HubSpot, Attio, and Affinity plus Zapier for 8,000+ additional apps. This skill covers setup, configuration, and testing for each platform. Business plan ($14/user/mo) required for all integrations.
Granola offers native integrations with Slack, Notion, HubSpot, Attio, and Affinity plus Zapier for 8,000+ additional apps. This skill covers setup, configuration, and testing for each platform. Business plan ($14/user/mo) required for all integrations.
Setup:
| Granola Folder | Slack Channel | Auto-Post |
|---|---|---|
| Sales Calls | #sales-notes | On |
| Engineering | #eng-meetings | On |
| All Hands | #general | On |
| 1-on-1s | (none) | Off |
How it works:
Slack Huddles support: Granola captures Slack Huddle audio the same way as Zoom/Meet — via system audio. Just ensure Granola is running and the huddle is on a synced calendar (or manually start recording).
Setup:
How it works:
Auto-sync workaround (via Zapier):
Trigger: Granola — Note Added to Folder ("All Meetings")
Action: Notion — Create Database Item
Database: Your Custom Database
Title: "{{title}}"
Date: "{{calendar_event_datetime}}"
Content: "{{note_content}}"
This bypasses the one-at-a-time limitation and lets you target any Notion database.
Setup:
How it works:
Limitations:
Zapier auto-sync workaround:
Trigger: Granola — Note Added to Folder ("Sales Calls")
Action: HubSpot — Find Contact (by attendee email)
Action: HubSpot — Create Contact (if not found)
Action: HubSpot — Create Engagement Note on Contact
Body: "{{note_content}}"
Setup:
Attio integration works similarly to HubSpot — manual sync per note, auto-matching by attendee email.
Setup:
Setup:
Available triggers:
| Trigger | Description |
|---|---|
| Note Added to Granola Folder | Auto-fires when any note is added to a specific folder |
| Note Shared to Zapier | Fires when you manually share a note to Zapier |
Popular Zapier recipes:
| Recipe | Trigger → Action |
|---|---|
| Notes to Google Drive | Note Added → Google Drive: Upload File |
| Action items to Asana | Note Shared → Asana: Create Task |
| Summary to email | Note Added → Gmail: Send Email |
| Notes to Salesforce | Note Shared → Salesforce: Create Note |
| Digest to Teams | Note Added → Microsoft Teams: Post Message |
Deploy a complete meeting follow-up chain:
Meeting ends → Granola enhances notes
→ Note added to "Client Meetings" folder
├→ Slack: Post summary to #client-updates
├→ Notion: Archive full notes in Client Database
├→ HubSpot: Log note on matched Deal/Contact
├→ Linear: Create tasks from action items
└→ Gmail: Draft follow-up email to external attendees
Configure each step as a separate Zapier action in a single multi-step Zap, or use Zapier Paths for conditional routing (internal vs. external meetings).
| Integration | Error | Fix |
|---|---|---|
| Slack | "Channel not found" | Channel may be renamed; verify name and invite Granola bot |
| Notion | "Cannot share" | Reconnect Notion; Granola's database may have been deleted |
| HubSpot | "No matching contact" | Create the contact in HubSpot first, then re-share |
| Attio | "Record not found" | Verify attendee email matches an Attio Person record |
| Zapier | "Trigger not firing" | Reconnect Granola in Zapier; check folder name matches exactly |
| All | "Authorization expired" | Disconnect and reconnect the integration in Settings |
Proceed to granola-webhooks-events for event-driven automation patterns.
npx claudepluginhub luxdevnet/claude-plus-lux --plugin granola-pack5plugins reuse this skill
First indexed Jul 10, 2026
Setup guide for Granola native integrations with Slack, Notion, HubSpot, Attio, Affinity, and Zapier. Includes configuration, testing, and automation chains.
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.