Automation library · Integrations

Triage and label Gmail inbox emails with OpenRouter Gemini 3.5

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

Medium

9 stepsMedium: a working afternoon
0Branches: places the flow splits
0Loops or waits
1Service it connects to

The flow

Starts it 1Logic 4Service 4

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

  1. 1When Email Unread in InboxGmail triggerStarts it
  2. 2Normalize Email DataCodeLogic
  3. 3Build Classification RequestCodeLogic
  4. 4Classify with OpenRouterHttp RequestService
  5. 5Verify Classification OutputCodeLogic
  6. 6Fetch Gmail LabelsGmailService
  7. 7Determine Category LabelCodeLogic
  8. 8Label Email by CategoryGmailService
  9. 9Mark as readGmailService

How it's built

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

Questions

What does it need to run?

An n8n account, plus your own Gmail account. 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.