InboundCI/CD & DevOps

GitLab CI + Alert24

Stream events from GitLab CI into Alert24 to correlate changes with incidents and shorten time to resolution.

Start Free TrialSee Pricing

Receive pipeline notifications and log deployments as changes to correlate with incidents.

Auto-detected payloads

Alert24 recognizes GitLab CI webhooks out of the box and maps fields to incidents automatically.

On-call routing & escalations

Page the right engineer over SMS, voice, push, email, or chat with policy-driven escalations.

Auto-updating status pages

Promote incidents to a public or private status page with one click and keep customers informed.

Change correlation & AI RCA

Recent deploys, infra updates, and feature flag flips surface alongside the incident for faster root cause.

Quick Setup

Copy Webhook URL

Go to your Alert24 dashboard and copy the webhook URL for GitLab CI.

Configure GitLab CI

Add the webhook URL in your GitLab CI settings.

Auto-Detected

Alert24 auto-detects GitLab CI payloads and maps them to incidents.

Step-by-Step Setup Instructions

GitLab CI Webhook Setup

1.In your GitLab project, go to Settings → Webhooks
2.Enter the webhook URL above
3.Set a Secret Token and enter the same value in the HMAC Secret field above
4.Check Pipeline events under triggers
5.Click Add webhook

Example Webhook Payload

This is a sample payload that GitLab CI sends to Alert24 when an alert fires.

{
  "object_kind": "pipeline",
  "object_attributes": {
    "id": 12345,
    "status": "failed",
    "name": "Deploy Production",
    "stages": [
      "build",
      "test",
      "deploy"
    ],
    "duration": 342,
    "created_at": "2024-01-15T10:25:00Z",
    "finished_at": "2024-01-15T10:30:42Z"
  },
  "project": {
    "name": "my-app",
    "web_url": "https://gitlab.com/org/my-app"
  }
}

How Alert24 Maps GitLab CI Data

Status Field

object_attributes.status

Message Field

object_attributes.name

Auto-Create Incidents

Yes

Auto-Resolve Incidents

Yes

Status Mapping

Alert24 StatusGitLab CI Values
operational
success
down
failed

Track Deployments from GitLab CI

Track changes for incident correlation and AI root cause analysis

  1. 1Go to your GitLab project → Settings → Webhooks
  2. 2Set URL to your Alert24 Changes Webhook URL
  3. 3Select triggers: Push events, Pipeline events, Merge request events
  4. 4Click Add webhook

Alert24 auto-detects GitLab push, pipeline, and merge request events.

# Or add to your .gitlab-ci.yml:
after_script:
  - |
    curl -s -X POST "${ALERT24_CHANGES_URL}" \
      -H "Content-Type: application/json" \
      -d "{
        \"summary\": \"Deploy ${CI_COMMIT_SHORT_SHA}\",
        \"change_type\": \"deployment\",
        \"commit_sha\": \"${CI_COMMIT_SHA}\",
        \"branch\": \"${CI_COMMIT_REF_NAME}\",
        \"changed_by\": \"${GITLAB_USER_NAME}\"
      }"

Changes are logged per service. Copy the Changes Webhook URL from your service page in Alert24. When an incident occurs, recent changes are surfaced automatically with AI-powered root cause analysis. Learn more →

Connect GitLab CI to Alert24 in minutes

Free plan includes 5 monitors, 1 status page, and incident management. No credit card required.

Start Free TrialSee Pricing

More CI/CD & DevOps Integrations

GitHub

Inbound

Log pull request merges, pushes, and releases as changes for incident correlation.

GitHub Actions

Inbound

Receive workflow run notifications and log deployments as changes to correlate with incidents.

CircleCI

Inbound

Receive job notifications and log deployments as changes to correlate with incidents.

Terraform Cloud

Inbound

Receive run notifications and log infrastructure changes to correlate with incidents.

Jenkins

Inbound

Receive build notifications and log deployments as changes to correlate with incidents.

Azure DevOps

Inbound

Receive pipeline and release notifications and log deployments as changes for incident correlation.