granola-local-dev-loop
Integrate Granola meeting notes into your local development workflow.Use when setting up development workflows, accessing notes programmatically,or syncing meeting outcomes with project tools.Trigger with phrases like "granola dev workflow", "granola development","granola local setup", "granola developer", "granola coding workflow".
When & Why to Use This Skill
The Granola Local Dev Loop skill bridges the gap between meeting productivity and software engineering by seamlessly integrating Granola meeting notes into local development environments. It automates note synchronization, action item extraction, and documentation updates, ensuring that project decisions are translated into code-ready tasks without manual overhead. By leveraging Zapier and local scripts, it creates a continuous feedback loop between team discussions and the codebase.
Use Cases
- Automated Note Syncing: Automatically transfer Granola meeting notes to a local project directory (e.g., ~/dev/meeting-notes) via Zapier for immediate access during development sessions.
- Action Item Extraction: Utilize Python-based scripts to parse meeting notes and extract actionable TODOs directly into your development task list or project management tools.
- Git-Integrated Documentation: Maintain a version-controlled record of meeting outcomes and architectural decisions within your project's repository to ensure team alignment.
- Workflow Automation: Trigger local development setups or update project documentation automatically following sprint planning or technical design meetings captured by Granola.
| name | granola-local-dev-loop |
|---|---|
| description | | |
| allowed-tools | Read, Write, Edit, Bash(curl:*), Grep |
| version | 1.0.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
Granola Local Dev Loop
Overview
Integrate Granola meeting notes into your local development workflow for seamless project management.
Prerequisites
- Granola installed and configured
- Zapier account (for automation)
- Project management tool (Jira, Linear, GitHub Issues)
- Local development environment
Instructions
Step 1: Export Notes Workflow
Configure automatic export of meeting notes:
- Open Granola Settings
- Go to Integrations > Zapier
- Connect your Zapier account
- Create a Zap: "New Granola Note" trigger
Step 2: Set Up Local Sync
Create a local directory for meeting notes:
# Create meeting notes directory
mkdir -p ~/dev/meeting-notes
# Create sync script
cat > ~/dev/scripts/sync-granola-notes.sh << 'EOF'
#!/bin/bash
# Sync Granola notes to local project
NOTES_DIR="$HOME/dev/meeting-notes"
PROJECT_DIR="$1"
if [ -z "$PROJECT_DIR" ]; then
echo "Usage: sync-granola-notes.sh <project-dir>"
exit 1
fi
# Copy relevant notes to project docs
cp -r "$NOTES_DIR"/*.md "$PROJECT_DIR/docs/meetings/" 2>/dev/null
echo "Synced meeting notes to $PROJECT_DIR/docs/meetings/"
EOF
chmod +x ~/dev/scripts/sync-granola-notes.sh
Step 3: Integrate with Git Workflow
# Add meeting notes to .gitignore if sensitive
echo "docs/meetings/*.md" >> .gitignore
# Or track action items only
cat > docs/meetings/README.md << 'EOF'
# Meeting Notes
Action items and decisions from team meetings.
Full notes available in Granola app.
EOF
Step 4: Create Action Item Extractor
#!/usr/bin/env python3
# extract_action_items.py
import re
import sys
def extract_actions(note_file):
with open(note_file, 'r') as f:
content = f.read()
# Find action items section
actions = re.findall(r'- \[ \] (.+)', content)
for action in actions:
print(f"TODO: {action}")
if __name__ == "__main__":
extract_actions(sys.argv[1])
Output
- Local meeting notes directory structure
- Sync script for project integration
- Action item extraction workflow
- Git-integrated note tracking
Workflow Example
1. Attend sprint planning meeting
Granola captures notes automatically
2. Notes sync to local directory
~/dev/meeting-notes/2025-01-06-sprint-planning.md
3. Extract action items
python extract_action_items.py notes/sprint-planning.md
4. Create tickets automatically
./create-tickets.sh TODO.md
5. Reference in commits
git commit -m "feat: implement login - per meeting 2025-01-06"
Error Handling
| Error | Cause | Solution |
|---|---|---|
| Sync Failed | Zapier disconnected | Reconnect Zapier integration |
| Notes Not Appearing | Export delay | Wait 2-5 minutes after meeting |
| Parsing Errors | Note format changed | Update extraction regex |
| Permission Denied | Directory access | Check file permissions |
Resources
Next Steps
Proceed to granola-sdk-patterns for advanced Zapier automation patterns.