Turn Granola customer calls into Jira product issues

Build 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.