Classify and route DevOps chat requests with Mattermost and Claude
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
Nodes used (10)
- Webhook
n8n-nodes-base.webhook - Code
n8n-nodes-base.code - OpenRouter Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenRouter - Switch
n8n-nodes-base.switch - Google Calendar
n8n-nodes-base.googleCalendar - AI Agent
@n8n/n8n-nodes-langchain.agent - MCP Client Tool
@n8n/n8n-nodes-langchain.mcpClientTool - Qdrant Vector Store
@n8n/n8n-nodes-langchain.vectorStoreQdrant - Embeddings Google Gemini
@n8n/n8n-nodes-langchain.embeddingsGoogleGemini - Edit Fields (Set)
n8n-nodes-base.set
What it does
Automatically classify and route DevOps requests from your team chat using LLM + on-call calendar lookup. What it does This workflow turns your Mattermost channel into a smart DevOps intake system. When someone mentions @devops-duty, the workflow: 1. Receives the message via Mattermost outgoing webhook 1. Classifies the request into one of 8 categories using an LLM 1. Looks up the current on-call engineer from Google Calendar 1. Routes the request through a Switch node based on category 1. Acknowledges in a Mattermost thread with the classification result Categories createresource - Provision new databases, secrets, services, DNS records incident - Something is broken — production or staging issues question - Information requests, status checks, clarifications cicderror - Build failures, deployment issues, GitHub Actions problems limits - Billing limits, quotas exceeded changerequest - Modify existing infrastructure or configuration codeapprove - Code review and merge request approvals other - Anything that doesn't fit above Extending Each Switch output is an independent branch — connect sub-workflows or additional nodes per category. For example: incident → trigger an AI investigation sub-workflow with MCP tools (Kubernetes, Grafana, etc.) createresource → run a provisioning playbook cicderror → fetch GitHub Actions logs and analyze failures Connect these workflows: - incident - newsystem, modify infrastructure - cicderror - question