Route customer reply emails to Freshdesk
An n8n workflow catches customer replies to order confirmations and forwards support requests into Freshdesk.
What they did
They built 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.
How it went
It solved the problem of support replies landing in a generic info@ inbox without dumping unrelated mail into the support queue. The author says the first version took about 30 minutes to build, but gives no accuracy or volume numbers.
Worth knowing
The main practical catch is that the source stays high level: it names Gmail, an AI classifier, and Freshdesk, but does not share the workflow, prompt, or classification criteria.
Labels
An n8n workflow catches customer replies to order confirmations and forwards support requests into Freshdesk.
It solved the problem of support replies landing in a generic info@ inbox without dumping unrelated mail into the support queue.
An n8n workflow catches customer replies to order confirmations and forwards support requests into Freshdesk.
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
They built an n8n workflow around a dedicated catch-all Gmail inbox for replies to order-confirmation emails.
It solved the problem of support replies landing in a generic info@ inbox without dumping unrelated mail into the support queue. The author says the first version took about 30 minutes to build, but gives no accuracy or volume numbers.
The “Material” label failed its quality check and is not used for selection.
Details
- Agents
- n8n
- Source
- Source date
- undated
- Accounts
- 1
- In registry since
- Oct 12, 2026