granola-ci-integration

jeremylongshore's avatarfrom jeremylongshore

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".

⭐939stars🔀114forks📁View on GitHub🕐Updated Jan 11, 2026

When & Why to Use This Skill

The Granola CI Integration skill enables developers and teams to automate the transition from meeting discussions to technical execution. By bridging Granola meeting notes with CI/CD pipelines, GitHub Actions, and Zapier, it automates the creation of GitHub issues, updates project documentation, and synchronizes tasks across platforms like Linear and Slack. This skill is essential for maintaining a high-velocity DevOps workflow where meeting outcomes are immediately translated into actionable code-related tasks.

Use Cases

  • Automated Task Management: Automatically extract action items from sprint planning or stand-up notes in Granola and create corresponding GitHub issues or Linear tasks with assigned owners.
  • Documentation-as-Code: Update meeting logs and project documentation in GitHub repositories automatically using repository dispatch events triggered by new Granola notes.
  • Cross-Platform Workflow Automation: Use Zapier webhooks to trigger complex multi-step workflows that notify Slack channels, update CRM records, and initiate CI/CD pipelines based on meeting summaries.
  • DevOps Pipeline Integration: Trigger specific GitHub Actions workflows to process meeting metadata, ensuring that technical decisions made during meetings are reflected in the development environment.
namegranola-ci-integration
description|
allowed-toolsRead, Write, Edit, Bash(gh:*), Bash(curl:*)
version1.0.0
licenseMIT
authorJeremy Longshore <jeremy@intentsolutions.io>

Granola CI Integration

Overview

Build automated workflows that process Granola meeting notes as part of your development pipeline.

Prerequisites

  • Granola Pro or Business plan
  • Zapier account
  • GitHub repository (for Actions)
  • Development workflow understanding

Architecture

Meeting-to-Action Pipeline

Meeting Ends
     ↓
Granola Processes Notes
     ↓
Zapier Webhook Triggered
     ↓
Processing Pipeline
     ├── Create Issues/Tasks
     ├── Update Documentation
     ├── Notify Team
     └── Update CRM

Zapier Webhook Setup

Step 1: Create Webhook Endpoint

# Create a Zapier Zap
Trigger: Granola - New Note Created
Filter: Meeting title contains "sprint" OR "planning"

Step 2: Parse Meeting Content

// Zapier Code Step - Parse Action Items
const noteContent = inputData.note_content;

// Extract action items
const actionPattern = /- \[ \] (.+?)(?:\(@(\w+)\))?/g;
const actions = [];
let match;

while ((match = actionPattern.exec(noteContent)) !== null) {
  actions.push({
    task: match[1].trim(),
    assignee: match[2] || 'unassigned'
  });
}

return { actions: JSON.stringify(actions) };

Step 3: Create GitHub Issues

Action: GitHub - Create Issue
Repository: your-org/your-repo
Title: "Meeting Action: {{task}}"
Body: |
  From meeting: {{meeting_title}}
  Date: {{meeting_date}}

  Task: {{task}}
  Assignee: {{assignee}}

  ---
  Auto-created by Granola integration
Labels: ["from-meeting", "action-item"]
Assignee: {{assignee}}

GitHub Actions Integration

Workflow: Process Meeting Notes

# .github/workflows/process-meeting-notes.yml
name: Process Meeting Notes

on:
  repository_dispatch:
    types: [granola-meeting-completed]

jobs:
  process-notes:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Parse Meeting Notes
        id: parse
        run: |
          echo "Processing meeting: ${{ github.event.client_payload.title }}"
          echo "Date: ${{ github.event.client_payload.date }}"

      - name: Update Meeting Log
        run: |
          # Append to meetings log
          echo "| ${{ github.event.client_payload.date }} | ${{ github.event.client_payload.title }} | [Link](${{ github.event.client_payload.url }}) |" >> docs/meetings.md

      - name: Create Issue for Action Items
        uses: actions/github-script@v7
        with:
          script: |
            const actions = JSON.parse('${{ github.event.client_payload.action_items }}');

            for (const action of actions) {
              await github.rest.issues.create({
                owner: context.repo.owner,
                repo: context.repo.repo,
                title: `Meeting Action: ${action.task}`,
                body: `From: ${{ github.event.client_payload.title }}\n\n${action.task}`,
                labels: ['meeting-action']
              });
            }

      - name: Commit Changes
        run: |
          git config user.name "Granola Bot"
          git config user.email "bot@granola.ai"
          git add docs/meetings.md
          git commit -m "docs: add meeting notes from ${{ github.event.client_payload.date }}"
          git push

Trigger Workflow from Zapier

# Zapier Webhook Action
Method: POST
URL: https://api.github.com/repos/your-org/your-repo/dispatches
Headers:
  Authorization: Bearer {{github_token}}
  Accept: application/vnd.github.v3+json
Body:
  {
    "event_type": "granola-meeting-completed",
    "client_payload": {
      "title": "{{meeting_title}}",
      "date": "{{meeting_date}}",
      "url": "{{granola_link}}",
      "summary": "{{summary}}",
      "action_items": {{action_items_json}}
    }
  }

Linear Integration Pipeline

Auto-Create Tasks from Meetings

# Zapier Multi-Step Workflow
Step 1 - Trigger:
  App: Granola
  Event: New Note Created

Step 2 - Filter:
  Condition: Summary contains "TODO" or "action item"

Step 3 - Parse:
  App: Code by Zapier
  Script: Extract action items with assignees

Step 4 - Loop:
  For each action item:
    App: Linear
    Action: Create Issue
    Team: Engineering
    Title: {{action.task}}
    Description: |
      From meeting: {{meeting_title}}
      Date: {{meeting_date}}

      Context: {{surrounding_text}}
    Assignee: {{action.assignee}}
    State: Todo

Slack Bot Integration

Meeting Summary Bot

# Automated Slack Post
Trigger: New Granola Note

Slack Message:
  Channel: #dev-meetings
  Blocks:
    - type: header
      text: "Meeting Notes: {{meeting_title}}"
    - type: section
      text: "{{summary}}"
    - type: divider
    - type: section
      text: "*Action Items:*\n{{action_items}}"
    - type: actions
      elements:
        - type: button
          text: "View Full Notes"
          url: "{{granola_link}}"
        - type: button
          text: "Create Tasks"
          action_id: "create_tasks"

Testing & Validation

Test Webhook Endpoint

# Test Zapier webhook with sample data
curl -X POST https://hooks.zapier.com/hooks/catch/YOUR_HOOK_ID \
  -H "Content-Type: application/json" \
  -d '{
    "meeting_title": "Test Sprint Planning",
    "meeting_date": "2025-01-06",
    "summary": "Discussed Q1 priorities",
    "action_items": [
      {"task": "Review PRs", "assignee": "mike"},
      {"task": "Update docs", "assignee": "sarah"}
    ]
  }'

Validate Integration

## Integration Test Checklist
- [ ] Schedule test meeting
- [ ] Complete meeting with sample action items
- [ ] Verify Zapier trigger fires
- [ ] Check GitHub issues created
- [ ] Confirm Slack notification sent
- [ ] Validate Linear tasks appear

Error Handling

Retry Configuration

# Zapier Error Handling
On Error:
  Retry: 3 times
  Delay: 5 minutes between retries
  Fallback: Send error to Slack #ops-alerts

Common Errors

Error Cause Solution
Webhook timeout Large payload Add processing delay
Auth expired Token invalid Refresh OAuth tokens
Rate limited Too many requests Add delays between actions
Parse failed Note format changed Update parsing logic

Resources

Next Steps

Proceed to granola-deploy-integration for native app integrations.