Triage AI support emails with human-in-the-loop routing via FirstHelm
Go to Workflow
Jason Bullen
Description
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
Starts when you manually execute the workflow in n8n.
Creates a sample support ticket payload with customer, subject, urgency, and ticket ID.
Sends a log event to FirstHelm (logActivity) to record that triage has started.
Calls FirstHelm (evaluateConstraint) to check whether sending a resolution email to the customer is allowed under the configured constraints.
If the ticket urgency is high, requests human approval via FirstHelm (requestApproval) and logs that the workflow is waiting for an operator decision.
If the ticket urgency is not high, logs an auto-response email action to FirstHelm.
Logs a final completion event to FirstHelm (logActivity) to mark the triage as finished.
Setup
Create a FirstHelm account and obtain a FirstHelm API key, then replace YOUR_FIRSTHELM_API_KEY in all HTTP requests.
Set your FirstHelm agent_id by replacing YOUR_AGENT_ID in the request bodies.
(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
This workflow was created by Jason Bullen and shared publicly on the n8n community template library. n8nFind indexes it for discovery — the workflow remains the property of its original creator.