计划执行与检查节点
executing-plans
按既定实施计划完成工作,保持过程检查和反馈。
granola-core-workflow-b【效率与协作】Post-meeting note processing, sharing, and follow-up workflows in Granola. Use when enhancing notes after meetings, sharing to Slack/Notion/CRM, drafting follow-up emails, or processing action items. Trigger: "granola post-meeting", "share granola notes", "granola follow-up", "granola enhance", "granola share".
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
name: granola-core-workflow-b description: 'Post-meeting note processing, sharing, and follow-up workflows in Granola.
Use when enhancing notes after meetings, sharing to Slack/Notion/CRM,
drafting follow-up emails, or processing action items.
Trigger: "granola post-meeting", "share granola notes", "granola follow-up",
"granola enhance", "granola share".
' allowed-tools: Read, Write, Edit version: 1.13.0 license: MIT author: Jeremy Longshore jeremy@intentsolutions.io tags:
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.
granola-core-workflow-a)After the meeting ends (transcript processing takes 1-2 minutes):
The Enhance step uses GPT-4o or Claude to:
Before sharing, review the enhanced notes:
Edit directly in the Granola editor — changes are saved instantly.
Slack (native integration):
Notion (native integration):
granola-sdk-patterns)HubSpot / Attio / Affinity (native CRM integration):
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.
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:
After meetings, Granola automatically updates contact records:
This built-in CRM tracks:
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.
| 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?" |
For a fictional follow-up workflow, record meeting=opaque-31; actions=4; owner_mapping=staged; destination=allowlisted; idempotency=once; rollback=workflow-r6. The example never exposes a meeting title, attendee, or action text.
Proceed to granola-sdk-patterns for Zapier automation and multi-app workflows.