You are a senior automation engineer. Build the following optimized workflow.

# Triage support tickets

Spion recorded this as a manual browser process (6 steps, ~4 min, per ticket) and redesigned it as a consolidated automation (4 steps). Build the OPTIMIZED workflow below, not a replay of the manual clicks.

Overview: Read each ticket, classify and prioritize it, assign the right queue, and draft a templated reply for an agent to send.
Tools: Jira, Zendesk, Claude
Trigger: New ticket (When a new ticket is created).
Efficiency target: 6 manual steps down to 4 (33% fewer), saving ~4 min per run.

## Optimized workflow steps

1. [Claude] Classify and prioritize (added by Spion: net-new value)
   What: Category (access, hardware, software, how-to, outage) and priority from impact: an outage is P1, a single-user blocker P2, the rest P3.
   Why: consistent triage instead of whoever-grabs-it judgment.
2. [Claude] Detect duplicates
   What: Flag whether it matches a known issue or duplicates an open ticket.
3. [Zendesk] Assign and label
   What: Assign to the matching queue and apply the category and priority labels.
4. [Claude] Draft reply
   What: Draft a reply from the category's template, pre-filled with the requester's details, ready for an agent to review and send.

## Original manual process (reference only, do not replicate)
1. Open the ticket
2. Read it
3. Pick a category
4. Set a priority
5. Assign a queue
6. Write the first reply

## What I need from you
1. Build the optimized workflow exactly as designed above: production-ready code (Python or JavaScript) or a platform recipe (Workato, Make, Zapier, or n8n), whichever fits these tools best.
2. Preserve the consolidation. Do not expand it back into the manual click-by-click process.
3. Recommend the right trigger and cadence (schedule, webhook, or event). If it recurs, state the exact schedule.
4. Define the data contract for each step: the exact input fields it reads, the output fields it produces, and how fields map between tools.
5. Specify every authentication requirement: which services need OAuth, API keys, or service accounts, and the exact scopes.
6. Add robust error handling (missing data, auth failures, empty results, rate limits with retries) and make the workflow idempotent so it is safe to re-run.
7. Include a short test plan: a sample input and the expected result, so I can verify it before going live.
8. Finish with exact, copy-and-paste setup instructions so I can run it today.