Turn Granola customer calls into Jira product issues
When a Granola meeting note lands, an agent extracts customer bug reports and feature requests, dedupes against your Jira backlog, and files or comments accordingly.
Granola
Jira
SlackProductCustomer SupportFeedback TriageMeeting WorkflowsNotifications & AlertsBuild me an agent workflow that turns customer feedback from Granola meeting notes into Jira product issues.
Trigger: poll Granola for new_note. Whenever a new meeting note is created, run the agent.
On each run, the agent should:
1. Use Granola Get Note to pull the full note for the triggering note id, including the summary and the transcript.
2. Read the summary and transcript and extract a list of candidate product issues. Only include explicit customer bug reports or feature requests raised by the customer. Skip generic discussion, internal asides, and roadmap chatter. For each candidate, capture: a short summary, the issue type (Bug or Story), the verbatim customer quote, and a few keywords plus a likely Jira component if you can infer one.
3. For every candidate, call Jira Search Issues (JQL) against the configured project to look for likely duplicates. Build a JQL query that scopes to project = <PROJECT_KEY>, filters out Done/Closed states, and matches on the candidate's keywords (text ~ "...") and component when present. Inspect the top results and decide if any are a real duplicate.
4. If a duplicate exists, call Jira Add Comment on that issue. The ADF comment should note that this came up again on a customer call, quote the customer, and include a link to the Granola note.
5. If no duplicate exists, call Jira Create Issue in the configured project with: issue type Bug or Story (based on the candidate), a clear one-line summary, an ADF description that quotes the customer and links back to the Granola note, and a label tying it to the meeting (for example granola-<note-id-or-slug>).
6. After processing all candidates, call Slack Send a Message to post a short recap to the configured product channel. The message should list, in compact bullets, what was created (with Jira issue keys and links) and what was updated (issue key plus "new customer mention"), and link back to the Granola note. If nothing actionable was found, post a one-liner saying so.
Configurable inputs the workflow should expose: Jira project key, Jira components or labels to scope the duplicate search, Slack channel id for the recap, and an optional toggle for whether to also include feature requests or only bugs.
Be conservative: when in doubt about duplicates, prefer commenting on the existing issue over creating a new one. Never create more than one Jira issue for the same candidate.
Additional information
What does this prompt do?
- Watches Granola for new meeting notes and reads the summary and transcript the moment a call wraps.
- Pulls out only the real product feedback — bug reports and feature requests — and ignores generic discussion.
- Checks your Jira project for likely duplicates and adds a customer mention to the existing issue when one exists.
- Files a new bug or story in the right project when nothing matches, with a clean summary and a link back to the Granola note.
- Posts a short Slack recap so your product team can see what was created or updated without opening Jira.
What do I need to use this?
- A Granola account with the meetings you want to mine for feedback.
- A Jira Cloud project where customer bugs and feature requests should land.
- A Slack workspace and a channel for the product team recap.
How can I customize it?
- Point it at a specific Jira project, or route different feedback types into different projects.
- Tighten or loosen what counts as feedback worth filing, like ignoring anything that is not raised by the customer themselves.
- Change the Slack channel or switch to a DM to the product manager instead of a shared channel.
- Adjust the labels and issue types so new tickets fit your existing taxonomy.
Frequently asked questions
Will it file an issue for every comment in a meeting?
How does it avoid creating duplicate Jira issues?
Where does the customer context end up in Jira?
Can I send the Slack recap to a private channel?
Do I need a paid Jira plan?
Related templates
Every Friday, get a ready-to-read preview of your league's weekend matches, with positions, form, scorers to watch, and predicted results, posted to Slack.
Every Monday morning, finance leadership gets a clear recap of last week's Braintree sales, refunds, and disputes by email and Slack.
Every morning we check your list of IP addresses for abusive activity, update your spreadsheet, and alert your team only about the risky ones.
Every time you ship to Heroku, we post a clear summary to Slack listing what changed, who deployed it, and whether it was a rollback.
Every weekday morning, your team gets one Slack briefing on who's flying today, their live flight status, and any delays or cancellations to act on.
Every Monday we scan your office, VPN, mail, and hosting IP ranges for abuse reports, post a summary to Slack, and open a ticket when anything crosses your risk line.
Stop losing customer feedback in meeting notes.
Connect Granola, Jira, and Slack once, and Geni files clean product issues every time a call wraps.