Create incident in PagerDuty.
Application
PagerDuty
Inputs (what you have)
Name | Description | Data Type | Required? | Example |
Connected Account | The connected account to use for the request | Connected Account | Yes | |
Title | A succinct description of the nature, symptoms, cause, or effect of the incident | Text (Short) | Yes | |
Service ID | The incident will be created on this service | Text (Short) | Yes | |
The email address of a valid user associated with the account making the request | Yes | |||
Escalation policy ID | Delegate this incident to the specified escalation policy. Cannot be specified if an assignee is given | Text (Short) | No | |
Incident details | Additional details about the incident which will go in the body | Text (Long) | No | |
Incident key | Sending subsequent requests referencing the same service and with the same incident_key will result in those requests being rejected if an open incident matches that incident_key | Text (Short) | No | |
Priority ID | The incident will be created on this service | Text (Short) | No | |
Urgency | The urgency of the incident | Predefined Choice List | No | |
Conference number | Phone numbers should be formatted like +1 415-555-1212,,,,1234#, where a comma (,) represents a one-second wait and pound (#) completes access code input | Text (Short) | No | |
Conference URL | An URL for the conference bridge. This could be a link to a web conference or Slack channel. | Link | No |
Outputs (what you get)
Name | Description | Data Type | Required? | Example |
JSON Output | JSON output returned by the API | Text (Long) | No |
Outcomes
Name | Description |
Success | This status is selected if the job has successfully completed. |
Unsuccessful | This status is selected if the job has completed unsuccessfully. |
Requirements
N/A