Slack Alert Notifications

Use this guide to send DurableStack alert notifications to a Slack channel.

Before you start

• Slack alert dispatch is a Pro feature in DurableStack.
• You need Slack workspace permissions to create or manage an incoming webhook for a channel.
• You need access to the DurableStack app with organization-level integration management permissions.

1) Create a Slack incoming webhook

1. Open Slack incoming webhook docs: https://api.slack.com/messaging/webhooks
2. Create or select a Slack app with incoming webhooks enabled.
3. Add a new webhook URL for the destination channel.
4. Copy the generated webhook URL.

Treat this URL like a secret. Anyone with the URL can post to that channel.

2) Add the integration in DurableStack

1. In DurableStack, go to Workspace > Organizations.
2. Open Manage Integrations for your organization.
3. In Slack Integrations, select Add Slack Integration.
4. Enter:
   • Name: a clear destination label (example: Slack #ops-alerts)
   • Target URL: the Slack incoming webhook URL
5. Save the integration.

Integrations are organization-scoped, so they can be reused across projects in the same organization.

3) Send a test notification

From the Organization Integrations page, click Test on the Slack integration.

• If the test succeeds, Slack should receive a sample alert message.
• If it fails, DurableStack shows an error toast with details.

4) Use the integration in an alert rule

1. Go to Alerts > Manage Alerts for your project.
2. Create or edit a rule.
3. In Dispatch, enable Slack.
4. Choose one of:
   • an existing Slack integration, or
   • Create new integration and save it inline
5. Save the alert rule.

Troubleshooting

• invalid_payload or no_text: usually means the endpoint is not receiving the expected Slack payload path.
• invalid_token, no_active_hooks, or channel_not_found: webhook was revoked, misconfigured, or points to an invalid channel.
• No message received with no visible error: verify you selected the correct organization integration and the integration is enabled.

Security and operations

• Store webhook URLs in secure secret systems during setup and rotation workflows.
• Rotate webhook URLs periodically and after team or channel ownership changes.
• Use integration names that reflect channel ownership and purpose.