Track Deployments in Alert24 from Any CI/CD Pipeline

Deployments are the most common cause of production incidents. When something breaks, the first question is always "did anything deploy recently?" Alert24's change log answers that question instantly — every deployment is timestamped, linked to a commit, and visible in your incident timeline.

How it works

Add a single step to the end of your deployment workflow. That step calls Alert24's changes API with metadata about the deployment (commit SHA, branch, pipeline URL, who deployed). The change appears in Alert24 immediately, correlated with any incidents that opened around the same time.

POST https://app.alert24.net/api/v1/changes
Authorization: Bearer ak_live_YOUR_KEY

{
  "summary": "Deployed my-app @ a1b2c3d",
  "change_type": "deployment",
  "environment": "production",
  "commit_sha": "a1b2c3d...",
  "branch": "main",
  "pipeline_url": "https://..."
}

Supported CI/CD tools

Change types

The change_type field lets you distinguish different kinds of changes in your timeline:

Linking changes to services

Add service_id to associate the change with a specific Alert24 service. When that service has an active incident, the change will be visible in the incident's context — immediately surfacing whether the deployment caused the problem.

{
  "summary": "Deployed payment-api @ v2.4.1",
  "service_id": "svc_YOUR_SERVICE_ID",
  "change_type": "deployment"
}

Find your service ID under Services or via GET /api/v1/services.

Any tool not listed?

Any tool that can run a shell command or make an HTTP request can log changes to Alert24. The curl / API guide shows the raw request format.