CHATBOTS
Discord Bot: Explain Why My MR Pipeline Failed
A Discord slash-command bot that takes a GitLab MR or pipeline ID, pulls the failed job logs, and replies in-channel with a plain-English root cause and the exact failing step.
How it runs
The automated pipeline, trigger to output.
- TriggerDiscord slash command /whyfail with MR or pipeline IDDiscord
- ActionResolve ID and fetch pipeline jobs from GitLabGitLab
- LogicBranch: any job failed? If not, reply all-green
- ActionDownload raw trace for first failed jobGitLab
- ActionParse trace and extract root cause with LLMOpenAI
- OutputPost threaded root-cause reply in DiscordDiscord
What it does
Contributors run a slash command in Discord with their merge request or pipeline ID. The bot fetches the failed pipeline from GitLab, downloads the trace of the first failing job, and returns a short, plain-English explanation of what broke and where, so they don't have to read hundreds of log lines or ping a maintainer.
When to use it
Use this when your repo gets frequent "why did CI fail?" questions in chat and maintainers spend time triaging trivial failures (lint, type errors, flaky tests). It turns self-serve triage into a 10-second command.
How it works
- 1A contributor invokes a Discord slash command (`/whyfail <mr-or-pipeline-id>`).
- 2The bot resolves the ID to a pipeline and lists its jobs via the GitLab API.
- 3A branch checks whether any job failed; passing pipelines short-circuit to a friendly "all green" reply.
- 4For the first failed job, it downloads the raw job trace from GitLab.
- 5An LLM parses the trace, classifies the failure type, and extracts the exact failing command and error line.
- 6The bot posts a threaded reply in Discord with the root cause, the failing step, and a suggested next action.
Set it up
What you configure once, before turning it on.
- 1Connect DiscordCommunity channels + voice + bots.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 3Connect OpenAIModels, embeddings, files.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Chatbots workflows
Discord Onboarding Completion to CRM Sync
The moment a member finishes Discord onboarding, captures their submitted profile answers, creates or updates a contact in HubSpot.
Discord FAQ-Gated Role Concierge
Greets each new Discord member in a private onboarding thread, walks them through required FAQ steps one at a time.
Discord FAQ Free-Text Answer Grader
When a member submits a free-text answer in their onboarding thread, an agent grades it against the canonical FAQ knowledge base, replies with targeted feedback.
Discord verify-button onboarding via web form webhook
Receives a completed external verification form by webhook, matches it to the Discord account, grants the verified role, and confirms back to the member in Discord.
Discord intro-gated role granting concierge
Watches your #introductions channel, uses AI to confirm a new member's intro is genuine and complete, then auto-assigns the verified Member role and welcomes them.
Daily Discord Digest of Repeated WAF False-Positive Reports
Each morning, scans logged Discord WAF reports in Postgres, groups them by the Cloudflare rule that keeps firing.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.