Turn Granola meeting notes into Slack action items and Linear issues

When a new Granola note lands, post a threaded action-item recap in Slack and open Linear issues for engineering and product owners.

Agentic Task
GranolaSlack BotLinearProductOperationsMeeting WorkflowsNotifications & Alerts
PromptCreate

Build me an agent workflow that turns every new Granola meeting note into shared action items in Slack and tracked work in Linear, so commitments do not die in a notes doc.

Trigger: poll Granola on new_note. Whenever a new meeting note appears, kick off the agent.

Step 1. Call Granola Get Note for the new note id and pull the full summary, the attendees with their emails, and the meeting title.

Step 2. Decide whether to skip. Skip the note entirely if it is a 1:1 (two attendees or a title that includes '1:1') or if the summary is shorter than a couple of paragraphs. The point is to avoid spamming the channel with low-signal notes.

Step 3. Extract the concrete action items with owners. Only count items that have a real verb and a real owner, like 'Priya to draft the rollout plan by Friday'. Skip vague 'we should think about' or 'maybe consider' lines.

Step 4. Resolve Slack handles. For each owner, take the attendee email from the Granola note and call Slackbot Look Up User by Email. If a match is found, tag the owner with their Slack handle. If not, leave the plain name.

Step 5. Post a single recap to a configurable Slack channel using Slackbot Send a Message. The top-level message should include the meeting title, the attendees, and a checklist of action items with each owner tagged. Post the action-item checklist in a thread under the top-level message so the channel stays clean.

Step 6. For any action item with a clear engineering or product owner, call Linear Create Issue. Use the action item as the title, include the meeting title and relevant summary context in the description, and set the assignee to the owner when their Linear account can be matched. Use a configurable Linear team as the default.

Configuration I want to control: the destination Slack channel, the default Linear team, and any meeting title or attendee rules that should change the routing or skip the note. Defaults are fine to start, but make these easy to change.

What does this prompt do?

  • Watches Granola for new meeting notes and pulls the full summary plus attendees with Get Note.
  • Extracts only the concrete action items with named owners, skipping vague 'we should think about' lines.
  • Posts a single threaded recap to a configurable Slack channel via Slackbot Send a Message with the meeting title, attendees, and an owner-tagged checklist.
  • Resolves Slack handles by matching attendee emails through Look Up User by Email when possible.
  • Opens a Linear issue with Create Issue for any action item that has a clear engineering or product owner, with the meeting context as the description and the owner as the assignee.
  • Skips 1:1s and very short notes so your channel does not get spammed.

What do I need to use this?

  • A Granola account with API access and the meeting notes you want to monitor.
  • A Slack workspace with the Slackbot integration connected and permission to post in your target channel.
  • A Linear workspace with permission to create issues in the relevant team.
  • Email addresses on your Slack profiles that match the attendee emails Granola captures, so owner tagging can resolve.

How can I customize it?

  • Change the destination Slack channel, or fan out to multiple channels by team or meeting type.
  • Adjust the skip rules. For example, only run for notes with at least three attendees, or skip notes whose title contains '1:1'.
  • Pick which Linear team receives new issues, or route to different teams based on keywords in the action item.
  • Tighten or loosen what counts as a real action item, such as requiring an explicit owner name and a verb.

FAQs

Will every Granola note create a Slack post and Linear tickets?
No. The agent skips notes from 1:1s and notes shorter than a couple of paragraphs, and only opens Linear issues for action items with a clear engineering or product owner.
How does owner tagging work in Slack?
The agent takes each attendee email from the Granola note and calls Look Up User by Email in Slack. When a match is found, the action item is tagged with that person's Slack handle. Items without a match stay tagged with the plain owner name.
What goes into the Linear issue?
The action item becomes the title, the meeting title and relevant context become the description, and the owner is set as the assignee when their Linear account can be matched.
Can I send the recap to different channels for different meetings?
Yes. Tell the agent which channel to use as the default and add rules based on meeting title, attendees, or calendar event so each note is posted where the right people will see it.
Does the recap get posted as a thread or a top-level message?
The agent posts a single top-level summary message and threads the action items underneath so the channel stays clean and the discussion stays attached to the recap.

Related templates

A brand asset library your marketing team actually searches

Every logo, photo, video cut and ad export in one searchable grid, with previews, campaign tags and rights expiry dates at a glance.

General Input Storage
General Input Database
JigsawStack
+1
App
Turn Mailjet email clicks into ranked HubSpot follow-ups

Twice a day we spot the people clicking your pricing and demo pages, create a follow-up task for their owner, and post a ranked recap to Slack.

Mailjet
HubSpot
Slack Bot
Agentic Task
Clean out the Looker dashboards and Looks nobody opens

One board showing every dashboard and Look with its folder, owner and favorite count, so you can find dead content and retire it safely.

Looker
Slack Bot
App
LiveKit live operations console for room moderation

Watch every live room on one screen, remove disruptive guests, start recordings and end stuck sessions without anyone opening a terminal.

LiveKit
Slack Bot
General Input Database
App
Wake up dormant Keap leads with a researched reason

Every Monday we find leads who never bought, research a real reason to reach out, and send a short personal email instead of another check in.

Keap
Slack Bot
Agentic Task
LiveChat coverage board for planning next week's shifts

See the exact hours your chat queue backs up and customers give up waiting, then plan next week's shifts before it happens again.

LiveChat
Slack Bot
General Input Database
App

Stop letting commitments die in a notes doc.

Connect Granola, Slack, and Linear once, and Geni turns every meaningful meeting note into shared action items and tracked work.