Slack support

Last updated date:

Connect, reconnect, and troubleshoot Slack without sharing credentials or customer content through support channels.

1. Before you start

  • Choose the Slack workspace and whether the connection is personal or workspace-owned.
  • For workspace setup, use an account allowed to create and install Slack apps and use Seedling's published app manifest.
  • Review every requested read scope before installation and do not add write scopes.
  • Do not send Slack credentials, customer content, personal information, or private record data by email or through an ordinary support ticket.
Slack authenticationSlack's official installation, OAuth, scopes, and token guidance.

2. Connect Slack

  1. Create the Slack app from Seedling's manifest and install it to the intended workspace, or obtain the actor-owned user token for personal setup.
  2. In Seedling, open Connections, select Slack, and choose the matching personal or workspace scope.
  3. Paste the xoxb- workspace token or xoxp-/xoxc- personal token and connect.
  4. Confirm the verified Slack workspace and allow channel, user, message, and file synchronization to complete.

3. Authorization and connection problems

Wrong token type
Use xoxb- for a workspace connection and xoxp- or xoxc- only for the actor-owned personal connection path.
Missing bot scope
Update the Slack app from the current Seedling manifest, reinstall it, and provide the newly issued token.
Private channel missing
Confirm the bot or user token has native access to that conversation; an installed app is not automatically a member of every private channel.

4. Missing or delayed data

  1. Confirm the token still belongs to the verified Slack team ID and has access to the affected conversation.
  2. For private channels, confirm the app or user is a member; for direct messages, confirm the selected token type can access that conversation.
  3. Check whether a message or file was deleted, the app was removed, scopes changed, or the token was rotated.
  4. Allow incremental synchronization and provider retry handling to complete. A temporary provider failure does not delete previously synchronized data.
  5. If the issue remains, contact support@tryseedling.ai with the Seedling workspace, safe timestamps, and non-sensitive provider record identifiers. Do not include credentials or record contents.

5. Rotate or replace access

Never use email or an ordinary support ticket to transfer the old or replacement credential.

  1. Reinstall or rotate the Slack app token, or obtain the replacement actor-owned user token.
  2. Replace the credential on the exact Seedling connection and confirm the same Slack team ID and scope type.
  3. Revoke the previous token in Slack after Seedling verifies the replacement.