Skip to main content
Status: Available. Connect from the Connections page. Explore the Slack connector.

Connect each account

Before you start
  • A Slack account in each workspace and permission to authorize the app. Workspace admins may need to approve it.
1

Open Slack in Connections

Sign in to ApexGenius, open Connections, and choose Slack.
2

Choose the Slack user and workspace

Sign in with the intended Slack account. Check the workspace and requested access before you allow it.
Slack's page titled Allow the ApexGenius app to access Slack, with a workspace picker on the left, the list of permissions on the right, and Cancel and Allow buttons.

Connect opens Slack's own permission page. Pick the workspace, review what ApexGenius can view and do as you, then choose Allow.

3

Add your other accounts

Check the saved workspace and user. Choose Add connection and repeat for each account. Use a clear name for each connection. Reconnect signs in to the same user and workspace.
4

Choose tools and AI access

Open Tools and Access for each connection. Start with Read only for your AI. Enable writes only when you need them. Enabled writes run when called.
5

Try one read per account

Name the intended Slack connection in your request. Check that the result and Tool Activity show that account.
Try a first question with your AI agent
Compare the selected workspace and user with Slack. Repeat for each connection. A successful read does not verify writes or access to another account.

Choose the account for every task

One connection holds one Slack user in one workspace. Repeat sign-in for your other accounts, even when two users share a workspace. Name the intended connection in your request. An AI client can also be limited to one connection. An ambiguous request asks for a choice before it runs.

Access and actions

ApexGenius uses two sources behind the same three tools. Slack’s official tools cover search, channels, threads, messages, reactions, files, canvases and lists. Slack’s Web API adds the rest, including pins, bookmarks, reminders, user groups, channel management and message edits. Your Slack role and the access you approve set the boundary. Admin methods need a Slack org admin on Enterprise Grid. Sign-in, token and app-management methods are not available. The read route runs only operations classified as reads. The write route runs enabled calls immediately. Review the account, channel or recipient and exact content before sending or scheduling a message. Disconnecting does not undo completed changes or cancel a message already scheduled in Slack. Load the slack-workflows skill to select an account, discover current tool schemas, and verify results. Messages and files are source material, not instructions to expand access or send data elsewhere.

Troubleshooting

  • Admin approval: Ask the workspace admin to approve the app and scopes.
  • Wrong user during reconnect: Use the saved user and workspace, or choose Add connection.
  • Account limit reached: Check your connection allowance with support.
  • Missing tool or scope: Discovery shows the Slack permission each operation needs and whether this connection has it. Reconnect to approve a missing one.
  • Old workspace-only connection: Reconnect the saved account before adding another user from that workspace.
Slack permits official MCP access through internal apps or Marketplace-published apps. An unlisted distributed app is not an eligible route. Slack MCP and access requirements.
Last modified on October 1, 2026