Automation library · Customer support

Route and prioritize Gmail support tickets to Notion

Started by an arriving email, and works across Gmail, Notion and Slack. It hands the judgement calls to Gemini. 9 steps, 1 branch: a working afternoon to understand properly.

MediumCalls a model: Gemini

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

The flow

Starts it 1Model 2Logic 3Service 3

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

  1. 1Watch for support emailsGmail triggerStarts it
  2. 2Google GeminiLm Chat Google GeminiModel
  3. 3Extract email fieldsSetLogic
  4. 4Classify ticket with AIChain LlmModel
  5. 5Parse AI classificationCodeLogic
  6. 6Create ticket in NotionNotionService
  7. 7Is critical priorityIfLogic
  8. 8Alert team on SlackSlackService
  9. 9Post ticket summary to SlackSlackService

How it's built

Starts on
An arriving email
Steps
9, with 1 branch
Size
Medium: a working afternoon
Connects to
Gmail, Notion, Slack
Model
Gemini

Questions

What does it need to run?

An n8n account, plus your own Gmail, Notion and Slack accounts, and a key for Gemini. You connect your own accounts after importing it; none are included.

What starts it?

It starts on an arriving email.

Does it use AI?

Yes. It calls Gemini. Model calls are billed by the provider, not by n8n.

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.