Automation library · Alerts and monitoring

Route critical out-of-office emails with Gmail and Gemini

Started by an arriving email, and works across Gmail, Google Sheets and Slack. 11 steps, 1 branch: a working afternoon to understand properly.

Medium

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

The flow

Starts it 1Logic 5Service 5

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

  1. 1When Email ReceivedGmail triggerStarts it
  2. 2Set Configuration FieldsSetLogic
  3. 3Prepare Email DataSetLogic
  4. 4Post to Gemini APIHttp RequestService
  5. 5Build Urgency DataSetLogic
  6. 6If Email Is CriticalIfLogic
  7. 7Post to Slack ChannelSlackService
  8. 8Do NothingNo OpLogic
  9. 9Reply to Client via GmailGmailService
  10. 10Append to SheetsGoogle SheetsService
  11. 11Add Label in GmailGmailService

How it's built

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

Questions

What does it need to run?

An n8n account, plus your own Gmail, Google Sheets and Slack 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. 11 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 11 steps before you point it at anything that matters.