Slack

{/* Generated by scripts/generate-integration-catalog.mjs. Do not edit by hand. */}

At a glance

  • Availability: Enabled by default.
  • Authentication: OAuth 2.0.
  • Connection: A user authorizes the connection in the provider's consent screen.
  • Scopes: channels:history, channels:read, chat:write, groups:history, groups:read, im:history, im:read, mpim:history, mpim:read, users:read.

Credentials

Set these per environment. See Connect an integration.

These variables are required only when you supply your own OAuth app. If a managed app is available, you can connect without setting them. Provider permissions and consent still apply.

VariableRequiredDescription
SLACK_CLIENT_IDYesSlack App Client ID Docs.
SLACK_CLIENT_SECRETYesSlack App Client Secret Docs.

Setup

  1. Choose who owns the Slack OAuth app: On hosted Veryfront, Slack uses the Veryfront-managed Slack OAuth app: connect Slack from the project's integrations and approve the Slack consent screen, no environment variables needed. Set SLACK_CLIENT_ID and SLACK_CLIENT_SECRET only to use your own Slack OAuth app, which is required for local and self-hosted runs.
  2. Create a Slack app: In the Slack API dashboard, create an app from scratch in a workspace you manage.
  3. Set the redirect URLs and scopes: Under OAuth & Permissions, add these bot token scopes: channels:history, channels:read, chat:write, groups:history, groups:read, im:history, im:read, mpim:history, mpim:read and users:read. Add the redirect URI of the environment that completes the flow: https://api.veryfront.com/oauth/callback/slack for hosted Veryfront, or your app origin followed by /api/auth/slack/callback for a local or self-hosted app. Set SLACK_CLIENT_ID and SLACK_CLIENT_SECRET from the app's credentials.
  4. Distribute the app: To connect workspaces other than the one that owns the app, turn on public distribution under Manage Distribution.
  5. Verify access: Run List Channels (read-only). It returns channels in the connected workspace without changing anything.

Provider notes

  • The connection requests channels:history, channels:read, chat:write, groups:history, groups:read, im:history, im:read, mpim:history, mpim:read and users:read. The scopes are bot token scopes: the connection acts as the app's bot, which must be added to a channel before it can read that channel's history.
  • chat:write is only needed by the tools that post messages.
  • Tools that create, update, send or delete data are marked as writes and need write authority; the other tools are read-only.

Provider API reference.

Tools

ToolAccessDescription
List Channels<br /><code className="reference-identifier">slack__list_channels</code>ReadList channels
Send Message<br /><code className="reference-identifier">slack__send_message</code>WriteSend message
Update Message<br /><code className="reference-identifier">slack__update_message</code>WriteUpdate message
Delete Message<br /><code className="reference-identifier">slack__delete_message</code>WriteDelete message
Get Messages<br /><code className="reference-identifier">slack__get_messages</code>ReadGet messages
Get Thread<br /><code className="reference-identifier">slack__get_thread</code>ReadGet thread
List Users<br /><code className="reference-identifier">slack__list_users</code>ReadList users

Verify the connection

Call a read tool such as slack__list_channels with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.