Email Ticket Intake
Checks the tech inbox for ticket requests, creates Asana tasks, stores thread tracking, updates the original subject, and uploads attachments.
Projects
Case Study · Automation · Integrations
A four-workflow n8n system that connects shared inbox requests, Asana tasks, email replies, attachment handling, and staff-triggered outbound responses into one ticket conversation loop.
The Problem
Asana organized the work, but submitters still expected normal email. I built the bridge so replies, attachments, and follow-up messages stayed tied to the task that owned them.
Approach
I built the system around recurring n8n checks so it could work cleanly in a locally hosted setup. Each workflow handles one responsibility, then stores just enough tracking data for the next workflow to continue the conversation without duplicate processing.
Result
New emails can become Asana tasks, Asana tasks can start email threads, email replies can become Asana comments, and staff can use a notify trigger in Asana to send a clean reply back to the original email thread. The result was a noticeably easier support flow for the department, with more people using the ticket system because responses were faster to see and easier to continue.
Interactive Proof
Select a workflow, inspect nodes, pan the canvas, and use Fit to bring the diagram back into frame.
System Components
Checks the tech inbox for ticket requests, creates Asana tasks, stores thread tracking, updates the original subject, and uploads attachments.
Watches Asana tasks for records that need an outbound email thread, sends the first message, and saves the task-to-thread relationship.
Reads inbox replies, filters ignored messages, matches each response to the stored ticket thread, and posts the reply back into Asana.
Finds Asana comments marked for notification, cleans the message, locates the original thread, sends the reply, and records the comment.