Triage AI support emails with human-in-the-loop routing via FirstHelm

Quick overview

This workflow runs a sample support-ticket triage in n8n and uses FirstHelm’s control plane APIs to log activity, evaluate communication constraints, and route high-urgency tickets for human approval while logging completion.

How it works

1. Starts when you manually execute the workflow in n8n.
2. Creates a sample support ticket payload with customer, subject, urgency, and ticket ID.
3. Sends a log event to FirstHelm (logActivity) to record that triage has started.
4. Calls FirstHelm (evaluateConstraint) to check whether sending a resolution email to the customer is allowed under the configured constraints.
5. If the ticket urgency is high, requests human approval via FirstHelm (requestApproval) and logs that the workflow is waiting for an operator decision.
6. If the ticket urgency is not high, logs an auto-response email action to FirstHelm.
7. Logs a final completion event to FirstHelm (logActivity) to mark the triage as finished.

Setup

1. Create a FirstHelm account and obtain a FirstHelm API key, then replace YOUR_FIRSTHELM_API_KEY in all HTTP requests.
2. Set your FirstHelm agent_id by replacing YOUR_AGENT_ID in the request bodies.
3. (Optional) Replace the sample ticket fields (customer, subject, urgency, ticket_id) with values from your real support system or upstream trigger.

Requirements

• Free FirstHelm account (firsthelm.dev) + API key

Customization

• Swap the sample ticket trigger for your own Gmail/Outlook/helpdesk node