Automation library · Integrations

Automatic email unsubscribe handler: Outlook

Started by a clock, and works across Outlook. 12 steps, 1 loop or waits: a working afternoon to understand properly.

Medium

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

The flow

Starts it 1Logic 6Service 5

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

  1. 1Run Ever 4 HoursSchedule triggerStarts it
  2. 2Today & 7 Days AgoCodeLogic
  3. 3Query Bigquery for all UnsubscribesGoogle Big QueryService
  4. 4Get Emails in Past 7 DaysMicrosoft OutlookService
  5. 5Edit Fields1SetLogic
  6. 6Filter for UnsubscribesFilterLogic
  7. 7Keep Only New UnsubsMergeLogic
  8. 8Edit FieldsSetLogic
  9. 9Aggregate to email levelSummarizeService
  10. 10Loop Over Items1Split In BatchesLogic
  11. 11SummarizeSummarizeService
  12. 12Add unsubscribes to TableGoogle Big QueryService

How it's built

Starts on
A clock
Steps
12, 1 loop or waits
Size
Medium: a working afternoon
Connects to
Outlook
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

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

What starts it?

It starts on a clock.

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. 12 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 12 steps before you point it at anything that matters.