The flow
Starts it 1Model 9Logic 5Service 2
The steps in the order they run, from what starts it.
- 1When Executed by Another WorkflowExecute Workflow triggerStarts it
- 2OpenRouter Chat ModelLm Chat Open RouterModel
- 3GrafanaMcp Client ToolModel
- 4DigitalOceanMcp Client ToolModel
- 5K8SMcp Client ToolModel
- 6Embeddings Google GeminiEmbeddings Google GeminiModel
- 7GithubMcp Client ToolModel
- 8MattermostMcp Client ToolModel
- 9HTTP RequestHttp Request ToolService
- 10ReadIncidentContextCodeLogic
- 11AI AgentAgentModel
- 12Qdrant Vector StoreVector Store QdrantModel
- 13Call 'attachmentsAnalyzer'Execute WorkflowLogic
- 14Post a messageMattermostService
- 15MergeMergeLogic
- 16Set: empty attachmentsSetLogic
- 17SetVarsSetLogic
How it's built
- Starts on
- An event in a connected app
- Steps
- 17
- Size
- Medium: a working afternoon
- Connects to
- Mattermost, Qdrant
- Model
- Gemini, OpenRouter
- 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 Mattermost and Qdrant accounts, and a key for Gemini and OpenRouter. 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?
Yes. It calls Gemini and OpenRouter. 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.