Turn customer call transcripts into Pylon follow-ups

Build me an agent workflow that turns customer call transcripts into Pylon follow-ups.

Trigger: poll Fireflies.ai for new_transcript. When a new transcript is ready, run the agent.

Step 1 — pull the transcript. Use the Fireflies Get Transcript operation with the transcript id from the trigger. Read the meeting title, summary, action items, and the full attendee list (names, emails, organizer flag). Also keep the transcript URL so we can link back to the recording.

Step 2 — decide if this is a customer call. Identify external attendees by comparing email domains to the connected user's domain (treat anyone outside our own domain as external). If there are no external attendees, stop — this is an internal meeting, do nothing.

Step 3 — find the Pylon account for the customer. Use Pylon Search Accounts. Try external_id first (the customer email or domain may already be the account's external_id), then fall back to a free-text or filter search by the email domain. If multiple candidates come back, prefer the one with the most matching contact emails. If no account matches, log the transcript id and stop — do not create a stray account.

Step 4 — pull existing open issues for that account. Use Pylon Search Issues filtered to the matched account_id and a non-closed state, so you have context on what is already being tracked.

Step 5 — for each action item from the Fireflies transcript, classify it:

• Customer commitment: a promise to the customer such as a fix, a follow-up, a feature request, a piece of documentation, or a scheduled next step. These are the ones we log.

• Internal-only or unrelated: skip it (e.g. "send the deck to marketing", "update our forecast", small talk).

Step 6 — for each customer commitment, decide attach vs create:

• If the commitment clearly relates to one of the open Pylon issues (same bug, same feature request, same in-flight ask), use Pylon Create Internal Note on that issue. The note should contain the action item text, the owner if stated, the due date if stated, a one-line excerpt of the relevant transcript context, and a link back to the Fireflies recording.

• Otherwise, use Pylon Create Issue tied to the matched account. Title = a short summary of the commitment. Body = the action item, the owner (if stated), the due date (if stated), the meeting title and date, the customer attendees, and a link back to the Fireflies recording. Keep priority/state at sensible defaults.

Step 7 — be conservative about duplicates. Before creating a new issue, scan the open issues you already pulled for a near-duplicate title or topic; if one exists, attach as an internal note instead.

Output: a short run summary listing, per transcript, which Pylon issues were created and which existing issues got internal notes, plus any action items that were skipped and why. No external messages, no email — Pylon is the system of record.