PagerDuty integration

Route BREAKING change alerts to PagerDuty and enrich incidents with Buildpathio ownership data so on-call engineers immediately know which team owns the affected service.

What this does

Sends a PagerDuty alert when a BREAKING check fires on a protected branch
Attaches the impacted service list, owning teams, and the PR link to the PagerDuty incident
Resolves the alert automatically when the BREAKING check passes on a subsequent push

Setup

In PagerDuty, go to Integrations → API Access Keys and create a new key with Full Access. Copy the key.

In Buildpathio, go to Settings → Integrations → PagerDuty. Paste the API key and select the escalation policy to use for BREAKING alerts.

Choose which severity level triggers a PagerDuty alert: BREAKING only (default), or BREAKING + WARNING.

Incident payload

Buildpathio sends the following context with each PagerDuty incident:

PagerDuty incident payload

{
  "summary": "BREAKING: [email protected] → payment-service",
  "source": "buildpathio",
  "severity": "critical",
  "custom_details": {
    "changed_service": "order-service",
    "changed_version": "1.5.0",
    "breaking_dependents": ["payment-service", "checkout-service"],
    "owning_teams": ["fulfillment", "payments"],
    "pr_url": "https://github.com/acme/order-service/pull/342"
  }
}

The PagerDuty integration is available on Pro and Team plans. It does not fire on Starter plan workspaces.