Incident response procedures for Granola meeting capture issues. Use when handling meeting capture failures, system outages, or urgent troubleshooting situations. Trigger with phrases like "granola incident", "granola outage", "granola emergency", "granola not recording", "granola down".
/plugin marketplace add jeremylongshore/claude-code-plugins-plus-skills/plugin install granola-pack@claude-code-plugins-plusThis skill is limited to using the following tools:
Standard operating procedures for responding to Granola incidents and meeting capture failures.
| Level | Description | Response Time | Examples |
|---|---|---|---|
| P1 | Critical | < 15 min | Complete outage, data loss |
| P2 | High | < 1 hour | Recording failures, sync issues |
| P3 | Medium | < 4 hours | Single user issues, slow processing |
| P4 | Low | < 24 hours | UI bugs, minor inconveniences |
Incident Detected
↓
Assess Severity (5 min)
↓
Check Status Page (1 min)
↓
┌──────────────────────┐
│ Granola Issue? │
├──────────────────────┤
│ Yes → Workaround │
│ No → Local Debug │
└──────────────────────┘
↓
Communicate Status
↓
Track to Resolution
↓
Post-Incident Review
# Check status page
curl -s https://status.granola.ai/api/v2/status.json | jq '.status'
# Or visit: https://status.granola.ai
# Test API connectivity
curl -I https://api.granola.ai/health
# Expected: HTTP 200 OK
# macOS - Check if Granola is running
pgrep -l Granola
# Check Granola logs
tail -f ~/Library/Logs/Granola/granola.log
## Quick Fix (< 5 min)
1. [ ] Manually click "Start Recording" in Granola
2. [ ] Check calendar is connected (Settings > Integrations)
3. [ ] Verify meeting is on synced calendar
4. [ ] Restart Granola app
5. [ ] Check audio permissions granted
## Investigate (if quick fix fails)
1. Calendar Sync Issue:
- Last sync time?
- OAuth token valid?
- Correct calendar selected?
2. Audio Permission:
- System Preferences > Security > Microphone
- Is Granola listed and checked?
3. App State:
- Force quit and restart
- Clear cache if needed
- Check for updates
## Quick Fix
1. [ ] Check audio input device in System Preferences
2. [ ] Verify physical mic is not muted
3. [ ] Test mic with other app (Voice Memos)
4. [ ] Restart Granola app
5. [ ] Rejoin meeting if possible
## If Audio Cannot Be Captured
1. Take manual notes during meeting
2. Record with backup tool (QuickTime, OBS)
3. Upload/transcribe after meeting
4. Document for post-incident review
## Quick Fix
1. [ ] Wait up to 15 minutes (large meetings take longer)
2. [ ] Check internet connectivity
3. [ ] Check Granola status page for delays
4. [ ] Restart Granola app
5. [ ] Contact support if > 20 min
## Contact Support
Email: help@granola.ai
Include:
- Meeting date/time
- Meeting ID (if available)
- Duration of meeting
- Error messages shown
- Steps already tried
## Quick Fix
1. [ ] Check integration status (Settings > Integrations)
2. [ ] Reconnect if showing "Disconnected"
3. [ ] Test integration manually
4. [ ] Check destination app permissions
5. [ ] Verify Zapier Zap is enabled
## Manual Sync
If integration broken:
1. Export note as Markdown
2. Manually paste to Notion/Slack
3. Create tasks manually in Linear
4. Update CRM by hand if needed
## During Outage
1. [ ] Acknowledge internally (Slack)
2. [ ] Enable backup note-taking
3. [ ] Monitor status page
4. [ ] Document affected meetings
Communication Template:
"Granola is currently experiencing an outage.
Please take manual notes. We're monitoring
the situation and will update in 30 minutes."
## Alternative Note-Taking
1. Designate note-taker per meeting
2. Use Google Docs or Notion directly
3. Record via Zoom/Meet native recording
4. Upload to Granola when service restored
:warning: Granola Incident
Status: [Investigating/Identified/Monitoring/Resolved]
Impact: [Description of impact]
Workaround: [Available workaround]
ETA: [Expected resolution time]
Updates: Every 30 minutes
Next update: [Time]
Subject: Granola Service Update
We're aware of issues with [specific issue] affecting
[scope of impact].
Impact: [What users will experience]
Status: [Current status]
Workaround: [Steps users can take]
We'll update you within [timeframe].
- The Granola Team
## Incident Report: [Title]
**Date:** [Date/Time]
**Duration:** [Start to resolution]
**Severity:** [P1/P2/P3/P4]
**Impact:** [Number of users, meetings affected]
**Timeline:**
- HH:MM - Incident detected
- HH:MM - Investigation started
- HH:MM - Root cause identified
- HH:MM - Resolution applied
- HH:MM - Service restored
**Root Cause:**
[Description of what caused the incident]
**Resolution:**
[What was done to resolve]
**Prevention:**
[Steps to prevent recurrence]
**Lessons Learned:**
- [Key takeaways]
## Post-Incident Review
1. Incident summary (5 min)
2. Timeline review (10 min)
3. What went well (5 min)
4. What could improve (10 min)
5. Action items (10 min)
6. Assign owners and deadlines (5 min)
## Escalation Path
1. Primary: [IT Support]
2. Secondary: [Granola Admin]
3. Management: [Team Lead]
4. Executive: [VP/CTO] - P1 only
Proceed to granola-data-handling for data management procedures.
This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.