The flow
Starts it 2Logic 8Service 6
The steps in the order they run, from what starts it.
- 1When clicking "Execute Workflow"Manual triggerStarts it
- 2Schedule TriggerSchedule triggerStarts it
- 3Get Meraki OrganizationsHttp RequestService
- 4Get Org Name & IDSetLogic
- 5Get Uplink Loss and LatencyHttp RequestService
- 6Get Network IDsHttp RequestService
- 7Combine latency to its respective NetworkMergeLogic
- 8Sets Network VariablesSetLogic
- 9Makes Latency and Loss FilterableSetLogic
- 10Average Latency & Loss over 5mCodeLogic
- 11Filters Problematic sitesCodeLogic
- 12Check if Alert ExistsRedisService
- 13MergeMergeLogic
- 14Create ResponseCodeLogic
- 15Message TechsMicrosoft TeamsService
- 16Log the AlertRedisService
How it's built
- Starts on
- A clock
- Steps
- 16
- 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. 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.