The flow
Starts it 2Logic 7Service 7
The steps in the order they run, from what starts it.
- 1Every HourSchedule triggerStarts it
- 2Workflow Error TriggerError triggerStarts it
- 3Get Unread Emails with AttachmentsMicrosoft OutlookService
- 4Send Error EmailMicrosoft OutlookService
- 5Has Emails?IfLogic
- 6Is Upload Error?IfLogic
- 7Process One Email at a TimeSplit In BatchesLogic
- 8No Emails - DoneNo OpLogic
- 9Log Failed Upload to SharePointMicrosoft Share PointService
- 10Get Email AttachmentsMicrosoft OutlookService
- 11Build Folder Path + Decode AttachmentCodeLogic
- 12Has File Attachments?IfLogic
- 13Upload to OneDriveMicrosoft One DriveService
- 14Aggregate Attachment UploadsCodeLogic
- 15Log to SharePoint Audit ListMicrosoft Share PointService
- 16Mark Email as ReadMicrosoft OutlookService
How it's built
- Starts on
- A clock
- Steps
- 16, with 3 branches, 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. 16 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.
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 16 steps before you point it at anything that matters.