Answer: You set up a Cursor agent to investigate new PagerDuty incidents by defining a pagerdutyChannel with an onIncident handler that returns a message like `Investigate PagerDuty incident #${event.incident.number}: ${event.incident.title}` and uses `defaultPagerDutyAuth(ctx)` for auth; on Cursor hosting you also declare `api.pagerduty.com` in egressDomains and `PAGERDUTY_TOKEN` in secretNames. Status: Confirmed Entry: tool/cursor/integrations/pagerduty-investigate-new-incident Revision: 1 Digest: sha256:ee06f06a1d28826c (changes whenever the content changes) Timeline: Created: 2026-11-13T03:08:37Z Last changed: 2026-11-13T03:08:37Z Last verified: 2026-11-20T12:33:12Z Next check: 2026-11-21T12:33:12Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of channel import | @grok/agent-sdk/channels/pagerduty | [1] | 2026-11-20 deliverReplies | true | [1] | 2026-11-20 event type filter | incident.triggered | [1] | 2026-11-20 message template | Investigate PagerDuty incident #${event.incident.number}: ${event.incident.title} | [1] | 2026-11-20 egress domain | api.pagerduty.com | [1] | 2026-11-20 secret name | PAGERDUTY_TOKEN | [1] | 2026-11-20 REST client | ctx.pagerduty | [1] | 2026-11-20 Sources: [1] Anysphere. "cursor.com/docs/agent-sdk/guides/pagerduty.md". https://cursor.com/docs/agent-sdk/guides/pagerduty.md Role: primary. Accessed: 2026-11-20T12:33:12Z Quote: "import { defaultPagerDutyAuth, pagerdutyChannel } from "@grok/agent-sdk/channels/pagerduty";" (Supports: channel import) Quote: "deliverReplies: true," (Supports: deliverReplies) Quote: "if (event.eventType !== "incident.triggered") {" (Supports: event type filter) Quote: "message: `Investigate PagerDuty incident #${event.incident.number}: ${event.incident.title}`," (Supports: message template) Quote: "egressDomains: ["api.pagerduty.com"]," (Supports: egress domain) Quote: "secretNames: ["PAGERDUTY_TOKEN"]," (Supports: secret name) Quote: "Hooks also get `ctx.pagerduty`, a REST client with the channel's credentials." (Supports: REST client) Snapshot SHA-256: a8324048a6d3f153209e51280e3901c4004417edc079bb4feb54def7305f4310 (captured 2026-11-13T03:08:38Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T03:08:37Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:33:12Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:33:12Z Last attempt: 2026-11-20T12:33:12Z Notes and limitations: Extracted automatically from a single official source (section "Investigate a new incident"). Related: https://latestn.com/tool/cursor/integrations/pagerduty-single-session How do I keep a Cursor PagerDuty agent following the same incident in one session? https://latestn.com/tool/cursor/integrations/prebuilt-channels What prebuilt channels does Cursor's Agent SDK provide? https://latestn.com/tool/cursor/integrations/publish-origin-app-to-marketplace How do I make my Cursor Origin app public and submit it to the App Marketplace? https://latestn.com/tool/cursor/integrations/other-ci-systems Can I use Cursor CLI in CI systems other than GitHub Actions? https://latestn.com/tool/cursor/integrations/pagerduty-deliver-replies How do I make a Cursor PagerDuty agent post its replies as notes on the incident? https://latestn.com/tool/cursor/integrations/pagerduty-ignore-own-actions How do I stop a Cursor PagerDuty agent from reacting to its own actions? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:08:37Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/cursor/integrations/pagerduty-investigate-new-incident/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/cursor/integrations/pagerduty-investigate-new-incident POST: https://latestn.com/dispute/tool/cursor/integrations/pagerduty-investigate-new-incident with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/cursor/integrations/pagerduty-investigate-new-incident?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I set up a Cursor agent to investigate new PagerDuty incidents? Revision 1, last verified 2026-11-20T12:33:12Z. https://latestn.com/tool/cursor/integrations/pagerduty-investigate-new-incident (accessed 2026-11-21T10:04:53Z). @misc{LatestN_tool_cursor_integrations_pagerduty_investigate_new_incident_r1, title = {How do I set up a Cursor agent to investigate new PagerDuty incidents?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/cursor/integrations/pagerduty-investigate-new-incident}}, note = {Revision 1; digest sha256:ee06f06a1d28826c; last verified 2026-11-20T12:33:12Z; accessed 2026-11-21T10:04:53Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/cursor/integrations/pagerduty-investigate-new-incident