The flow
Starts it 1Model 7Logic 6Service 2
The steps in the order they run, from what starts it.
- 1Schedule TriggerSchedule triggerStarts it
- 2Anthropic Model - Anomaly Detection AgentLm Chat AnthropicModel
- 3Anomaly Detection Output ParserOutput Parser StructuredModel
- 4Anthropic Model - Maintenance Prioritization AgentLm Chat AnthropicModel
- 5Maintenance Prioritization Output ParserOutput Parser StructuredModel
- 6RUL Calculation ToolTool CodeModel
- 7Workflow ConfigurationSetLogic
- 8Anomaly Detection AgentAgentModel
- 9Maintenance Prioritization AgentAgentModel
- 10Fetch Real-Time Vehicle TelemetryHttp RequestService
- 11Fetch Historical Vehicle DataHttp RequestService
- 12Check Urgency LevelIfLogic
- 13Merge Telemetry and Historical DataMergeLogic
- 14Format Urgent AlertSetLogic
- 15Format Standard Maintenance RecordSetLogic
- 16Generate Audit LogCodeLogic
How it's built
- Starts on
- A clock
- Steps
- 16, with 1 branch
- Size
- Medium: a working afternoon
- Connects to
- Nothing by connector; it calls services over plain HTTP
- Model
- Claude
Questions
What does it need to run?
An n8n account, and a key for Claude. 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 Claude. 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.
Before you run itNothing 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.