Create your own Linear and PagerDuty integration

Choose a trigger
Choose an action

When Linear: Issue created happens, do PagerDuty: Create incident.

Popular Linear and PagerDuty workflows

When this happens in one app, do this in the other. Try it on Hub to connect both apps and run the pair.

Most popular

Open a Linear postmortem when incidents resolve

When PagerDuty resolves a Sev1, create a Linear issue in Postmortems with the incident timeline link.

PagerDuty + LinearTry it →

Track status page copy in Linear

When a Linear incident comms issue is created, add the PagerDuty incident id as a comment for traceability.

Linear + PagerDutyTry it →

Update Linear when on-call acknowledges

When the primary on-call acknowledges in PagerDuty, move the linked Linear issue to In progress.

PagerDuty + LinearTry it →

Page from a Linear regression label

When a Linear issue gets label production-regression, trigger a PagerDuty incident for the platform service.

Linear + PagerDutyTry it →

Mirror PagerDuty notes on the Linear thread

When a PagerDuty incident is assigned to a new responder, post the handoff summary as a Linear comment.

PagerDuty + LinearTry it →

Agent

Use Corsair's MCP with your agent

Corsair connected

The agent searches both apps before it answers.

Do we still owe a postmortem for Friday's outage?

Linear and PagerDuty details

Linear and PagerDuty FAQ

Yes. Corsair is built with a REST API. This means you can build agents, knowledge bases, interfaces, and workflows.

Yes. With Corsair you connect both apps once, then automate in either direction: PagerDuty incidents drive Linear postmortem tasks and Linear regressions can trigger pages.

Auto-create postmortems on resolve, sync acks to issue status, page from regression labels, and mirror handoff notes.

PagerDuty incident lifecycle events and Linear issue and comment webhooks are typed triggers.