The flow
Starts it 1Logic 4Service 6
The steps in the order they run, from what starts it.
- 1Schedule TriggerSchedule triggerStarts it
- 2Create n8n TicketsHttp RequestService
- 3Get Open TicketsHttp RequestService
- 4Pull Unifi Site'sHttp RequestService
- 5Separate Status and Device InfoCodeLogic
- 6Filter On Problematic SitesCodeLogic
- 7Check if Alert ExistsRedisService
- 8MergeMergeLogic
- 9Add Parameter to Filter onCodeLogic
- 10Teams AlertMicrosoft TeamsService
- 11Log Alert for 3hRedisService
How it's built
- Starts on
- A clock
- Steps
- 11
- Size
- Medium: a working afternoon
- Connects to
- Redis
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Redis 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. 11 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 11 steps before you point it at anything that matters.