Skip to main content
CoreWeave Alerts delivers real-time notifications about your clusters, deployments, and operations. This page introduces the two areas you manage in the Cloud Console to control which alerts your organization receives and where they’re delivered:
  • Destinations determine where CoreWeave delivers alerts. In-app delivery is on by default, so alerts appear on the Cloud Console Alert history page without any setup. You can also connect Slack or a webhook to extend delivery outside the Cloud Console. Enabling an additional destination doesn’t disable in-app. Manage destinations on the Integrations page.
  • Alert configuration determines which alerts your organization receives and which destinations each one goes to. Manage subscriptions on the Alert configuration page.
The Alert history page shows delivery status for every destination that received the alert. Click an entry to see each destination, its integration type, delivery status, and timestamp. For the IAM roles required to access these pages, see Before you begin.

​
Destinations

CoreWeave Alerts supports four destination types. In-app delivery is on by default and doesn’t need to be configured.
Your organization can have at most one Slack destination (either Slack OAuth or Slack webhook) and one generic webhook destination at a time. To switch types, you must delete the existing destination before creating a new one.
Each entry on the Alert history page shows the subject, delivery status, and timestamp. Click an entry to see every destination that received the alert.

​
Destination type comparison

​
Alert configuration

On the Alert configuration page, each alert has an independent toggle per destination, including in-app. The page groups alerts by category (such as Distributed File Storage, AI Object Storage, GPU (hardware health and runtime errors), and SUNK) and tags each one with a severity of Critical, Warning, or Info. For each alert, you can do the following:
  • Toggle delivery per destination. Enabling Slack or a webhook is additive. In-app stays on unless you explicitly turn it off.
  • Use Configure all on a category to apply the same destination settings to every alert in that category at once.
An alert row shows Disabled when you turn off all destination toggles for that alert. This is intentional. The alert isn’t delivered until you re-enable at least one destination. For a walkthrough, see Configure alerts.

​
Before you begin

CoreWeave splits access to alerts between two areas, each with its own IAM roles. Grant these through an IAM Access Policy.
The Administrator default policy includes all available roles, including the Notifications and Integrations roles. Principals assigned to it can use CoreWeave Alerts without additional setup. If your organization uses legacy permissions, the admin group doesn’t automatically include the Notifications or Integrations roles. You must create an IAM Access Policy to grant them explicitly.

​
Set up an integration

The following cards link to step-by-step setup guides for each integration type.

Slack OAuth integration

Connect CoreWeave Alerts to your Enterprise Slack workspace using the OAuth authorization flow

Webhook integrations

Connect CoreWeave Alerts to Slack or any HTTPS endpoint using a webhook URL

​
Configure alerts

Configure alerts

Choose which alerts your organization receives and which destinations each one goes to
Last modified on July 10, 2026