Create Incident
Create a new incident within your PagerDuty instance.
Do not use the New Incident event card and the Create Incident action card together in the same flow. By doing so, you can create a circular reference.
Input
| Field | Definition | Type | Required |
|---|---|---|---|
|
Incident |
|||
|
Service Key |
Key assigned to a service integration to send events to your PagerDuty instance and creates incidents on your service. |
Text | TRUE |
|
Event Type |
One of: trigger, acknowledge, or resolve. |
Dropdown | FALSE |
|
Description |
A short description of the incident. |
Text | TRUE |
|
Client |
The name of the client application that's integrated with your PagerDuty instance. |
Text | FALSE |
|
Client URL |
URL of an integrated application or component. |
Text | FALSE |
|
Incident Key |
A unique key for the incident. |
Text | FALSE |
|
Detsails |
Free-form details from an event in your PagerDuty instance. |
||
|
Ping Time: |
Time (in milliseconds) for PagerDuty's monitoring tools to reach a host. |
Number | FALSE |
|
Load Avg |
Average number of incidents per team. |
Number | FALSE |
|
Contexts |
Additional information such as graphs or images that can be attached to an incident. Only used for trigger events. |
||
|
Type |
Type of context; link or image. |
Dropdown | FALSE |
|
URL |
URL for the context resource. |
Text | FALSE |
| Text |
Text for the context asset that's attached to the incident. |
Text | FALSE |
Output
| Field | Definition | Type |
|---|---|---|
|
Incident Key |
Parameter that identifies the incident to which a PagerDuty trigger event should be applied. An incident key helps prevent duplication of incidents. |
Text |