CHATBOTS

Discord Pipeline Watcher: Live GitLab CI Updates in a Thread

When a GitLab pipeline starts, this opens a dedicated Discord thread and posts a running status as each stage transitions.

CategoryChatbots
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerGitLab pipeline webhook (status change)GitLabGitLab
  • LogicDedupe by pipeline ID, find or create thread
  • ActionFormat stage / branch / author status line
  • LogicBranch on terminal state (success vs failed)
  • OutputCreate or edit the Discord thread messageDiscordDiscord

What it does

Every GitLab pipeline event for a watched project lands as a webhook. The flow opens (or reuses) a single Discord thread per pipeline and edits it forward as stages move through running, success, or failed — so a noisy CI run becomes one tidy thread instead of a flood of pings.

When to use it

When merge-request authors want to babysit their pipeline from Discord without refreshing GitLab. Best for teams with multi-stage pipelines (build, test, deploy) where people care about which stage broke.

How it works

  1. 1A GitLab pipeline webhook fires on every status change.
  2. 2A logic step dedupes by pipeline ID to find or create the matching Discord thread.
  3. 3The flow formats the current stage, branch, and triggering user into a status line.
  4. 4A branch checks terminal state: on failed, it appends the failing job name and log link; on success, it posts the deploy target.
  5. 5The Discord thread message is created or edited so the thread always shows the latest state.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitLabRepos, MRs, pipelines, registry.
  2. 2
    Connect DiscordCommunity channels + voice + bots.
  3. 3
    Connect HTTP webhookTrigger any URL on agent actions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.