Slack integration

What connects

The connection uses a workspace-installed Slack Bot User OAuth Token. The bot needs chat:write to post and channels:read to list public channels; groups:read is additionally needed when the picker must list private channels.

• A workspace admin creates and installs the Slack app, then provides its Bot User OAuth Token, which starts with xoxb-.
• The destination picker is the workspace authorization boundary: the team chooses which channels IntellaOne may use, and the Slack app must be invited to each destination channel.
• The connection verifies the bot token and channel list; it does not request or use message-history read access.

Information used

Nothing is imported from Slack. The connector reads only the workspace identity and channel listing needed to show eligible destinations; it does not read Slack messages, threads, files, or channel history.

• Public and private channel metadata may appear in the picker when the bot has the relevant Slack scope and membership.
• Archived channels are excluded from the picker.
• The share route uses the title, summary, optional insight, URL, or message that the user submits for that explicit send.

Why it is useful

A rep can share a reviewed, curated industry insight to the Slack channel their workspace authorized without leaving the workflow to copy and paste it. The destination remains visible and controlled by the user.

• Slack is a delivery destination, not a source of buyer or team conversation history.
• Private-channel sharing stays subject to Slack membership, workspace permissions, and the additional private-channel scope.
• The connector does not send CRM updates, alerts, or background notifications through Slack.

How the workflow behaves

Slack activity is on demand. Before posting, IntellaOne rechecks that the selected channel is an enabled authorized destination, then calls Slack's chat.postMessage API with the user-submitted preview.

• A post happens only as the direct result of an explicit user clicking Send.
• The provider's response must confirm the post before IntellaOne reports success and records the remote message identity.
• A failed provider call is surfaced as a failed share and does not become a reported successful post.
• The connection's sync operation only re-verifies the bot credential; it never imports Slack messages or posts on its own.

Prerequisites and limits

A workspace admin must create and install a Slack app, add the chat:write and channels:read bot scopes, add groups:read when private channels need to be listed, and provide the Bot User OAuth Token. The app must be invited to each destination channel. Slack membership, archived channels, provider limits, and workspace policy can prevent a post.

Availability still depends on the provider account, plan, permissions, and application setup; a catalog status is not a guarantee that every account can use every provider feature.

Security and privacy boundaries

Newly saved connector credentials are encrypted before storage.

Connected tools sync server-side under the user's own credentials. Requested permissions and data flows are connector-specific.

Availability still depends on the provider account, plan, permissions, and application setup; a catalog status is not a guarantee that every account can use every provider feature.

Slack has no inbound data path in this integration. The enabled destination list limits where the action may go, and an explicit user action is required each time; IntellaOne does not read message history or post autonomously.

• The bot token is a workspace credential and should be revoked or reconnected in Slack if it is no longer trusted.
• A post succeeds only when Slack accepts the request; an app that is not in a channel can be rejected by Slack.
• A channel being visible in a picker is not a promise that Slack will accept every later post.

Frequently asked questions

Does the Slack integration read message history?

No. Slack is outbound-only here. IntellaOne uses the workspace and authorized channel metadata needed for destination selection, not Slack messages, threads, or history.

Can IntellaOne post to Slack automatically?

No. A user must choose an authorized channel and click Send for each post. The connector has no autonomous posting path.

What is needed to share to a private Slack channel?

The Slack app must be a member of the channel, and the workspace app needs chat:write plus channels:read and groups:read to list private destinations. Slack still decides whether the post is accepted.

What happens if Slack rejects a post?

IntellaOne reports the share as failed and does not present it as successful. The provider error can indicate that the app needs an invitation, a scope, a different channel, or a later retry.