Skip to Content

PagerDuty List Incident Activity

Introduction

A PagerDuty List Incident activity, using its PagerDuty connection, retrieves multiple incidents from PagerDuty and is intended to be used as a source in an operation.

Create a PagerDuty List Incident Activity

An instance of a PagerDuty List Incident activity is created from a PagerDuty connection using its List Incident activity type.

To create an instance of an activity, drag the activity type to the design canvas or copy the activity type and paste it on the design canvas. For details, see Creating an Activity Instance in Component Reuse.

An existing PagerDuty List Incident activity can be edited from these locations:

Configure a PagerDuty List Incident Activity

Follow these steps to configure a PagerDuty List Incident activity:

Step 1: Specify Settings

In this step, specify the settings. Each user interface element of this step is described below.

PagerDuty List Incident Activity Configuration Step 1

  • Name: Enter a name to identify the activity. The name must be unique for each PagerDuty List Incident activity and must not contain forward slashes / or colons :.

  • Save & Exit: If enabled, click to save the configuration for this step and close the activity configuration.

  • Next: Click to temporarily store the configuration for this step and continue to the next step. The configuration will not be saved until you click the Finished button on the last step.

  • Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.

Step 2: Review the Data Schemas

Any request or response schemas generated from the endpoint are displayed. Each user interface element of this step is described below.

PagerDuty List Incident Activity Configuration Step 2

  • Data Schemas: These data schemas are inherited by adjacent transformations and are displayed again during transformation mapping.

    The PagerDuty connector uses the PagerDuty REST API v2. Refer to List incidents in the PagerDuty API Reference documentation for information on the schema nodes and fields.

  • Refresh: Click the refresh icon Refresh icon or the word Refresh to regenerate schemas from the PagerDuty endpoint. This action also regenerates a schema in other locations throughout the project where the same schema is referenced, such as in an adjacent transformation.

  • Back: Click to temporarily store the configuration for this step and return to the previous step.

  • Finished: Click to save the configuration for all steps and close the activity configuration.

  • Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.

Next Steps

After configuring a PagerDuty List Incident activity, complete the configuration of the operation by adding and configuring other activities, transformations, or scripts as operation steps. You can also configure the operation settings, which include the ability to chain operations together that are in the same or different workflows.

Menu actions for an activity are accessible from the project pane and the design canvas. For details, see Activity Actions Menu in Connector Basics.

PagerDuty List Incident activities can be used as a source with these operation patterns:

To use the activity with scripting functions, write the data to a temporary location and then use that temporary location in the scripting function.

When ready, deploy and run the operation and validate behavior by checking the operation logs.