Slack
Search messages, post to channels, manage threads. OAuth via operator-registered Slack app.
Search messages, post to channels, manage threads. OAuth via operator-registered Slack app.
What this connection offers
Complete Slack consent for the intended workspace. Available records and tools depend on that grant. Review channel and message targets before approving external actions.
| Detail | Value |
|---|---|
| Available uses | records, Assistant tools |
| Sign-in | Service sign-in and consent |
| Catalogue identifier | com.slack.mcp |
| Connection scope | user |
| Direction | source |
Connect
- Open Connections, choose to connect a service, and select Slack with the uses listed above.
- Give the connection a recognisable name.
- Complete the service’s sign-in and consent window with the account you intend to use.
- Check the connection status and run a connection test where offered.
- Select this saved connection in the app, workflow step, storage browser, or Assistant task that needs it.
Connection settings
This connector declares no ordinary configuration fields. Its sign-in or managed provisioning flow supplies the access it needs.
Reconnect
If access expires or consent is revoked, open this connection and use its reconnect flow. Finish consent, test access, then rerun the dependent task. Keep the existing connection when possible so workflow references remain valid.
Diagnose a failure
Check the connected account, its permission to the target, the selected folder, table or collection, and the connection’s current status. A successful sign-in is not proof that a particular resource is shared with that account. An empty search or folder page is not necessarily an authentication error. Revoke access when it is no longer needed; deleting the connection can also affect its tools and synced data. See connection lifecycle.