The flow
Starts it 1Model 6Logic 5Service 5
The steps in the order they run, from what starts it.
- 1Incident TriggerWebhookStarts it
- 2OpenAI EmbeddingsEmbeddings Open AiModel
- 3OpenAI Chat ModelLm Chat Open AiModel
- 4Root Cause Output ParserOutput Parser StructuredModel
- 5Document LoaderDocument Default Data LoaderModel
- 6Workflow ConfigurationSetLogic
- 7Cluster Log MessagesVector Store In MemoryModel
- 8Root Cause Analysis AgentAgentModel
- 9Fetch LogsHttp RequestService
- 10Fetch MetricsHttp RequestService
- 11Fetch Recent DeploymentsHttp RequestService
- 12Fetch Feature FlagsHttp RequestService
- 13Identify Failure PatternsCodeLogic
- 14Create Incident TicketSlackService
- 15Normalize and Denoise LogsCodeLogic
- 16Merge Context DataAggregateLogic
- 17Time-Align EventsCodeLogic
How it's built
- Starts on
- Another system calling it
- Steps
- 17
- Size
- Medium: a working afternoon
- Connects to
- Slack, in-memory vectors
- Model
- OpenAI
- Retrieval
- Answers are drawn from documents you supply, not from the model alone
Questions
What does it need to run?
An n8n account, plus your own Slack and in-memory vectors accounts, and a key for OpenAI. You connect your own accounts after importing it; none are included.
What starts it?
It starts on another system calling it.
Does it use AI?
Yes. It calls OpenAI. Its answers draw on documents you give it, not on the model alone. 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.