Triage Jotform bug reports into Linear tickets and Slack alerts

Build me an agent workflow that triages incoming bug reports and feature requests from my Jotform intake form and files them as Linear issues with a Slack alert. Trigger on a Jotform outgoing webhook so it runs the moment a submission lands.

At the start of each run, use Jotform's Get Form Questions once so the agent knows how to map the form's field IDs to human-meaningful labels like title, description, steps to reproduce, screenshots, console logs, and reporter email. Then use Jotform's Get Single Submission to pull the full submission that was just posted.

Read the submission and decide two things. First, is this a bug or a feature request. Second, if it's a bug, what severity: P0 for a production outage or data loss, P1 for a broken flow with no reasonable workaround, P2 for an annoyance that has a workaround, and P3 for a nice to have. Infer the product area from the description and any attachments: frontend, backend, mobile, or integrations. Feature requests should default to P3 unless the reporter argues for something higher.

Before filing, use Linear's Search Issues to look for an already open issue that matches the same problem. If a close match exists and the new report is P2 or P3, drop it and stop. If it's P0 or P1, still file the new issue but note the possible duplicate at the top of the description.

Otherwise, use Linear's Create Issue in the team that owns the inferred product area (I'll map area to team in the config). Set the priority to match the severity (Urgent for P0, High for P1, Normal for P2, Low for P3). Give it a clean, specific title that summarizes the issue in under 80 characters. In the description, include a short summary paragraph the agent wrote, a blockquote of the reporter's original words, a section for steps to reproduce and expected vs actual behavior if present, and links to any screenshots or console logs. Add labels for the severity, the area, and a 'bug' or 'feature-request' tag.

After the issue is filed, use Slack Bot's Send a Message to post a summary card in the #bugs channel. The card should include the severity, product area, one-sentence summary, reporter name, and a link to the Linear issue. For P0 or P1, @mention the on-call engineer user group so the message can't be missed. For P2 or P3, no mention.

Finally, if the submission captured a reporter email address and the issue is P0 or P1, use Gmail's Send a Message to reply to that email address with a short acknowledgement: thank them for the report, confirm the ticket has been filed, and note that engineering is looking at it. If there's no email captured or the issue is P2 or P3, skip this step.

Keep the agent focused. One run per submission. If Linear or Slack fails, retry once and then post an error message in the #bugs channel with the raw submission so nothing gets lost.