Automation library · Alerts and monitoring

Automate GitLab tag releases to Jira and Slack for Dev and QA

Started by another system calling it, and works across Jira and Slack. 11 steps, 1 branch: a working afternoon to understand properly.

Medium

11 stepsMedium: a working afternoon
1Branch: places the flow splits
0Loops or waits
2Services it connects to

The flow

Starts it 3Logic 3Service 5

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

  1. 1Git Tag WebhookWebhookStarts it
  2. 2Is Valid Semver?IfLogic
  3. 3Fetch Commits from BranchHttp RequestService
  4. 4Slack: Invalid Format WarningSlackService
  5. 5Generate Release NotesCodeLogic
  6. 6Webhook Error ResponseRespond To WebhookStarts it
  7. 7Create an issueJiraService
  8. 8Prepare Slack PayloadSetLogic
  9. 9Slack: Dev ChannelSlackService
  10. 10Slack: QA ChannelSlackService
  11. 11Webhook ResponseRespond To WebhookStarts it

How it's built

Starts on
Another system calling it
Steps
11, with 1 branch
Size
Medium: a working afternoon
Connects to
Jira, Slack
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Jira and Slack accounts. 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?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Plan an afternoon. 11 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 11 steps before you point it at anything that matters.