granola-core-workflow-b
Optimizes post-meeting productivity by configuring note enhancement templates and automating sharing to Slack, Notion, or CRMs.
Install
mkdir -p .claude/skills/granola-core-workflow-b && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/8911" && unzip -o skill.zip -d .claude/skills/granola-core-workflow-b && rm skill.zipInstalls to .claude/skills/granola-core-workflow-b
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Post-meeting note processing, sharing, and follow-up workflows in Granola.Key capabilities
- →Enhance meeting notes using AI templates
- →Extract action items and key decisions
- →Share summaries to Slack, Notion, and CRM platforms
- →Draft follow-up emails via Granola Chat
- →Manage contact history in People & Companies CRM
How it works
Granola processes audio to generate a transcript, which is then combined with user notes and AI templates to produce structured meeting outputs.
Inputs & outputs
When to use granola-core-workflow-b
- →Enhancing meeting transcripts for clarity
- →Exporting action items to project management tools
- →Sharing meeting summaries with teams via Slack
- →Updating CRM records after client meetings
About this skill
Granola Core Workflow B: Post-Meeting Processing & Sharing
Overview
After a meeting ends, Granola processes your audio and produces a transcript. This skill covers the post-meeting workflow: enhancing notes, sharing to integrations, using Granola Chat for follow-up, and managing the People & Companies CRM.
Prerequisites
- At least one meeting captured in Granola
- Integrations connected (Slack, Notion, HubSpot — optional but recommended)
- Templates configured (see
granola-core-workflow-a)
Instructions
Step 1 — Enhance Notes
After the meeting ends (transcript processing takes 1-2 minutes):
- Open the meeting note in Granola
- Click Enhance Notes
- Select your template (or accept the auto-matched one)
- Granola merges your typed notes + full transcript into structured output
The Enhance step uses GPT-4o or Claude to:
- Organize content under template sections
- Extract action items with owners
- Identify key decisions
- Generate a concise summary
- Pull verbatim quotes (if your template includes that section)
Step 2 — Review and Edit
Before sharing, review the enhanced notes:
- Action items are correctly attributed to the right people
- Decisions are accurately captured
- No sensitive information in sections you plan to share externally
- Summary reflects the actual meeting outcome (not hallucinated)
Edit directly in the Granola editor — changes are saved instantly.
Step 3 — Share to Integrations
Slack (native integration):
- Click Share > Slack
- Select the target channel (or use auto-post to a configured folder's default channel)
- Granola posts a concise summary with action items
- Recipients can click through to the full note or use AI Chat in Slack for questions
Notion (native integration):
- Click Share > Notion
- Notes are saved as rows in a dedicated Notion database (created on first connect)
- Each note becomes a database entry with title, date, participants, and content
- Currently one-at-a-time sharing (for auto-sync, use Zapier — see
granola-sdk-patterns)
HubSpot / Attio / Affinity (native CRM integration):
- Click Share > HubSpot (or Attio/Affinity)
- Granola auto-matches the note to the correct Contact, Company, or Deal based on attendee emails
- Review the match suggestion and confirm
- Meeting summary appears on the CRM record timeline
Note: Native HubSpot integration does not auto-create new contacts. Create the contact in HubSpot first, then sync the note. For automatic contact creation, use a Zapier workflow with a "Find or Create Contact" step.
Step 4 — Use Granola Chat for Follow-Up
After enhancement, use the chat panel for post-meeting tasks:
You: "Draft a follow-up email to the client summarizing what we agreed"
Granola: Subject: Follow-up: Q1 Planning Discussion
Hi Sarah,
Thank you for the productive discussion today. Here's a summary
of what we agreed:
1. Timeline: MVP delivery by April 15
2. Budget: Approved up to $50K for Phase 1
3. Next Steps: Your team will share the API spec by Friday
Please let me know if I've missed anything.
Best regards
Other useful Chat queries:
- "What did [person] say about [topic]?" — searches transcript
- "List all open questions from this meeting" — finds unresolved items
- "Compare this meeting's decisions with last week's" — cross-note analysis
- "Create Jira ticket descriptions for each action item" — formatted for paste
Step 5 — Manage People & Companies
After meetings, Granola automatically updates contact records:
- Open People in the sidebar — see all contacts from meetings
- Click a person to view their full meeting history with you
- Open Companies for organization-level aggregation
- Before a follow-up meeting, review the contact card to refresh context
This built-in CRM tracks:
- Meeting frequency per contact
- Last interaction date
- Full conversation history across all meetings
- Job titles and company info (auto-enriched)
Step 6 — Organize with Folders
Structure your notes using folders:
| Folder | Purpose | Sharing |
|---|---|---|
Sales Calls | Client-facing meetings | Auto-post to #sales Slack |
Engineering | Technical meetings | Share to Notion wiki |
Leadership | Exec meetings | Private, no auto-share |
Interviews | Hiring loops | Shared with hiring panel only |
Folders support auto-posting rules: any note added to a folder can automatically trigger Slack posts or Zapier workflows.
Output
- Enhanced notes with structured sections, decisions, and action items
- Notes shared to Slack, Notion, and/or CRM as needed
- Follow-up email drafted via Granola Chat
- People & Companies records updated with meeting context
Error Handling
| Error | Cause | Fix |
|---|---|---|
| Enhance produces poor output | Template too complex or meeting too short | Simplify template sections, ensure meeting > 5 min |
| Slack post missing | Channel not configured or bot not invited | Verify channel in Settings > Slack, invite Granola bot |
| HubSpot contact mismatch | Attendee email differs from CRM record | Update attendee email or CRM contact |
| Notion share fails | Authorization expired | Reconnect Notion in Settings > Integrations |
| Chat gives wrong answer | Ambiguous question | Be specific: "What did Sarah say about the timeline?" |
Resources
Next Steps
Proceed to granola-sdk-patterns for Zapier automation and multi-app workflows.
When not to use it
- →Meetings shorter than 5 minutes
- →Meetings requiring automatic contact creation in HubSpot
Prerequisites
Limitations
- →Native HubSpot integration does not auto-create new contacts
- →Notion sharing is currently limited to one-at-a-time entries
How it compares
Unlike manual note-taking, this workflow automates the extraction of action items and synchronization with external project management and CRM tools.
Compared to similar skills
granola-core-workflow-b side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| granola-core-workflow-b (this skill) | 0 | 25d | No flags | Beginner |
| session-handoff | 13 | 2mo | Review | Beginner |
| spec-to-backlog | 8 | 4mo | No flags | Intermediate |
| create-handoff | 3 | 6mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
session-handoff
davila7
Creates comprehensive handoff documents for seamless AI agent session transfers. Triggered when: (1) user requests handoff/memory/context save, (2) context window approaches capacity, (3) major task milestone completed, (4) work session ending, (5) user says 'save state', 'create handoff', 'I need to pause', 'context is getting full', (6) resuming work with 'load handoff', 'resume from', 'continue where we left off'. Proactively suggests handoffs after substantial work (multiple file edits, complex debugging, architecture decisions). Solves long-running agent context exhaustion by enabling fresh agents to continue with zero ambiguity.
spec-to-backlog
atlassian
Automatically convert Confluence specification documents into structured Jira backlogs with Epics and implementation tickets. When Claude needs to: (1) Create Jira tickets from a Confluence page, (2) Generate a backlog from a specification, (3) Break down a spec into implementation tasks, or (4) Convert requirements into Jira issues. Handles reading Confluence pages, analyzing specifications, creating Epics with proper structure, and generating detailed implementation tickets linked to the Epic.
create-handoff
parcadei
Create handoff document for transferring work to another session
moai-workflow-project
modu-ai
Integrated project management system with documentation, language initialization, and template optimization modules. Use when setting up projects, generating documentation, configuring multilingual support, or optimizing templates.
reporting
comeredon
Final pipeline execution report format. Defines the structure, agent registry, Mermaid gantt chart, and change summary. Used by AnalystAgent in Phase 6.
weekly-report
quintindk
>