Slack integration troubleshooting

Quick links

Fast checks

1. Confirm you are signed in as a Landed admin.
2. Confirm Slack OAuth completes in a single browser tab.
3. Confirm the Slack workspace is not already installed on a different Landed workspace.
4. Use Reauthorize for an existing installation instead of creating a duplicate.
5. Confirm @Landed is in the Slack channel before activating a customer Slack channel.
6. Confirm the channel maps to exactly one organization.

OAuth cancelled or denied

If you close Slack consent or deny the app, Landed returns you to Slack settings and leaves existing installations in place.

Start Install Slack workspace or Reauthorize again to complete authorization.

Slack workspace already installed elsewhere

A Slack workspace can be installed on only one Landed workspace. If you see a conflict, disconnect it from the other Landed workspace or use that workspace instead.

Revoked or disconnected installations

If Slack uninstalls the Landed app or revokes its bot token, Landed marks that installation Revoked. Existing Landed data is not deleted. Use Reauthorize to restore a healthy installation.

If an admin disconnects the installation in Landed, it shows Disconnected until they install or reauthorize again.

Attachment replies need more permission

You can send images and supported files from a Customer Slack Channel Conversation, including a reply with files and no text. The Slack Sender Account needs files:write as well as chat:write. Admins with an older authorization can still send text replies; reauthorize that Sender Account before sending files.

The Slack workspace installation uses files:read to retrieve inbound files. You do not need to reinstall the workspace app just to add files:write to a Sender Account.

Repeat authorization

Reauthorize the same Slack workspace to refresh tokens and scopes without creating a second installation for that Slack team. Reauthorize your Sender Account separately when it needs updated user scopes.

Channel connection

If activation fails because @Landed is missing, invite the Landed app to the channel and try again.

If a channel already has an organization in this Landed workspace, connect a different channel instead of mapping it twice.

/invite @Landed and Connect channel produce the same connection. Complete setup from Slack settings if an invite is waiting for an organization.

Review channels only connects rows you accept, edit, or create. If bulk setup stops partway, open it again to retry the remaining channels. Private channels stay listed until @Landed is invited.

Channel lifecycle and sync health

Slack settings show each customer Slack channel’s Slack workspace, channel name, organization, connection status, last successful sync, and actionable errors.

Channel renames update the display name only. The Slack channel ID stays the connection identity.

Archived, disconnected, or permission-lost channels stop new synchronization and outbound delivery. Disconnecting a channel, uninstalling the Landed Slack app, or revoking authorization does not delete existing Landed conversations, messages, or Slack provenance.

Use Resync to recover missed events after a webhook outage or similar gap. Use Reauthorize for the Slack workspace or your admin Slack authorization without disconnecting the workspace installation. Rate limits, webhook failures, authorization failures, and permanent delivery failures appear on the channel until they are resolved or the channel is reconnected.