Connect Slack to V7 Go

🚧

Preview

This feature is new and evolving. Details on this page may change as we
improve it.

V7 Go connects to Slack through Slack's MCP server, so the agent can search
public and private channel messages, channels, and files, and send messages, from chats, playbooks,
and workflows.

Connect with the official V7 Go app

🚧

Marketplace publication pending

The official V7 Go app is being prepared for Slack Marketplace review and is not yet published. External customers may be blocked from using it until publication. If you need to connect now, use the custom OAuth setup below with an internal Slack app.

Choose the region where your V7 Go workspace is hosted:

Connect Slack in V7 Go — EU

Connect Slack in V7 Go — US

These links open V7 Go. Sign in and select your workspace, then:

1. Open Integrations → MCP Connectors → Slack.
2. Click Connect.
3. Choose your Slack workspace and review the permissions requested by V7 Go.
4. Complete Slack's authorization and return to Go. Your Slack workspace administrator may need to approve the app.

After the official app is published, customers can use this flow without creating a Slack app or supplying a Client ID or Client Secret. A V7 Go account is required. Use your workspace's EU or US environment throughout the connection.

The connection follows the authorizing user's Slack permissions. AI-generated answers and summaries can contain errors; review them before relying on them.

The official app supports public and private channel message search and history. Direct-message and group-direct-message search and history are excluded from this release. Sending messages remains available with the permissions you authorize.

Custom OAuth setup

Use this option if your organization manages its own internal Slack app. Only internal apps or apps published to the Slack Marketplace may use Slack's MCP server; unlisted apps are blocked. Enter your app's Client ID and Client Secret in the Go connect card.

1. In Go, open Integrations → MCP Connectors → Slack — or ask the agent
   in chat to use Slack. A connect card appears.
2. In Slack API, create a new app From
   scratch. Keep it as an internal app (or later publish it to the
   Slack Marketplace).
3. On OAuth & Permissions, add a User Token Redirect URL equal to
   the callback URI on the card. Bot-token redirect URLs are the wrong
   field.
4. Add the user token scopes listed on the card (search, history,
   channel read, file and user lookup, and chat:write). Bot-token scopes do not count.
5. A workspace admin may need to approve the app under Slack
   Manage apps.
6. Copy the Client ID and Client Secret from Basic Information
   into the card. Never paste them into chat.
7. Press Connect and complete Slack's authorization popup.

Troubleshooting

• "unlisted apps prohibited". Switch the app to internal, or publish
  it to the Slack Marketplace, then reconnect.
• "No scopes requested". User token scopes were not added. Add the
  scopes from the card on OAuth & Permissions, then reconnect.
• Admin approval pending. A workspace admin must approve the app under
  Manage apps. Reconnecting before that fails the same way.
• Redirect URI mismatch. Paste the card's callback URI into User
  Token Redirect URLs, not Bot Token Redirect URLs.

For messages Go shows on the connect card, see
MCP connector errors.

FAQ

Who can connect? A V7 Go user who is allowed to authorize apps in their Slack workspace. Once the official app is published, customers can connect without custom OAuth credentials. Until then, use an internal Slack app through the custom OAuth setup above. Slack administrator approval may still be required.

Is the connection shared? Connections follow the sharing policy on the
connector page.

What can the agent do? Search public and private channel messages and files, retrieve channel history, and send messages,
within the user token scopes you granted. Ask "what Slack tools do you
have?" for the live list.