Automation library · Alerts and monitoring

Analyze GitLab CI job failures with OpenAI

Started by another system calling it, and works across Slack. It hands the judgement calls to OpenAI. 16 steps, 1 branch: a working afternoon to understand properly.

MediumCalls a model: OpenAI

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

The flow

Starts it 1Model 4Logic 7Service 4

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

  1. 1Get Job EventsWebhookStarts it
  2. 2OpenAI Chat ModelLm Chat Open AiModel
  3. 3HTTP RequestHttp Request ToolService
  4. 4Gitlab MCPMcp Client ToolModel
  5. 5MCP GrafanaMcp Client ToolModel
  6. 6Is job failed?IfLogic
  7. 7AI AgentAgentModel
  8. 8SetVarsSetLogic
  9. 9No Operation, do nothingNo OpLogic
  10. 10Send a messageSlackService
  11. 11Extract event dataCodeLogic
  12. 12GetJobLogsHttp RequestService
  13. 13GetCIFileHttp RequestService
  14. 14MergeMergeLogic
  15. 15GetLastLogLinesCodeLogic
  16. 16FormatDataCodeLogic

How it's built

Starts on
Another system calling it
Steps
16, with 1 branch
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 another system calling it.

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