Use this event to trigger a flow when an incident is triggered in 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 create a circular reference.
It is recommended that you preserve the default polling value of Every 5 minutes for this card. If you increase the time value for polling intervals, you may run the risk of not returning all of the records that are processed in that period. The PagerDuty connector supports a maximum of 1,000 records between polls.
No options available.
|Name||A short description of the incident||String|
|Incident Key||Unique key that identifies the incident to which a PagerDuty trigger event should be applied. An incident key helps prevent duplication of incidents.||String|
|Incident Number||A numeric identifier automatically assigned to an incident in your PagerDuty instance||Number|
|Incident ID||Identifier that you can assign to an incident||String|
Date and time when the object was created.
|Status||State of the incident:
Feature that determines how a team is notified based on the criticality of an incident:
|Type||Type of integration that can be used to trigger an incident. The type can be
|URL||URL to view an incident in your PagerDuty instance||String|
|Name||Name of a service against which incidents are opened. For example, an application or component.||String|
|Service ID||Unique identifier of the of a service||String|
|Type||Type of integration for the service. Type can be
|URL||URL of an integrated application or component within your PagerDuty instance||String|
|Escalation Policy ID||Escalation policy identifier. An escalation policy ensures the right people are notified at the right time when an incident occurs.||String|
|Type||Type of escalation policy. The type can be
|Summary||A description of the escalation policy, including user and schedule targets||String|
|URL||URL to view an escalation policy within your PagerDuty instance||String|