Results stay results until they leave the Reactor. Distribution makes them actionable.
What It Does
Every item in the Pool — whether generated by a Recipe, captured via Live Transcript, or manually added — can be distributed to external channels. Four channels are available:
| Channel | Icon | Mechanism |
|---|---|---|
| ✉ | Opens the default mail client with a pre-filled subject line and body | |
| 💬 | Opens WhatsApp Web with the content pre-encoded as message text | |
| Slack | ⬡ | Sends the content directly to a configured Slack channel via Webhook |
| System | ↗ | Triggers the native OS share dialog (AirDrop, Messages, Notes etc.) |
E-Mail, WhatsApp, and System Share use client-side mechanisms — the content never passes through Reactor servers. Slack uses a server-side relay to forward the message to the configured Webhook URL.
Single Item Distribution
Each Pool card exposes a share menu via its action bar. Click the share icon on a card to see the four channel options. Select a channel — the content of that card is distributed immediately.
If Slack is not yet configured, the Slack option opens the setup dialog instead (see Slack Integration).
Batch Distribution
The Pool toolbar provides batch distribution for all items or a selected subset.
How It Works
- Open the kebab menu (⋮) in the Pool toolbar
- The distribution options appear below the separator
- Each channel shows context-aware labels:
| State | Label (DE) | Label (EN) |
|---|---|---|
| No selection | Alle per E-Mail | Email All |
| Items selected | Ausgewählte per E-Mail | Email Selected |
The same pattern applies to WhatsApp, Slack, and System Share.
Selection Mode
To distribute a subset instead of all items:
- Click the checkmark icon in the Pool toolbar to activate selection mode
- Select individual cards via checkbox
- Open the kebab menu — labels now reflect the selection
- Choose a channel
All selected items are concatenated into a single message, separated by line breaks.
Channel Details
Opens a mailto: link with Brainstorm Reactor Insight as subject and the concatenated content as body. No recipient is pre-filled — the operator chooses the recipient in their mail client.
Opens wa.me in a new tab with the content URL-encoded as text parameter. On mobile devices, this opens the WhatsApp app directly. On desktop, WhatsApp Web handles the share.
Slack
Requires a Webhook URL configured in the Reactor. The content is sent server-side via POST to /api/distribute/slack. A success toast confirms delivery; errors are surfaced as toast notifications.
If no Webhook is configured, the Slack option in the menu opens the Slack setup dialog. See Slack Integration for configuration details.
System Share
Uses the browser-native navigator.share() API. On macOS, this opens the system share sheet (AirDrop, Messages, Notes, Reminders). On mobile, the native share dialog of the OS appears.
If the browser does not support the Web Share API, the content is copied to the clipboard as fallback.
Technical Notes
- Distribution is fire-and-forget for E-Mail, WhatsApp, and System Share. The Reactor does not track whether the recipient received or read the content.
- Slack delivery is confirmed by the API response. A
200status means Slack accepted the message. - Cancelling the System Share dialog does not produce an error — the abort is handled silently.
- Pool items retain their original formatting (Markdown). Channels that do not support Markdown (WhatsApp, Slack) receive plain text.