Skip to content
PagerDuty logoCursor logo

Connect PagerDuty to Cursor

Move data between PagerDuty and Cursor the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

PagerDuty triggers
3
PagerDuty actions
6
Cursor triggers
5
Cursor actions
4

Automation ideas

What you can build with PagerDuty and Cursor

A few flows teams run between PagerDuty and Cursor. Use one as a starting point, or build your own from scratch.

  • New Incident in PagerDuty creates Launch Agent in Cursor

    Triggers when a new incident is created

  • New Agent in Cursor creates Create Incident in PagerDuty

    Triggers when a new Cursor agent is created or when agent status changes

  • New Incident in PagerDuty creates Add Followup Instruction to Agent in Cursor

    Triggers when a new incident is created

  • New Agent in Cursor creates List Incidents in PagerDuty

    Triggers when a new Cursor agent is created or when agent status changes

  • New Incident in PagerDuty creates Find Agent Status in Cursor

    Triggers when a new incident is created

  • New Agent in Cursor creates Get Incident in PagerDuty

    Triggers when a new Cursor agent is created or when agent status changes

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

Yes. Build one flow that starts in PagerDuty and acts in Cursor, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.