# Manage Control Center Alert Actions for Confluent Platform After creating a [trigger](triggers.md#new-edit-trigger-form), you are prompted to create or select an existing action; or you can click **I’ll do this later**.  The Actions page is blank when there are no actions defined. Clicking the **Actions** tab shows a summary of all configured actions:  Use the Actions page to: - Create an action using the **+ New action** button. - View and sort a summary of actions, their maximum frequency, number of associated triggers, and status. - Search for an action. - [Pause and resume](#pause-resume-alerts-actions-ui) all enabled actions. The Status column indicates whether a particular action is individually enabled, disabled, or paused. The Pause all actions toggle indicates whether all enabled actions are currently paused. - [Edit](#edit-alert-action) or [delete](#delete-alert-action) an existing action. ## New or edit Action form Complete the Action form to specify the type of notification you want to receive when a defined trigger has fired. Supported notification actions include: - email - PagerDuty - Slack - Generic webhook    Prerequisites: - Define a [trigger](triggers.md#new-edit-trigger-form) for an action. - Configure the prerequisites for each type of action. ### Action field descriptions A description of each action field follows. Most fields are required, as noted by the asterisks in the UI. Action name : A unique name for the action (for example: `email DevOps on call`).
Uniqueness is not enforced. Use unique and descriptive names to avoid confusion. Enabled/Disabled : You might want to temporarily disable actions. Choose whether an action is currently enabled or disabled with this field. Triggers : One or more triggers that will cause the action to execute. Refer to [Control Center Alerts for Confluent Platform](concepts.md#concepts-alerts) for more information. Action : The type of action to perform:
- **Send email** - **Send PagerDuty notification** - **Send Slack notification** - **Send Webhook notification**
Recipient email address (email action only) : The email address or addresses associated with this action. A message is sent to the specified email address each time the action is executed. Separate multiple email addresses with a comma.
Webhook URL (Slack and generic webhook notifications only) : Webhook options for Slack and generic webhooks:
- The URL generated in Slack. The **Generate incoming webhook URL** links to [Slack instructions](https://api.slack.com/incoming-webhooks). - The URL onto which you want the alert payloads to be dispatched.
Slack Username (Slack webhook notification only) : Optional. If configured, overrides the username configured by default when the webhook was set up in Slack. The username represents the user who sent the alert. For example: `@username`.
Slack Channel (Slack webhook notification only) : Optional. If configured, overrides the channel configured by default when the webhook was set up in Slack. The channel is the destination for the notification in Slack. For example: `#mychannel`. You can configure this field to send a notification to a Slack channel or a direct message to a Slack user.
PagerDuty Routing Key (PagerDuty action only) : The Integration key from PagerDuty. Refer to the [PagerDuty documentation](https://support.pagerduty.com/docs/services-and-integrations) to generate an integration key.
Event severity (PagerDuty action only) : The severity for auto-created PagerDuty events: Critical, Error, Info, or Warning. Subject (not for generic webhooks) : The subject line of the notification associated with the action. Per hour (not for generic webhooks) : Choose a frequency from the pull-down menu for how often notifications should be sent. Set in conjunction with **Max send rate**. Renotify every : Specify how often you receive alert notifications for unresolved alerts. ## Pause and resume all alerts actions Pause all enabled alerts when necessary for maintenance or troubleshooting reasons. The existing settings of individual actions that are enabled or disabled is respected during pause and resume. Any trigger conditions that are met and fired are ignored while paused, and all enabled actions associated with a trigger are suppressed. When ready, resume alerts again. The next time a trigger condition fires, its enabled actions send their corresponding alerts. #### WARNING If you stop and restart Confluent Platform or Control Center, the paused actions resume and become active again. Click the **Pause all actions** toggle to pause the actions again. **To temporarily pause all alerts actions:** 1. Click the Alerts bell icon in the top banner. The **Alerts** page opens to the **History** tab by default. 1. Click the **Actions** tab. 2. Click the **Pause all actions** toggle. You are prompted to confirm pausing all currently enabled actions. 3. Click **Confirm**. A check mark in the toggle indicates all enabled actions are currently paused.  **To resume paused alerts actions:** 1. Click the Alerts bell icon in the top banner. The **Alerts** page opens to the **History** tab by default. 1. Click the **Actions** tab. 2. Click the **Pause all actions** toggle. You are prompted to confirm resuming all currently paused actions. 3. Click **Confirm**. The **Pause all alerts** toggle is deactivated. ## Disable or enable an individual alert action When you create an action, it is enabled by default. Disable an action if you do not want it to be active. Pause and resume actions respect the disabled setting for an action. Resuming paused alerts does not activate disabled alert actions. **To disable an action:** 1. Click the Alerts bell icon in the top banner. The **Alerts** page opens to the **History** tab by default. 1. Click the **Actions** tab. 2. In the **Name** column, click the action you want to disable. 3. Click **Edit**. 4. Click the **Enabled/Disabled** action toggle.  The toggle switches off and the action displays as Disabled in the Status column. 5. Click **Save**. To enable an action again, repeat the procedure and click the **Enabled/Disabled** toggle again. ## Edit an alert action 1. Click the Alerts bell icon in the top banner. The **Alerts** page opens to the **History** tab by default. 1. Click the **Actions** tab. 2. Click the name of the action. 3. Click **Edit**. 4. Make the changes you want to the action fields. Note that when you are running Control Center in [Reduced infrastructure mode](../overview.md#reduced-infra-mode), and you delete an incompatible trigger, it will no longer display in the Triggers drop-down. 5. Click **Save**. ## Delete an alert action 1. Click the Alerts bell icon in the top banner. The **Alerts** page opens to the **History** tab by default. 1. Click the **Actions** tab. 2. Click the name of the action. 3. Click **Delete**. 4. Confirm deleting the action.