Skip to main content

Investigate CI/CD incidents in Slack with a GPT-5.5 AI agent

Workflow preview

Workflow preview
100%
Investigate CI/CD incidents in Slack with a GPT-5.5 AI agent preview
Open on n8n.io

1. Workflow Overview

Overview It is a sub workflow that investigates CI/CD failures reported by engineers in Slack. It is invoked by a parent classifier and it runs an autonomous AI Agent that diagnoses the failing pip...

Best for

  • DevOps automation workflows
  • AI Chatbot automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.executeworkflowtrigger, @n8n/n8n-nodes-langchain.agent, @n8n/n8n-nodes-langchain.mcpclienttool, n8n-nodes-base.set, @n8n/n8n-nodes-langchain.toolworkflow, @n8n/n8n-nodes-langchain.lmchatopenai, n8n-nodes-base.slack, n8n-nodes-base.merge

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Sergei Byvshev.

Original n8n.io source

1.1 Workflow description

Title
Investigate CI/CD incidents in Slack with a GPT-5.5 AI agent
Workflow name
Investigate CI/CD incidents in Slack with a GPT-5.5 AI agent

Overview

It is a sub-workflow that investigates CI/CD failures reported by engineers in Slack. It is invoked by a parent classifier and it runs an autonomous AI Agent that diagnoses the failing pipeline, job, or deployment without making any changes.

Requirements

  • OpenRouter/OpenAI/Anthropic API key — for the chat model .
  • MCP servers (see MCP section) .
  • Slack credentials .
  • attachmentsAnalyzer sub-workflow — must be present in the same n8n instance; analyzes files attached to the originating Mattermost message and returns a textual context.
  • httpProbeTool sub-workflow — provides the probe_url tool that the agent uses to verify reachability of external dependencies; must return structured
  • Parent workflow — a classifier that calls this workflow via Execute Workflow

How it works

  • The workflow is invoked by another workflow via Execute Workflow Trigger
  • Call 'attachmentsAnalyzer' invokes a separate sub-workflow that fetches and analyzes any files the user attached to the originating Slack post
  • The successful branch returns enriched attachment context; the error branch goes through
  • SetVars materializes the runtime configuration
  • The agent is instructed to read the conversation history before pulling logs from anywhere else
  • Post a message sends the final answer back into theoriginal channel

How to use

  • Deploy MCP servers
  • Configure the SetVars node with your environment
  • Edit the AI Agent system prompt to match your organization
  • Import sibling sub-workflows:
  • attachmentsAnalyzer
  • httpProbeTool - for probe_url node tool
  • Connect a parent classifier that calls this workflow via Execute Workflow

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - When Executed by Another Workflow

Type / Role
n8n-nodes-base.executeWorkflowTrigger - executeWorkflowTrigger
Config choices
Version 1.1

Block 2 - AI Agent

Type / Role
@n8n/n8n-nodes-langchain.agent - agent
Config choices
Version 3.1

Block 3 - Grafana

Type / Role
@n8n/n8n-nodes-langchain.mcpClientTool - mcpClientTool
Config choices
Version 1.2

Block 4 - SetVars

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 5 - probe_url

Type / Role
@n8n/n8n-nodes-langchain.toolWorkflow - toolWorkflow
Config choices
Version 2.2

Block 6 - k8s

Type / Role
@n8n/n8n-nodes-langchain.mcpClientTool - mcpClientTool
Config choices
Version 1.2

Block 7 - OpenAI Chat Model

Type / Role
@n8n/n8n-nodes-langchain.lmChatOpenAi - lmChatOpenAi
Config choices
Version 1.3

Block 8 - Send a message

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.4

Block 9 - Slack

Type / Role
@n8n/n8n-nodes-langchain.mcpClientTool - mcpClientTool
Config choices
Version 1.2

Block 10 - Gitlab

Type / Role
@n8n/n8n-nodes-langchain.mcpClientTool - mcpClientTool
Config choices
Version 1.2

Block 11 - Merge

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3.2

Block 12 - Set: empty attachments

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 13 - Call 'attachmentsAnalyzer'

Type / Role
n8n-nodes-base.executeWorkflow - executeWorkflow
Config choices
Version 1.3

Block 14 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 15 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 16 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 17 - Sticky Note3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 18 - Sticky Note4

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 19 - Sticky Note5

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

3. Summary Table

Workflow Investigate CI/CD incidents in Slack with a GPT-5.5 AI agent
Complexity advanced
Nodes 19
Categories DevOps, AI Chatbot
Author Sergei Byvshev
Published 19 May 2026

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/15828/15828.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Investigate CI/CD incidents in Slack with a GPT-5.5 AI agent do?

Overview It is a sub workflow that investigates CI/CD failures reported by engineers in Slack. It is invoked by a parent classifier and it runs an autonomous AI Agent that diagnoses the failing pip...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your DevOps, AI Chatbot use case.