PagerDuty Trigger icon

PagerDuty Trigger

Starts the workflow when PagerDuty events occur
Join our community

Overview

The PagerDuty Trigger node for n8n starts workflows in response to specific events from PagerDuty, such as incidents being acknowledged, resolved, or services being updated. It acts as a webhook receiver: when configured, it subscribes to selected PagerDuty event types and triggers the workflow whenever those events occur.

Common scenarios:

  • Automating incident management processes (e.g., notifying teams in Slack when an incident is triggered).
  • Logging PagerDuty events into other systems (like databases or ticketing tools).
  • Orchestrating follow-up actions when services are created, updated, or deleted in PagerDuty.

Practical example:
If you want your n8n workflow to run every time an incident is resolved in PagerDuty, you would use this node, select the "Incident Resolved" event, and connect subsequent automation steps.

Properties

Name Type Meaning
Authentication options Selects the authentication method for PagerDuty API access. Options: "API Token" or "OAuth2".
Scope options Limits which events trigger the node: "Service", "Team", or "Account". Determines if filtering is by service, team, or all account events.
Team Name or ID options Specifies the team to filter events by. Required if "Scope" is set to "Team". Can be chosen from a list or entered via expression.
Service Name or ID options Specifies the service to filter events by. Required if "Scope" is set to "Service". Can be chosen from a list or entered via expression.
Events multiOptions Selects which PagerDuty event types will trigger the workflow (e.g., "Incident Acknowledged", "Service Created"). At least one must be selected.
Options → Custom Headers collection Allows adding custom HTTP headers to outgoing webhook requests. Each header has a "Name" and "Value".
Options → Include Headers and Query Parameters boolean If enabled, the output will include the full request details (headers and query parameters) along with the body.

Output

  • By default, the node outputs the JSON body of the incoming PagerDuty webhook event.
  • If Include Headers and Query Parameters is enabled or any custom headers are set, the output will be an object containing:
    • body: The main event payload from PagerDuty.
    • headers: All HTTP headers received with the webhook.
    • query: Any query parameters included in the webhook URL.

Example output (with full request enabled):

[
  {
    "body": { /* PagerDuty event data */ },
    "headers": { /* HTTP headers */ },
    "query": { /* Query parameters */ }
  }
]

Example output (default):

[
  {
    /* PagerDuty event data */
  }
]

Dependencies

  • External Services: Requires a PagerDuty account with API access.
  • Authentication: Needs either an API Token or OAuth2 credentials configured in n8n.
  • n8n Configuration: The instance must be accessible from the public internet (not localhost) for PagerDuty to deliver webhooks. Use a tunnel or deploy on a public domain.

Troubleshooting

  • Webhook not triggering:

    • Ensure your n8n instance is publicly accessible. PagerDuty cannot reach localhost.
    • Check that the correct events and scope are selected.
    • Verify that the webhook subscription was successfully created in PagerDuty.

  • Error: "The Webhook can not work on 'localhost'..."

    • This means your n8n instance is running locally and is not reachable by PagerDuty. Use --tunnel or deploy n8n to a server with a public IP/domain.

  • Error: "PagerDuty webhook subscription response did not contain the expected data."

    • Indicates a problem creating the webhook subscription. Double-check your credentials and permissions in PagerDuty.

  • Missing events:

    • Make sure the correct "Events" are selected and that the "Scope" matches the intended service/team/account.

Links and References

Discussion