Automation library · Chat assistants

Investigate CI/CD incidents in Slack with OpenAI

Started by an event in a connected app, and works across Slack. It hands the judgement calls to OpenAI. 13 steps: a working afternoon to understand properly.

MediumCalls a model: OpenAI

13 stepsMedium: a working afternoon
0Branches: places the flow splits
0Loops or waits
1Service it connects to

The flow

Starts it 1Model 7Logic 4Service 1

The steps in the order they run, from what starts it.

  1. 1When Executed by Another WorkflowExecute Workflow triggerStarts it
  2. 2GrafanaMcp Client ToolModel
  3. 3probe_urlTool WorkflowModel
  4. 4k8sMcp Client ToolModel
  5. 5OpenAI Chat ModelLm Chat Open AiModel
  6. 6SlackMcp Client ToolModel
  7. 7GitlabMcp Client ToolModel
  8. 8Call 'attachmentsAnalyzer'Execute WorkflowLogic
  9. 9AI AgentAgentModel
  10. 10MergeMergeLogic
  11. 11Set: empty attachmentsSetLogic
  12. 12Send a messageSlackService
  13. 13SetVarsSetLogic

How it's built

Starts on
An event in a connected app
Steps
13
Size
Medium: a working afternoon
Connects to
Slack
Model
OpenAI

Questions

What does it need to run?

An n8n account, plus your own Slack account, and a key for OpenAI. 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 OpenAI. Model calls are billed by the provider, not by n8n.

How long does it take to set up?

Plan an afternoon. 13 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.

Before you run it

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 13 steps before you point it at anything that matters.