Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 06:00 UTC
| 1 | --- |
| 2 | type: "reference" |
| 3 | title: "Slackbot" |
| 4 | description: "Public support knowledge for Slackbot." |
| 5 | category: "auth-config" |
| 6 | visibility: "public" |
| 7 | timestamp: "2026-07-16T00:00:00Z" |
| 8 | tags: |
| 9 | - "slackbot" |
| 10 | --- |
| 11 | # Slackbot |
| 12 | |
| 13 | |
| 14 | ## Use Slack for user actions and Slackbot for bot-token/bot-scope actions |
| 15 | |
| 16 | Slack and Slackbot serve different token models. The Slack toolkit performs actions on behalf of an actual Slack user. The Slackbot toolkit performs actions as a bot and should be used for bot scopes such as `channels:join` or bot-token workflows. For mixed use cases, create separate Slack and Slackbot auth configs rather than combining user and bot scopes in one connection. |
| 17 | |
| 18 | ## Slackbot triggers require the verification token in custom auth |
| 19 | |
| 20 | For Slackbot triggers with custom auth, configure the Slack app verification |
| 21 | token in the auth config, then create a fresh connection after updating the auth |
| 22 | config. The current auth schema does not expose a separate subscription-ID |
| 23 | field, so do not substitute one for the verification token. |
| 24 | |
| 25 | ## Private Slack channels and DMs require extra history scopes |
| 26 | |
| 27 | Slack private-channel and DM access requires additional scopes. Use `groups:history` for private channels, `im:history` for direct messages, and `mpim:history` for multi-person DMs. These scopes are not always included by default and may be limited by Slack plan/provider constraints, so the customer may need a custom Slack app with the relevant scopes. |
| 28 | |
| 29 | ## Slack file downloads use `SLACK_DOWNLOAD_SLACK_FILE` with a Slack file ID |
| 30 | |
| 31 | Slack file content can be downloaded with `SLACK_DOWNLOAD_SLACK_FILE`. The tool needs the Slack file ID, usually starting with `F`. If the customer does not have the file ID yet, use `SLACK_LIST_FILES_WITH_FILTERS_IN_SLACK` first and pass the returned file ID to the download tool. |
| 32 | |
| 33 | ## Slack short auth links are not the OAuth redirect URI |
| 34 | |
| 35 | The short `/api/v3/s/...` auth link is only a shortened connection initiation URL that redirects the browser to Slack. It is not the `redirect_uri` sent to Slack. Configure the static redirect/callback URI shown in the Composio auth config in the Slack OAuth app; either supported v1 or v3 callback URI can be used depending on the auth config. |
| 36 | |
| 37 | ## Use `SLACKBOT_SEND_MESSAGE` to post a bot message |
| 38 | |
| 39 | Use `SLACKBOT_SEND_MESSAGE` to post to a channel, direct message, or private group. Provide exactly one visible content mode: `markdown_text` for normal Markdown content, or `blocks` for a raw Block Kit layout. Use `fallback_text` only with `blocks`. |
| 40 | |
| 41 | ## Slackbot trigger payloads include `connection_id` and `trigger_id` |
| 42 | |
| 43 | Slackbot trigger payloads include identifiers such as `connection_id` and `trigger_id` inside the payload data. Use `connection_id` to map the event back to the connected account involved in the trigger. |