PagerDuty - New incident trigger

This trigger checks for new incidents in PagerDuty. Checks for new events on every poll interval. Each incident is processed as a separate job.

Input

FieldDescription
Trigger poll intervalSelect from the picklist or input your own value. Choose from how frequently to check for new events.
When first started, this recipe should pick up events fromGet incidents created since the given date/time. Leave empty to get incidents created since the recipe starts. Once recipe has been run or tested, this value cannot be changed. Refer to Triggers to learn more about this input field.

Output

FieldDescription
IDThe incident ID.
TypeA string that determines the schema of the object. This must be the standard name for the entity.
SummaryA short-form, server-generated string that provides succinct, important information about an object suitable for primary labeling of an entity in a client. In many cases, this will be identical to name, though it is not intended to be an identifier.
SelfThe API show URL at which the object is accessible.
HTML URLThe URL at which the entity is uniquely displayed in the Web app.
Incident numberThe number of the incident. This is unique across your account.
Created atThe date and time when this record was created.
StatusThe current status of the incident.
Incident keyThe incident's de-duplication key.
Pending actionsThe list of pending actions on the incident. Each pending action contains the following fields.
  • Type of action
  • Updated at
ServiceThe service object contains the following fields.
  • ID
  • Type
  • Summary
  • Self
  • HTML URL
AssignmentsList of all assignments for this incident. This list will be empty if the Incident.status is resolved.
AcknowledgmentsList of all acknowledgments for this incident. This list will be empty if the Incident.status is resolved or triggered. Each acknowledgment contains the following fields.
  • At
  • Acknowledger
Last status change atThe time at which the status of the incident last changed.
Last status change byThe agent that created or updated this incident. The agent object contains the following fields.
  • ID
  • Type
  • Summary
  • Self
  • HTML URL
First trigger log entryThis object contains the following fields.
  • ID
  • Type
  • Summary
  • Self
  • HTML URL
Escalation policyThis object contains the following fields.
  • ID
  • Type
  • Summary
  • Self
  • HTML URL
TeamsA list of teams involved in the incident's lifecycle. Each team contains the following fields.
  • ID
  • Type
  • Summary
  • Self
  • HTML URL
UrgencyThe current urgency of the incident.

Last updated: