The flow
Starts it 1Model 2Logic 10Service 4
The steps in the order they run, from what starts it.
- 1Daily Vehicle CheckSchedule triggerStarts it
- 2OpenRouter Chat ModelLm Chat Open RouterModel
- 3Simulate Vehicle DataSetLogic
- 4Fleet Data SourceCodeLogic
- 5AI Maintenance AnalyzerAgentModel
- 6Analyze Maintenance NeedsSetLogic
- 7Split Fleet DataSplit In BatchesLogic
- 8Parse AI AnalysisCodeLogic
- 9Check If Maintenance NeededIfLogic
- 10Enhanced Slack Alert with AISlackService
- 11Generate Alert DetailsCodeLogic
- 12No Maintenance NeededSetLogic
- 13Send Slack AlertSlackService
- 14Log to DatabasePostgresService
- 15Aggregate Fleet AlertsAggregateLogic
- 16Generate Fleet SummaryCodeLogic
- 17Send Fleet Summary to SlackSlackService
How it's built
- Starts on
- A clock
- Steps
- 17, with 1 branch, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- Postgres, Slack
- Model
- OpenRouter
Questions
What does it need to run?
An n8n account, plus your own Postgres and Slack accounts, and a key for OpenRouter. 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 OpenRouter. Model calls are billed by the provider, not by n8n.
How long does it take to set up?
Plan an afternoon. 17 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 17 steps before you point it at anything that matters.