# Add Periodic Incident Progress

Automatically posts recurring progress updates to Slack or Microsoft Teams on an active incident at a configured cadence.

## Description

The Add Periodic Incident Progress incident workflow action automatically posts progress updates in Slack or Microsoft Teams on active incidents at your configured cadence (default: every 15 minutes), keeping responders and stakeholders informed of what changed since the last update. It's designed for teams that want regular, low-toil status pings without manual check-ins.

Read more about Periodic Incident Progress in the [PagerDuty AI User Guide](/ai-automation/advance/user-guide#periodic-incident-progress-pip). 

> **Multiple Workflows:** If multiple incident workflows trigger the Periodic Incident Progress action on the same incident, **the first executed workflow's settings will be applied**. Subsequent workflows attempting to activate PIP on the same incident will not override the initial settings.

## Instructions

> **Availability:** See the [Incident Workflow Actions Overview table](/workflow-actions) for the plans this workflow is available on.

> **Prerequisites:** This action requires [PagerDuty AI](/ai-automation/advance), plus either the [Slack](/integrations/slack-integration-guide) or [Microsoft Teams](/integrations/microsoft-teams) integration to be enabled and configured.

1. If you have not done so already, please follow our instructions to [Create an Incident Workflow](/ai-automation/automation/incident-workflows#create-an-incident-workflow).  
2. When you are prompted to [add actions](/ai-automation/automation/incident-workflows#add-actions), select **Add Periodic Incident Progress**.  
   - Under **Periodic Incident Progress cadence**, set how often updates are sent. The default is 15 minutes.  
   - Under **Periodic Incident Progress noise level**, select **Yes** to receive updates regardless of changes, or **No** to only receive updates when something has changed.
3. Continue following instructions to **Publish** the Workflow. When the action runs, you will see the **Outputs** listed below.

## Inputs

This action has no inputs.

## Outputs

| Name           | Description                                                                         |
| :------------- | :---------------------------------------------------------------------------------- |
| Result         | Value that shows if the action was successful or not. Either "Success" or "Failed". |
| Result Summary | Brief description of what the action did or if it failed.                           |
| Error          | Brief description that is populated if the action fails.                            |