The flow
Starts it 1Logic 8Service 5
The steps in the order they run, from what starts it.
- 1Schedule TriggerSchedule triggerStarts it
- 2Configuration VariablesSetLogic
- 3Get session tokenHttp RequestService
- 4Tickets about to expireHttp RequestService
- 5Split OutSplit OutLogic
- 6Loop Over ItemsSplit In BatchesLogic
- 7AggregateAggregateLogic
- 8Support Technician 1?IfLogic
- 9End session1Http RequestService
- 10Send a message to Support Technician 1Microsoft TeamsService
- 11Support Technician 2?IfLogic
- 12No Operation, do nothing2No OpLogic
- 13Send a message to Support Technician 2Microsoft TeamsService
- 14No Operation, do nothing3No OpLogic
How it's built
- Starts on
- A clock
- Steps
- 14, with 2 branches, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- Nothing by connector; it calls services over plain HTTP
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n 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. 14 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 14 steps before you point it at anything that matters.