Connect a Slack webhook

Create, save, test, and secure a supported Slack incoming webhook.

Last checked 21 August 2026

TechDash sends Slack notifications through an incoming webhook that belongs to a Slack app and channel. The webhook URL is a secret because anyone who has it may be able to post to that destination.

Get an incoming webhook URL

Follow Slack's official Sending messages using incoming webhooks guide to create or obtain a webhook for the intended workspace and channel. Slack may change its app-management navigation, available options, or approval flow, so use the current instructions on that page rather than relying on older menu names.

You may need a Slack administrator to approve the app or webhook. For a private channel, make sure the person configuring the webhook is already a member. Copy the resulting URL, which normally begins with https://hooks.slack.com/.

Add it to TechDash

  1. Open Notifications.
  2. Find Slack webhook.
  3. Paste the complete URL. It should begin with https://hooks.slack.com/.
  4. Select Send test.
  5. Confirm Test notification sent. appears in TechDash.
  6. Confirm TechDash test notification. appears in the intended Slack channel.

There is no separate Save button. TechDash saves the field as it changes. Clearing Slack webhook removes the global Slack destination for future sends.

Select How to configure beside the field for TechDash's in-app guidance.

If TechDash rejects the URL

TechDash accepts Slack webhook URLs only when:

  • The scheme is HTTPS.
  • The hostname is exactly hooks.slack.com.
  • The URL can be parsed as a complete URL.

A normal Slack workspace, channel, or browser URL is not a webhook and will not work. TechDash also rejects HTTP endpoints and lookalike subdomains.

Treat the URL as a password. Do not put it in screenshots, tickets, source control, or shared documents. If it is exposed, rotate it in Slack and replace the value in TechDash.

Understand what Slack receives

Slack delivery requires all applicable controls:

  1. Slack webhook contains a valid URL.
  2. Slack is On under Notify for the affected monitored page.
  3. The result is eligible to notify and is not ignored.
  4. TechDash is running and can reach Slack.

Good means a check passed. Good does not open an incident or lower Health Score. A Good result can produce a Slack recovery message when it closes a previously notifiable failure and Notify when a check recovers is On.

Built-in Advisory incidents describe lower-impact concerns and do not post. Warning incidents indicate meaningful risks that may affect visitors, crawling, indexing, reporting, or renewals. Critical incidents indicate the highest likely impact, such as serious availability or certificate problems. Warning and Critical incidents can post. Custom Checks use their own Notify option, so a custom Advisory check can post when explicitly configured to notify.

Sitewide findings use the monitored / page's Slack toggle when available, otherwise the first monitored page's toggle.

Open incidents affect Health Score whether or not Slack is configured: Advisory has weight 1, Warning weight 4, and Critical weight 10. Turning Slack Off does not change incidents or the score. Ignoring a matching check suppresses its incident and all notification channels.

Verify the expected result

The test bypasses severity, page toggles, ignore rules, and recovery policy. Always verify both results: Test notification sent. in TechDash and TechDash test notification. in Slack. If TechDash reports success but Slack shows no message, confirm the channel, recreate or rotate the webhook using Slack's official guide, replace Slack webhook, and test again.

Related articles