Escalate Zendesk bug tickets into clean Linear issues

Build an agent workflow that escalates real engineering bugs from Zendesk into Linear automatically, so support agents stop manually re-typing bug reports into the engineering tracker.

Trigger: Zendesk poll trigger on the new_ticket event. Fire whenever a new ticket is created in our Zendesk account.

For each new ticket, the agent should do the following:

1. Dedup safety net. Check the ticket's tags. If it already has the linear-escalated tag, stop immediately. As an extra safeguard, the agent may use Zendesk Search Tickets with a query like tags:linear-escalated and the ticket id to confirm it has not already been escalated.

2. Classify the ticket. Read the subject, description, and any existing comments. Decide whether this is a real engineering bug (broken behavior, errors, regressions, things that should work but do not) versus a how-to question, a billing or account issue, a feature request, or general feedback. If it is not a bug, skip the ticket entirely and do nothing else. Only continue when the agent has high confidence it is a real bug.

3. Use Linear's Create Issue operation to file the issue in our designated engineering team. The agent can use Linear's List Teams operation if it needs to discover the right team id. The new issue should include:

- A concise, engineer-friendly title generated from the ticket (not just a copy of the Zendesk subject). - A structured markdown description with these sections: Problem summary, Expected behavior, Actual behavior, Steps to reproduce, Environment details (browser, OS, app version, account or workspace if mentioned), Customer impact (who is affected and how badly), and a Source section with a link back to the Zendesk ticket and the requester's email if available. - Priority mapped from the Zendesk ticket priority using Linear's enum: Zendesk urgent maps to Linear 1 (urgent), Zendesk high maps to Linear 2 (high), Zendesk normal maps to Linear 3 (medium), and Zendesk low or no priority maps to Linear 4 (low).

4. Use Zendesk Update Ticket to add an internal note (not a public reply) on the original ticket containing the new Linear issue URL and a one-line summary like "Escalated to engineering as <linear identifier>." In the same Update Ticket call, add the tag linear-escalated to the ticket so it is never escalated again.

Be defensive. If Linear Create Issue fails, do not tag the Zendesk ticket as escalated, so a retry can happen on the next run. If the ticket is missing fields the agent needs, fall back to sensible defaults rather than failing (for example, default to Linear priority 3 medium when no Zendesk priority is set).

Operations to use: Zendesk Search Tickets (optional dedup), Linear List Teams (optional, to find the engineering team id), Linear Create Issue, Zendesk Update Ticket. Trigger: Zendesk poll, event new_ticket.