Update Incident
Update an incident in your PagerDuty instance.
Input
| Field | Definition | Type | Required |
|---|---|---|---|
|
Update By |
|||
|
Incident ID |
The unique identifier of the incident. |
Text | TRUE |
|
From |
|||
|
Email ID |
The email address of the user who's responsible for updating the incident. |
Text | TRUE |
|
Incident |
|||
|
Type |
The incident type.
|
Dropdown | TRUE |
|
Status |
The new status of the incident.
|
Dropdown | FALSE |
| Priority | The priority ID. | Text | FALSE |
| Resolution | The resolution for this incident. When you set the incident status to Resolved, the value is added to the incident's Resolve log entry, but isn't displayed in the UI. | Text | FALSE |
| Title | The title of the incident. | Text | FALSE |
| Escalation Level | The escalation level of the incident. | Number | FALSE |
| Assignments |
The assignees of the incident. Copy
|
List of Objects | FALSE |
| Escalation Policy ID | The escalation policy ID. | Text | FALSE |
| Urgency |
The urgency of the incident.
|
Dropdown | FALSE |
| Conference URL | The URL of the conference bridge, such as a link to a web conference or Slack channel. | Text | FALSE |
| Conference Number |
The phone number of the conference call bridge. Format phone numbers as +1415-555-1212,,,,1234#, where a comma represents a one-second wait and the pound symbol completes the access code input. |
Text | FALSE |
Due to a PagerDuty API limitation, if an incident is triggered as incident, it can't be changed to incident_reference. But an incident can be triggered through the API as either type.
Output
| Field | Definition | Type |
|---|---|---|
|
Status Code |
Result of the operation. The connector returns an HTTP status code that indicates whether the action taken by the card succeeded or failed. For example:
For a full list of possible status codes, see HTTP status codes. |
Number |
