The flow
Starts it 1Logic 9Service 2
The steps in the order they run, from what starts it.
- 1Run Synthetic CheckManual triggerStarts it
- 2Set AISIX Probe ConfigSetLogic
- 3List AISIX Model AliasesHttp RequestService
- 4Build Model Probe QueueCodeLogic
- 5Route Discovery ResultSwitchLogic
- 6Probe Model via AISIXHttp RequestService
- 7Return Discovery FailureSetLogic
- 8Classify Probe ResultCodeLogic
- 9Build AISIX Health ReportCodeLogic
- 10Route Health StatusSwitchLogic
- 11Return Healthy ReportSetLogic
- 12Return Attention ReportSetLogic
How it's built
- Starts on
- An event in a connected app
- Steps
- 12, with 2 branches
- 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 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. 12 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 12 steps before you point it at anything that matters.