The flow
Starts it 1Logic 8Service 8
The steps in the order they run, from what starts it.
- 1Outlook - New email with attachmentsMicrosoft Outlook triggerStarts it
- 2Template - Configure variablesSetLogic
- 3Demo - Configure processingCodeLogic
- 4DATEV - Look up demo clientMaster DataService
- 5Demo - Evaluate client matchCodeLogic
- 6Demo - Exactly one client?IfLogic
- 7Attachments - Split and filter documentsCodeLogic
- 8Outlook - Mark review requiredMicrosoft OutlookService
- 9Attachments - Has archiveable document?IfLogic
- 10DATEV DMS - Upload fileDocument ManagementService
- 11DATEV DMS - Combine upload contextMergeLogic
- 12DATEV - Get current userIdentity And Access ManagementService
- 13DATEV DMS - Create documentDocument ManagementService
- 14Archive - Summarize successful DMS archiveCodeLogic
- 15Outlook - Mark archivedMicrosoft OutlookService
- 16Outlook - Move to archive folderMicrosoft OutlookService
- 17Slack - Notify archive successSlackService
How it's built
- Starts on
- An event in a connected app
- Steps
- 17, with 2 branches
- Size
- Medium: a working afternoon
- Connects to
- Outlook, Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Outlook and Slack 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. 17 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 17 steps before you point it at anything that matters.