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.
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. |
{"title": "{{trigger.title}}","serviceId": "{{trigger.serviceId}}","urgency": "{{trigger.urgency}}","body": "e.g. Hi there, thanks for reaching out."}
{"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.
Any of these apps can fire this action as part of a workflow.