GitLab alerts, routed to the right on-call engineer
Page on failed pipelines and jobs on your default branch and on failed deployments, from GitLab.com or self-managed GitLab. Verified with the webhook's secret token. EvoHub turns each GitLab alert into an on-call alert, runs it through your escalation policy, and pages people by voice call, mobile push and email.
How the GitLab integration works
- Create a GitLab integration in EvoHub On-Call and pick the escalation policy it should notify.
- EvoHub gives the integration its own URL (or inbound address) with a unique key — paste it into GitLab using the steps below.
- Each GitLab alert opens an EvoHub alert, and your escalation policy pages the on-call person — then the next step if nobody acknowledges.
- Resolves automatically when the next pipeline or job on the same branch, or the next deployment to the same environment, succeeds.
Set up GitLab
Create the integration in EvoHub first — it shows your personal integration URL to paste below.
# 1. Project (or group) → Settings → Webhooks → Add new webhook
URL: <your EvoHub integration URL>
Secret token: the signing secret from this integration
# (GitLab 19.1+ signing token instead? Paste that whsec_… value
# into "Use my own" on this integration.)
# 2. Trigger — tick one of:
# Pipeline events (one page per failed pipeline), or
# Job events (one page per failed job)
# and, if you deploy with GitLab environments:
# Deployment events
# 3. Add webhook. Test → Pipeline events replays your latest
# pipeline — a failed one on the default branch will page.
# What pages:
# • a failed pipeline on the default branch → high;
# the next successful pipeline on that branch resolves it
# (child pipelines are left to their parent)
# • a failed job on the default branch, unless allow_failure → high
# • a failed deployment → critical for the production tier, else high;
# the next successful deployment to that environment resolves it
# Pushes, merge requests and other branches are answered OK, so
# GitLab never disables the webhook for them.GitLab + EvoHub — FAQ
How do I connect GitLab to EvoHub?
In EvoHub, go to On-Call → Integrations, add GitLab, and choose an escalation policy. Then configure GitLab with the integration URL EvoHub shows you — the exact steps are on this page.
Do GitLab alerts resolve automatically in EvoHub?
Resolves automatically when the next pipeline or job on the same branch, or the next deployment to the same environment, succeeds.
How is the GitLab integration priced?
Integrations are included. EvoHub bills on usage, not per seat: an ingested alert costs 1 EvoHub token (about $0.015), push and webhook notifications are free, and every account gets 200 free tokens each month.
Start free — 200 EvoHub tokens every month. See pricing.
Last updated: · EvoHub is built and operated by EvoSync Teknoloji A.Ş.