Connect Slack channels for agent alerts and automations
Workspace administrators can connect Slack channels in Settings → Integrations and then use those channels as a delivery destination for agent run alerts and automation actions. ## Before you begin - You must be a workspace owner or administrator. - You need a Slack incoming webhook URL for the channel you want to connect. Create one from the Slack API apps page for your workspace. Hub stores webhook URLs in server-only collections. They are never returned to the browser or visible in the Hub interface after you save them. ## Connect a Slack channel 1. Open **Settings** in your workspace. 2. Select **Integrations**. 3. Find the **Slack** row and select it to expand its settings. 4. Select **Connect channel**. 5. Enter the webhook URL for the channel. 6. Give the connection a recognisable label (for example, `#alerts` or `#sales-team`). The label field has a help hint explaining that Slack chooses the destination channel when you create the webhook — the label is only used in Hub. 7. Save. The connection appears in the Slack section with its label and a labelled status badge. You can add multiple channels and manage or remove each one independently. ## Integrations page layout The **Settings → Integrations** page lists all integrations — ChatGPT, Slack, GitHub, Outlook and Stripe — in a single compact list. Each row shows: - The integration name and a brief description. - A **Status** badge indicating the current connection state (for example, *Connected*, *Not connected*, *Checking…*, or *Needs attention*). Select any row to expand it and see connection details and settings. Expanded sections use animated disclosure rows that retain draft values when collapsed and keep hidden controls out of keyboard navigation. ## Route agent run alerts to Slack Once a channel is connected, you can send agent notifications there: 1. Open **Agents** and select the agent you want to configure. 2. Select **Notifications**. 3. Choose **Notify when**: every completed run, or failures only. 4. Under **Delivery**, select a connected Slack channel alongside or instead of in-app delivery. 5. Save the notification settings. Slack delivery is independent of in-app notifications — you can use one, the other, or both. Delivery uses a shared outbox that: - Deduplicates messages using deterministic run IDs, so a retry never sends the same alert twice. - Retries automatically for Slack rate limits and temporary server failures. - Records delivery history in the Notifications settings so you can confirm each message was sent. ## Add a Send Slack message action to an automation You can send a templated Slack message as a step in an automation — for example, when a new lead arrives. 1. Open **Settings → Automations** (or open an existing automation). 2. Add a **Send Slack message** action step. 3. Select the connected channel to send to. 4. Write the message, using template variables such as `{{record.subject}}` or `{{record.url}}` to include record details. 5. Save and activate the automation. Send Slack message is available in **Hub-assisted automations**. Custom workflow rules continue to use their existing action canvas. ## Delivery history and failure handling Delivery history for each Slack connection is visible in its expanded row under **Settings → Integrations**. The status badge distinguishes between loading, disconnected and error states so you can identify connectivity issues at a glance. If a webhook becomes invalid (for example, if it is revoked in Slack), Hub marks the connection as disconnected. Update the webhook URL under Integrations to restore delivery. ## What is not sent automatically - No Slack messages are sent for events you have not explicitly configured. - Existing in-app notifications continue unaffected when you add a Slack channel. - Webhook URLs are never exposed in run history, notifications or any browser-accessible API response.