From granola-pack
Configure Granola CI/CD integration with automated workflows. Use when setting up automated meeting note processing, integrating with development pipelines, or building Zapier automations. Trigger with phrases like "granola CI", "granola automation pipeline", "granola workflow", "automated granola", "granola DevOps".
How this skill is triggered — by the user, by Claude, or both
Slash command
/granola-pack:granola-ci-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
- [Overview](#overview)
Build automated workflows that process Granola meeting notes into GitHub issues, Linear tasks, Slack notifications, and documentation updates.
Create Zap with Granola "New Note Created" trigger. Add filter for meeting type (sprint, planning, etc.).
Use Zapier Code step to extract action items with assignees from note content using regex patterns.
Route parsed action items to GitHub as labeled issues with meeting context.
Create repository_dispatch workflow triggered by Zapier to update meeting logs and create issues programmatically.
Auto-create Linear tasks from action items with team assignment and meeting context.
Post meeting summaries with action items and "View Full Notes" button to team channels.
See detailed implementation for Zapier code steps, GitHub Actions workflow YAML, Linear pipeline config, and Slack bot message format.
| Error | Cause | Solution |
|---|---|---|
| Webhook timeout | Large payload | Add processing delay step |
| Auth expired | Token invalid | Refresh OAuth tokens in Zapier |
| Rate limited | Too many requests | Add delays between actions |
| Parse failed | Note format changed | Update parsing regex logic |
Proceed to granola-deploy-integration for native app integrations.
npx claudepluginhub bulozb/claude-code-plugins-plus-skills --plugin granola-packGuides 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.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
4plugins reuse this skill
First indexed Jul 11, 2026