Slack and Discord notifications
Send deployment and service updates to your team's existing channels.
Connect Slack or Discord incoming webhooks from the dashboard's Notifications page. An owner or admin configures these workspace integrations.
Connect Slack
- Create an incoming webhook in your Slack workspace and select the destination channel.
- In Openstead, choose Connect Slack.
- Enter a name and the Slack incoming webhook URL.
- Save the enabled connection.
- Open its delivery history and send a test.
Slack URLs must use https://hooks.slack.com/services/.... Use the webhook URL rather than a channel URL or bot token. Treat the webhook URL as a credential.
Connect Discord
Create a webhook in the target Discord channel's integration settings, copy its URL, then save it as a Discord connection in Openstead.
Discord URLs must use https://discord.com/api/webhooks/.... Test the connection after saving. Notifications are sent without activating mentions.
Events and delivery
Channel integrations receive deployment success and failure, service health, and backup events. Messages contain the event title and description. Use custom webhooks when your receiver needs the structured JSON envelope and explicit event subscriptions.
Saving an enabled connection begins delivery of future events. Historical messages are not replayed. Delivery retries up to eight attempts when the provider returns a failure or cannot be reached.
Troubleshooting
| Symptom | Action |
|---|---|
| The URL is rejected | Use the provider's incoming-webhook URL on its supported host. |
| A test fails | Check that the webhook is active and can post to the selected channel. |
| HTTP 403 or 404 | The destination may have been revoked or removed; generate a replacement. |
| HTTP 429 | Let delivery retry after provider throttling and reduce redundant destinations. |
| Messages reach the wrong channel | Replace the webhook with one belonging to the intended channel. |
Use delivery history to confirm that a test actually reached the provider. Disabling a connection stops pending delivery; an already-sent request may still be received.