Automation library · Customer support

Route Gmail support emails to Zendesk

Started by an arriving email, and works across Gmail and Zendesk. 9 steps, 1 branch: a working afternoon to understand properly.

Medium

9 stepsMedium: a working afternoon
1Branch: places the flow splits
0Loops or waits
2Services it connects to

The flow

Starts it 1Logic 6Service 2

The steps in the order they run, from what starts it.

  1. 1New Support Email TriggerGmail triggerStarts it
  2. 2Spam Detection & FilteringCodeLogic
  3. 3Extract & Normalize Email DataSetLogic
  4. 4Auto-Tag Ticket Based on Email ContentCodeLogic
  5. 5Zendesk – Fetch Existing TicketsZendeskService
  6. 6Merge Email With Existing TicketsMergeLogic
  7. 7Detect Duplicate Ticket by SubjectCodeLogic
  8. 8Is This a New Ticket?IfLogic
  9. 9Create Zendesk Support TicketZendeskService

How it's built

Starts on
An arriving email
Steps
9, with 1 branch
Size
Medium: a working afternoon
Connects to
Gmail, Zendesk
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Gmail and Zendesk accounts. You connect your own accounts after importing it; none are included.

What starts it?

It starts on an arriving email.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Plan an afternoon. 9 steps is enough that you should read each one before running it.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 9 steps before you point it at anything that matters.