Slack integration

This guide helps an admin install the Landed Slack app and connect a customer Slack channel.

Installing Slack records a workspace-scoped Slack integration installation. Connecting a channel is a separate setup step from workspace settings or from /invite @Landed in Slack. Both entry points create the same customer Slack channel connection. Admins can also review existing Slack channels in bulk and confirm organization matches before anything is connected.

Quick actions

What a Slack installation does

• Lets a Slack admin authorize the Landed Slack app for a Slack workspace.
• Stores the Slack workspace identity and authorization status for Landed admins.
• Allows more than one Slack workspace installation on the same Landed workspace.
• Does not ingest messages or connect channels by itself.

Required Slack scopes

The workspace installation always requests these bot/workspace scopes:

• channels:read
• groups:read
• channels:history
• groups:history
• files:read
• reactions:read
• users:read
• users:read.email

Each Admin Slack Sender Account also needs chat:write to send replies. File replies need the Sender Account to include files:write; reauthorize that Sender Account to add the scope. The workspace installation uses files:read to retrieve files shared in Slack.

Prerequisites

• Admin access in the Landed workspace.
• Permission in Slack to install or approve the Landed Slack app.

Install a Slack workspace

1. Open Integrations in your workspace dashboard.
2. Select Slack.
3. Click Install Slack workspace.
4. Complete Slack OAuth and approve the requested scopes.
5. Confirm the installation appears with status Installed.

You can install additional Slack workspaces from the same page. Repeat authorization updates the existing installation for that Slack workspace.

Connect a customer Slack channel

Connect one channel at a time. The Slack channel ID is the durable connection key; the channel name is display metadata only.

1. Invite @Landed to the Slack channel, or start Connect channel from Slack settings and choose a channel the Landed app is already in.
2. Choose Customer as the channel type. Community and internal types exist in the model but cannot be activated yet.
3. Select an existing organization or create one during setup. Landed does not infer organizations from channel names or participants.
4. Confirm the connection shows the channel, Slack workspace, organization, and status.

A customer Slack channel cannot become active without exactly one explicit organization mapping. The same Slack channel cannot map to two organizations in the same Landed workspace.

/invite @Landed creates a pending connection with the app present. Completing setup in Landed activates that same connection.

Review existing channels in bulk

Use Review channels to list Slack channels that are not yet connected, including pending /invite @Landed rows.

Landed may suggest an organization from:

• Exact configured naming conventions ({externalId} and {slug} by default)
• Known organization external identifiers
• A prior explicit mapping for that Slack channel ID

Each row shows the match reason, confidence, and conflict state. Private channels are actionable only after @Landed is invited. Suggestions never connect a channel or create an organization. Accept, edit, skip, or create an organization for each row, then activate the approved rows. Those rows use the same customer Slack channel connection as the single-channel flow.

If bulk setup is interrupted, reopen Review channels to retry remaining rows. After an explicit mapping exists, later channel-name or organization-slug changes are not treated as authoritative.

Configure exact naming conventions from Naming conventions on a Slack installation.

After install

No Slack channel is connected when installation succeeds. Use Connect channel or /invite @Landed to create a customer Slack channel.