Answer infrastructure questions in Mattermost with OpenRouter and Qdrant
Ready for 3.0What this workflow does
This AI workflow has 17 nodes and runs when another workflow calls it. Along the way it connects OpenRouter Chat Model, MCP Client, Qdrant Vector Store and Embeddings Google Gemini and 2 more.
How it runs
Trigger: When another workflow calls it.
- ReadIncidentContext (Code): runs custom JavaScript code
- Call 'attachmentsAnalyzer' (Execute Sub-workflow): calls another n8n workflow
- Merge: merges the data from its input branches
- Set: empty attachments (Edit Fields (Set)): sets 2 fields: attachments_context, attachments_count
- SetVars (Edit Fields (Set)): sets 12 fields: GITHUB_ORG, K8S_NAMESPACE, K8S_CLUSTERS…
- AI Agent: runs an AI agent, with model: OpenRouter Chat Model; 7 tools (K8S, Github, Grafana, Mattermost…)
- Post a message (Mattermost): uses Mattermost
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (12)
- Execute Workflow Trigger
n8n-nodes-base.executeWorkflowTrigger - AI Agent
@n8n/n8n-nodes-langchain.agent - OpenRouter Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenRouter - MCP Client Tool
@n8n/n8n-nodes-langchain.mcpClientTool - Qdrant Vector Store
@n8n/n8n-nodes-langchain.vectorStoreQdrant - Embeddings Google Gemini
@n8n/n8n-nodes-langchain.embeddingsGoogleGemini - Mattermost
n8n-nodes-base.mattermost - Code
n8n-nodes-base.code - Edit Fields (Set)
n8n-nodes-base.set - Http Request Tool
n8n-nodes-base.httpRequestTool - Merge
n8n-nodes-base.merge - Execute Sub-workflow
n8n-nodes-base.executeWorkflow
From the author
Overview AI-powered sub-workflow that answers questions about a your infrastructure configuration directly in a Mattermost channel or thread Requirements OpenRouter/OpenAI/Anthropic API key Google Gemini API key — for embeddings Jira API credentials — Cloud…