# n8n + Jodoo Support Ticket Triage Recipe

## Workflow shape

1. Webhook node: receives the support ticket payload.
2. Agent Decision node: returns machine-readable triage fields.
3. HTTP Request node: sends mapped fields to Jodoo.
4. Jodoo record: stores requester, category, priority, SLA target, status, owner, and notes.

## Demo decision logic

The verified demo uses a credential-free Agent Decision code node. It returns deterministic fields for a synthetic SSO launch blocker so the workflow can be tested without adding external model credentials.

```json
{
  "requester_name": "Emma Carter",
  "requester_email": "emma.carter@northstar.example",
  "requester_department": "Customer Support",
  "issue_category": "Access & Permissions",
  "affected_asset": "Customer portal SSO login",
  "priority": "Critical",
  "sla_target": "2026-06-04 09:00",
  "ticket_status": "Escalated",
  "assigned_owner": "Support Escalation / Identity team",
  "routing_reason": "Launch-blocking authentication issue for an enterprise customer."
}
```

## Production AI Agent prompt

You are a support triage agent. Review each incoming ticket and return structured fields that Jodoo can store, route, and report on.

Classify the ticket using these signals:

- Category: What support queue should own the issue?
- Urgency: Is the customer blocked, at SLA risk, or waiting for launch?
- Priority: Critical, High, Medium, or Low.
- Owner: Which team should take the next action?
- First response: What should support say next?
- Follow-up: What evidence or next step should be tracked?

Return only structured output. Do not return a loose paragraph.

## HTTP Request mapping

| n8n output | Jodoo field |
| --- | --- |
| requester_name | Requester name |
| requester_email | Requester email |
| requester_department | Requester department |
| issue_category | Issue category |
| affected_asset | Affected asset |
| priority | Priority |
| sla_target | SLA target date |
| ticket_status | Ticket status |
| assigned_owner | Assigned owner |
| issue_description | Issue description |
| resolution_notes | Resolution notes |
| follow_up_note | Follow-up notes |
| full JSON response | Original agent output |

## Verified sample

- Test requester: Emma Carter
- Ticket: Customer portal SSO login failure before launch
- Outcome: Critical priority, Escalated status
- Jodoo data ID: 6a2006db953796b6817ab6aa

## Production notes

n8n Cloud or self-hosted n8n can run the orchestration. Model usage, hosting, credentials, and production execution volume can create costs. Keep Jodoo credentials out of public workflow files and test with synthetic tickets before sending real customer data.