ActionPagerDutyUpdated September 2026

How do I create a PagerDuty incident?

Short answer: You can create pagerduty incident in PagerDuty by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the PagerDuty Create PagerDuty Incident action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Create PagerDuty Incident in PagerDuty — start free All 5 PagerDuty actions

Create PagerDuty Incident in PagerDuty — start free

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.

Triggered by

Apps that pair well as the trigger for Create PagerDuty Incident.

Any of these apps can fire this action as part of a workflow.

Google Sheets → PagerDuty

2 Google Sheets triggers

HubSpot → PagerDuty

18 HubSpot triggers

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 run history shows the failed step with its input and the error message PagerDuty returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Create PagerDuty Incident support batch operations?

Run Create PagerDuty Incident inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within PagerDuty's rate limits.

More actions