Automation library · Documents and files

Automatic Microsoft Outlook attachment storage to OneDrive

Started by an event in a connected app, and works across Excel and Outlook. 10 steps, 1 loop or waits: a working afternoon to understand properly.

Medium

10 stepsMedium: a working afternoon
0Branches: places the flow splits
1Loop or waits
2Services it connects to

The flow

Starts it 1Logic 3Service 6

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

  1. 1On Mail ReceivedMicrosoft Outlook triggerStarts it
  2. 2Get Message IDSetLogic
  3. 3Get AttachmentsMicrosoft OutlookService
  4. 4Loop Over ItemsSplit In BatchesLogic
  5. 5Notify UserMicrosoft TeamsService
  6. 6Get Folder IDMicrosoft One DriveService
  7. 7Download AttachmentMicrosoft OutlookService
  8. 8Upload to OneDriveMicrosoft One DriveService
  9. 9Set FilenameSetLogic
  10. 10Append to Excel LogMicrosoft ExcelService

How it's built

Starts on
An event in a connected app
Steps
10, 1 loop or waits
Size
Medium: a working afternoon
Connects to
Excel, Outlook
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

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

What starts it?

It starts on an event in a connected app.

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