Set up Slack webhook notifications

In your Slack app, activate Incoming Webhooks, choose Add New Webhook to Workspace, authorize the channel, and copy its URL. In CostRadar, open Settings → Alert Channels, paste it into Slack Webhook URL, click Test, check the destination channel, then Save Channels. Never paste a webhook URL into the chatbot. Testing does not save it; Connected means stored, not verified delivery. Growth or Business is required.

Create a Slack Incoming Webhook

1. Open Slack app management, create an app for your workspace, or select an existing app you are authorized to manage. If offered, choose From scratch, name the app, and select the workspace. No custom bot code is needed for this webhook setup.
2. In the app settings, select Incoming Webhooks and turn on Activate Incoming Webhooks.
3. Click Add New Webhook to Workspace, choose the destination channel, and authorize access. For a private channel, you must first be a member of that channel. Workspace policies may require administrator approval; ask the administrator rather than bypassing restrictions.
4. Copy the generated URL from Webhook URLs for Your Workspace. CostRadar supports Slack Incoming Webhooks on hooks.slack.com. A channel link, bot token, or Slack Workflow Builder trigger URL is not a replacement. GovSlack webhook domains are not currently supported by CostRadar.

Connect and test in CostRadar

Webhook alerts require Growth or Business and an account owner who can manage settings. Open Dashboard → Settings → Alert Channels, and paste the URL into Slack Webhook URL. Never paste a webhook URL into the chatbot, support email, or screenshots: it contains a posting credential.

Click Test while the entered URL is present. This sends a real test message; look for it in the selected Slack channel. Then click Save Channels. Testing alone does not save the URL for future alerts. A successful endpoint response is not independent proof of channel receipt; check Slack yourself.

After reloading, Connected and a masked value mean a URL is stored, not that delivery was recently verified. CostRadar does not reveal the saved URL. To replace or retest it, focus the field, paste the full URL from Slack, test, and save. Do not paste the mask. Disconnect removes the CostRadar destination, not the Slack app or webhook.

Troubleshooting Slack webhook notifications

If you cannot create/install the app or authorize the webhook, ask your workspace administrator about app approval and channel access. If a test fails, confirm the webhook has not been revoked, the app remains installed, and the channel is available. Slack can revoke leaked webhook URLs: create a replacement and update CostRadar if necessary.

A webhook is tied to its authorized channel. To change the destination, create/authorize a webhook for the new channel and replace the CostRadar URL; changing a channel name in CostRadar is not supported. If a test appears in the wrong channel, correct the webhook selection before saving.

For repeated failures, email support@costradar.io with the error text, provider name, and approximate test time, without the secret URL. Do not replace the URL's hostname with an IP address or disable security protections.

The chatbot can explain the steps but cannot install the Slack app, send a test for you, contact support, or verify your Slack channel. Future anomaly notifications depend on detection and eligibility; a test is not a billing anomaly and does not guarantee future delivery. Azure cost data and alerts are not real time.

Slack instructions

In Slack Developer Docs, search for “Sending messages using incoming webhooks.”