Create a webhook for your Slack channel, paste it privately into Integrations and send a test. Saving the connection is not delivery evidence: check the message in Slack too.
Before you start
You need the owner or admin role in Site Hush. A viewer can open the help but cannot connect or test. Start with a test channel before using your operations channel.
Your workspace may require app approval. Ask its administrators for help if installation is restricted.
Create the webhook in Slack
- Open your Slack apps and create or select an app in the right workspace.
- Enable Incoming Webhooks.
- Choose Add New Webhook to Workspace, select the channel and authorise. Join a private channel first.
- Copy the address privately. Refer to Slack's official webhook guide if needed.
The webhook address is a secret. Never paste it into chat, support tickets, screenshots or a code repository. If exposed, revoke it in Slack and create a new one.
Connect and test in Site Hush
- Select the correct account and open Integrations.
- Enter a descriptive name and paste the address into Slack webhook address.
- Choose the incident and recovery notifications the channel should receive. Choose Connect.
- Choose Test on the saved integration. Do not start a second test while it is waiting.
- Read Latest recorded test and check the same test channel in Slack.
The app stores the address encrypted and never shows the saved value again. An earlier successful test is history, not new confirmation. A colleague's later test does not confirm the result of your own request.
If tests work but incident notifications are missing
Check all three levels: account Notifications for the whole account, monitor Send notifications for this monitor, and the integration's active state/notification choices. An integration test checks the channel separately, even when account incident notifications are off.
Incidents are recorded regardless of notification settings. Pausing or administratively closing an incident is not verified recovery and must not be interpreted as a RECOVERED notification.
If the test fails
Read the persistent error result. Check the channel, app approval and whether the webhook still exists. Reconnect using a new private address if needed. Do not share the secret when reporting a problem.
Next step: understand incidents and recovery. Only use your own approved test website for a real DOWN/RECOVERED exercise, never interrupt a customer's website.