Create PagerDuty Incident: PagerDuty action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Title title	string	Required	Title
Service ID serviceId	string	Required	Service ID
Urgency urgency	options	Optional	Urgency. Options: High, Low
Details body	string	Optional	Message body content. Plain text unless the API specifies HTML/markdown.

Sample request

{
  "title": "{{trigger.title}}",
  "serviceId": "{{trigger.serviceId}}",
  "urgency": "{{trigger.urgency}}",
  "body": "e.g. Hi there, thanks for reaching out."
}

Returns

{
  "incident": {
    "id": "P123ABC",
    "title": "Server down",
    "status": "triggered",
    "urgency": "high",
    "incident_number": 42
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Create PagerDuty Incident.

What does the Create PagerDuty Incident action do in PagerDuty?

Opens an incident with title, service, urgency, dedup_key for fan-in. The standard hook for "external monitor detected → page the on-call engineer" workflows.

What inputs does Create PagerDuty Incident require?

Required: Title, Service ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if PagerDuty returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Create PagerDuty Incident support batch operations?

Yes. Run Create PagerDuty Incident inside a Loop node to process arrays. Tiny Command handles PagerDuty's rate limits automatically so you don't have to throttle manually.

More actions