Back to rankings

Windsurf: Devin Adds PagerDuty Integration for Oncall Response

WindsurfView original changelog

Windsurf's Devin can now connect directly to PagerDuty, letting incident events (triggered, acknowledged, resolved, and updated) trigger Devin automations automatically. The integration also lets Devin act as an oncall responder, triaging incoming PagerDuty incidents on its own and posting its investigation directly as incident notes. It extends Devin's existing Auto-Triage automation platform to a new class of on-call and incident-response workflows.

Key Takeaways

  • PagerDuty is now a first-class trigger source for Devin Automations, alongside Slack, Linear, GitHub, and webhooks, covering triggered, acknowledged, resolved, and updated incident states.
  • Devin can be configured as an oncall responder, automatically triaging PagerDuty incidents without a human kicking off the investigation first.
  • Investigation output is posted directly as PagerDuty incident notes, keeping context inside the tool the on-call team is already working in.
  • The feature extends Auto-Triage, Devin's proactive incident-investigation system, into the on-call/PagerDuty workflow specifically.
  • The integration is aimed at SRE and on-call engineering teams rather than general application developers, making it a narrower but potentially high-value addition for that audience.

PagerDuty Joins Devin's Automation Triggers

Windsurf's Devin added a native PagerDuty integration to its Automations platform, giving incident-response teams a direct line from PagerDuty into Devin's agentic workflows. Once connected, PagerDuty incident events, specifically when an incident is triggered, acknowledged, resolved, or updated, can be configured as triggers for any Devin automation, alongside the existing Slack, Linear, GitHub, and webhook triggers already supported.

Devin as an Oncall Responder

The more notable part of the release is that Devin can now be configured to act as an oncall responder in its own right. When a PagerDuty incident fires, Devin triages it automatically: it investigates the underlying issue using the same codebase and observability access it already has through Auto-Triage, then posts its findings back to PagerDuty as incident notes rather than requiring an engineer to kick off a manual investigation first.

This builds on Auto-Triage, the proactive incident-investigation capability Windsurf introduced for Devin earlier in 2026, which already pulled from Slack, Linear, GitHub, Sentry, and Datadog. PagerDuty's addition rounds out the incident-management side of that toolkit, specifically targeting the on-call rotation workflow where the first response to a page often just confirms what Devin can now investigate directly.

Why It Matters

For teams running on-call rotations, this closes a gap between "an alert fired" and "someone has looked into it." Rather than an engineer being paged, opening a laptop, and manually cross-referencing logs, Devin can already have a preliminary root-cause writeup waiting as an incident note by the time a human engineer picks up the page.