One Webhook URL. Direct delivery. No middleware.
What It Does
The Slack Integration connects the Reactor's Pool distribution system to a Slack workspace. Once configured, Pool items can be sent to a Slack channel with a single click — individually from a card or in batch from the Pool toolbar.
The integration uses Slack's Incoming Webhooks mechanism. No Slack App installation, no OAuth flow, no bot token management. One URL — that is the entire configuration.
Setup
Prerequisites
- A Slack workspace where you have permission to create Incoming Webhooks
- Access to the Reactor's Moderator Settings
Creating the Webhook in Slack
- Navigate to api.slack.com/apps
- Create a new app (or select an existing one)
- Under Features, select Incoming Webhooks
- Activate Incoming Webhooks
- Click Add New Webhook to Workspace
- Select the target channel
- Copy the generated Webhook URL — it follows the pattern:
https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXXConfiguring the Reactor
The Slack Webhook URL is configured directly within The Pool:
- In the right sidebar, open the Pool tab.
- On any saved Pool card or via the batch action bar, click the share menu and select "Setup Slack…" (
Slackicon). - Paste your incoming Webhook URL and save. The configuration is securely stored in your user profile.
Testing the Connection
The setup dialog includes a Test button. Click it to send a test message to the configured channel. If the message arrives, the integration is live.
A success confirmation reads: "Dieser Slack-Webhook wurde erfolgreich mit deinem Brainstorm Reactor Moderator-Dashboard verknüpft."
How Distribution Works
With the Webhook configured, Slack appears as an active channel in every share menu — both on individual Pool cards and in the batch distribution toolbar.
When you send content to Slack:
- The Reactor sends a
POSTrequest to/api/distribute/slack - The server-side relay forwards the content to the Slack Webhook URL
- Slack delivers the message to the configured channel
- A toast confirms successful delivery
The message appears in Slack as plain text from the Incoming Webhook app. No formatting, no embeds — the raw insight, delivered immediately.
Batch Distribution
The Pool toolbar's kebab menu includes a Slack All (or Alle an Slack) option. This concatenates all Pool items (or the current selection) and sends them as a single Slack message.
| Scenario | Label (DE) | Label (EN) |
|---|---|---|
| No selection active | Alle an Slack | Slack All |
| Items selected | Ausgewählte an Slack | Slack Selected |
| Not configured | Slack einrichten… | Setup Slack… |
Scope and Persistence
The Webhook URL is stored per user in the Reactor's settings backend. It persists across sessions and page reloads. The integration is independent of any specific tool — it works with Pool items from any source (Recipes, Live Transcripts, manual entries, AI summaries).
Security
- The Webhook URL is stored server-side and never exposed in client-side code after initial configuration
- Distribution requests pass through the Reactor's API relay — the Webhook URL is not called from the browser
- Slack Incoming Webhooks are write-only — the Reactor cannot read channel history or user data
- The URL pattern is validated against
https://hooks.slack.com/services/before saving
Removing the Integration
To disconnect Slack, clear the Webhook URL field in the Moderator Settings and save. The Slack option in share menus will revert to the setup prompt.