Route customer reply emails to Freshdesk
As described in the source, they assembled an n8n workflow around a dedicated catch-all Gmail inbox for replies to order-confirmation emails. An AI classifier checked each incoming message to decide whether it was a real support request, and if so the workflow forwarded it into Freshdesk instead of sending every reply to support; the post does not describe any manual review step. It solved the problem of support replies landing in a generic info@ inbox without dumping unrelated mail into the support queue.
- Agent or tool
- n8n
- Topic
- Automation
- Reported on
- Added
- 2026-10-15
Why it matters
Automation used to mean wiring up rigid rules. Agents can handle the messy, in-between steps that rules miss, which makes many more workflows worth automating. It is one of 19 sightings filed under Automation on Agent Sightings (number 6 by interest), and one of 36 involving n8n.
How you could try it
Here is a reusable prompt, written by us in our own words, that captures the task. Paste it into n8n or any similar agent and adjust the details to your situation.
Automation design: route customer reply emails to Freshdesk. Specify triggers, steps, and failure modes before enabling sends or deletes.
Tip: Start small: run it once on a low-stakes example, read what the agent did, and only then let it run on real work.
Source
Read the original first-hand account on Reddit: https://www.reddit.com/r/n8n/comments/1njjah9. Our summary is a paraphrase; details are in the source.