The flow
Starts it 1Model 2Logic 6Service 7
The steps in the order they run, from what starts it.
- 1Poll Station Status Every 15 MinSchedule triggerStarts it
- 2GPT-4o Mini Diagnosis ModelLm Chat Open AiModel
- 3Fault Code Reference LookupHttp Request ToolService
- 4Fetch Current Station StatusHttp RequestService
- 5Read Prior Station StateData TableService
- 6Diagnose Fault & Recommend ActionAgentModel
- 7Combine Current & Prior StateMergeLogic
- 8Tag Diagnosed FaultSetLogic
- 9Diff Station States & Detect New FaultsCodeLogic
- 10Active Session AffectedIfLogic
- 11Consolidate Station OutcomesMergeLogic
- 12New Fault DetectedIfLogic
- 13Trigger Driver Refund via Payment APIHttp RequestService
- 14Alert Technician Fault OnlyTelegramService
- 15Persist Station BaselineData TableService
- 16Alert Technician Refund IssuedTelegramService
How it's built
- Starts on
- A clock
- Steps
- 16, with 2 branches
- Size
- Medium: a working afternoon
- Connects to
- Telegram, n8n data table
- Model
- OpenAI
Questions
What does it need to run?
An n8n account, plus your own Telegram account, and a key for OpenAI. You connect your own accounts after importing it; none are included.
What starts it?
It starts on a clock.
Does it use AI?
Yes. It calls OpenAI. Model calls are billed by the provider, not by n8n.
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.