Slack Integration Guide

Before you start

Permission to install/authorize the app in the intended Slack workspace and to manage the target Data Weaver client's delivery setup.
An operator-configured Slack integration and a destination channel accessible to the app.

Connect Slack from Sources and review Slack authorization. Choose the destination using the channel picker or enter a channel ID manually.
Save a default channel for the selected client. Schedules can choose a different channel explicitly; an all-client report needs an explicit destination rather than silently inheriting a client's default.
Ensure the app has channel access, including membership where required, before enabling delivery.

Channel-list access helps you choose a destination; message-send access delivers the requested briefings/alerts. This connector does not import channel messages.
Feature permissions include channels:read for public channel listing and files:write for private chart-image uploads. Review Slack's consent screen when installing the app. Private channel listing requires appropriate private-channel access; invite the app to the destination where needed.

Data Weaver lists accessible channel identities and sends scoped report text. Where permitted, charts are uploaded as private Slack files rather than public customer-data image URLs.

No analytics sync is needed. Delivery runs when the configured schedule or alert executes; a source sync badge is not proof of successful message delivery.

Missing private-channel permission does not prevent listing public channels. A manual channel ID does not bypass channel access checks.
Without file-upload permission, briefings can use text-based trend fallbacks. Explicit schedule destinations override the client's default channel.

For missing channels, check app membership and channel-list permissions; enter a verified channel ID if needed.
For failed delivery, verify destination/access and the schedule result. Reconnect for revoked authorization or newly granted permissions, not merely to change a default channel.

Remove Slack in Sources to stop the connection being used and initiate remote cleanup. Review schedules that relied on it.
Separately uninstall/revoke the app in Slack's app-management settings for provider-side access removal. Messages/files already delivered to Slack are not recalled by a local disconnect; manage those under Slack's retention/deletion controls.

You stay in control of what you connect. Review how we handle information, request deletion, or contact us.