Slack webhook integration
As an alternative to the OAuth flow, you can connect CoreWeave Alerts to Slack using an incoming webhook URL.Prerequisites
To complete this integration, you need the following:- The Integrations Admin IAM role, assigned through an IAM Access Policy.
- A Slack incoming webhook URL. To create one, follow Slack’s Sending messages using incoming webhooks guide.
Create a Slack webhook integration
- Log in to the CoreWeave Cloud Console.
- From the left navigation menu, select Administration > Integrations, or go directly to the Integrations page.
- In the Slack section, click Create Slack.
- Select the Slack webhook button.
- In the Display name field, enter a recognizable name (for example,
Cluster-Alerts-Webhook). - In the Slack Webhook URL field, enter your Slack incoming webhook URL. The URL must begin with
https://hooks.slack.com/services/. - Click Create integration.
Test the Slack webhook integration
- On the Cloud Console Integrations page, find the Slack webhook integration you created.
- Locate the vertical ellipsis icon on the right side of the integration row. Expand the menu and click Send test. A success message appears in the lower right corner of the Cloud Console.
- In Slack, verify that the test notification message appears in your channel.
- Open the Alert history page. Confirm that the test alert appears with the correct subject, a Delivered status, the Slack webhook integration type, and a timestamp.
Generic webhook integration
You can send CoreWeave Alerts to any HTTPS endpoint using a generic webhook integration. Use this integration to connect to third-party tools, custom dashboards, or internal services.Prerequisites
To complete this integration, you need the following:- The Integrations Admin IAM role, assigned through an IAM Access Policy.
Create a generic webhook integration
- Log in to the CoreWeave Cloud Console.
- From the left navigation menu, select Administration > Integrations, or go directly to the Integrations page.
- In the Webhook section, click Create webhook.
- In the Display name field, enter a recognizable name.
- In the Webhook URL field, enter your HTTPS endpoint URL.
- Optional: To create a signing secret, click Generate signing secret. CoreWeave includes this secret in the
X-CoreWeave-Signatureheader with each request so your endpoint can verify the payload authenticity. Click Download to save the secret, and store it securely. You can’t view the secret again after you create the integration. - Click Create integration.
Webhook payload format
Generic webhook destinations receive aPOST request with Content-Type: application/json. The body has two fields:
| Field | Description |
|---|---|
subject | The alert name. Use this to route or summarize alerts on the receiving end. |
body | The rendered alert message, which includes status (Firing or Resolved), description, and affected resources (node, cluster, zone). |
Test the generic webhook integration
- On the Cloud Console Integrations page, find the generic webhook integration you created.
- Locate the vertical ellipsis icon on the right side of the integration row. Expand the menu and click Send test. A success message appears in the lower right corner of the Cloud Console.
- Verify that your endpoint received the test payload.
- Open the Alert history page. Confirm that the test alert appears with the correct subject, a Delivered status, the Webhook integration type, and a timestamp.
Verify webhook signatures
If you configured a signing secret, CoreWeave sends anX-CoreWeave-Signature header with each webhook request. Use this header to verify that incoming requests are authentic.