All connectors

Slackbot

98 tools · Team Chat · Team Collaboration

Slackbot gives agents workspace-wide read access to a Slack workspace on behalf of the installing user - search messages and files, browse channel and thread history, and look up users and channels - while continuing to post and react as the bot. Includes direct messages and user email addresses so agents can search across DMs and resolve users by email.

Connect Slackbot

  1. Open Slashspace and go to Settings, then Connectors.
  2. On Discover, search for Slackbot and click Connect.
  3. Sign in to Slackbot in your browser. Slashspace updates when the account is connected.
  4. Then ask for what you need in any Agent mode chat. Slackbot is on in every chat unless you switch it off.

What your chats can do

98 tools from Slackbot.

  • Add call participantsRegisters new participants added to a Slack call.
  • Add reaction to messageAdds a specified emoji reaction to an existing message in a Slack channel, identified by its timestamp; does not remove or retrieve reactions.
  • Add a remote fileAdds a reference to an external file (e.g., Google Drive, Dropbox) to Slack for discovery and sharing, requiring a unique `external_id` and an `external_url` accessible by Slack.
  • Archive a Slack conversationArchives a Slack conversation by its ID, rendering it read-only and hidden while retaining history, ideal for cleaning up inactive channels; be aware that some channels (like #general or certain DMs) cannot be archived and this may impact connected integrations.
  • Close conversation channelCloses a Slack direct message (DM) or multi-person direct message (MPDM) channel, removing it from the user's sidebar without deleting history; this action affects only the calling user's view.
  • Create a reminderCreates a Slack reminder with specified text and time; time accepts Unix timestamps, seconds from now, or natural language (e.g., 'in 15 minutes', 'every Thursday at 2pm').
  • Create Slack CanvasCreates a new Slack Canvas with the specified title and optional content.
  • Create channelInitiates a public or private channel-based conversation in a Slack workspace. Immediately creates the channel; invoke only after explicit user confirmation.
  • Create Slack ListCreates a new Slack List via `slackLists.create`. Provide a `name` and, optionally, a `description_blocks` description and a `schema` of typed columns. You can instead copy an existing List's structure with `copy_from_list_id` (and its rows via `include_copied_list_records`), or enable task-tracking columns with `todo_mode`. Returns the new List's `list_id`. Requires a user token with the `lists:write` scope.
  • Create Slack List itemCreates a new item (row) in a Slack List via `slackLists.items.create`. Set initial cell values with `initial_fields`; text columns require Block Kit `rich_text` (a plain string is wrapped automatically). Optionally duplicate an existing row with `duplicated_item_id` or create a subtask with `parent_item_id`. Requires a user token with the `lists:write` scope.
  • Create a Slack user groupCreates a new User Group (often referred to as a subteam) in a Slack workspace.
  • Customize URL unfurlCustomizes URL previews (unfurling) in a specific Slack message using a URL-encoded JSON in `unfurls` to define custom content or remove existing previews.
  • Delete Slack CanvasDeletes a Slack Canvas permanently and irreversibly. Always confirm with the user before calling this tool.
  • Delete a file by IDPermanently deletes an existing file from a Slack workspace using its unique file ID; this action is irreversible and also removes any associated comments or shares.
  • Delete file commentDeletes a specific comment from a file in Slack; this action is irreversible.
  • Delete Slack List accessRevokes sharing access on a Slack List via `slackLists.access.delete`. Provide the `list_id` and EXACTLY ONE of `channel_ids` or `user_ids` (they are mutually exclusive) to remove access for those channels or users. Requires a user token with the `lists:write` scope.
  • Delete Slack List itemDeletes an item (row) from a Slack List via `slackLists.items.delete`. Identify the List with `list_id` and the row to remove with `id`. Deletion is permanent and cannot be undone. Requires a user token with the `lists:write` scope.
  • Delete multiple Slack List itemsDeletes several items (rows) from a Slack List in one call via `slackLists.items.deleteMultiple`. This operation is ALL-OR-NOTHING: Slack returns a single `{"ok": true}` on success or `{"ok": false, "error": ...}` on failure, with NO per-item result array, so partial state cannot be reported. On failure, treat the whole batch as not deleted and retry the entire batch. Requires a user token with the `lists:write` scope.
  • Delete a Slack reminderDeletes an existing Slack reminder, typically when it is no longer relevant or a task is completed; this operation is irreversible.
  • Delete a message from a chatDeletes a message, identified by its channel ID and timestamp, from a Slack channel, private group, or direct message conversation; the authenticated user or bot must be the original poster.
  • Delete scheduled chat messageDeletes a pending, unsent scheduled message from the specified Slack channel, identified by its `scheduled_message_id`.
  • Disable a Slack user groupDisables a specified, currently enabled Slack User Group by its unique ID, effectively archiving it by setting its 'date_delete' timestamp; the group is not permanently deleted and can be re-enabled.
  • Download Slack fileTool to download Slack file content and convert it to a publicly accessible URL. Use when you need to retrieve and download files that have been shared in Slack channels or conversations.
  • Edit Slack CanvasEdits a Slack Canvas with granular control over content placement. Supports replace, insert (before/after/start/end) operations for flexible content management.
  • Share file public urlEnables public sharing for an existing Slack file by generating a publicly accessible URL; this action does not create new files. Once enabled, the file is accessible to anyone with the URL — verify intent before sharing sensitive or confidential files.
  • Enable a user groupEnables a disabled User Group in Slack using its ID, reactivating it for mentions and permissions; this action only changes the enabled status and cannot create new groups or modify other properties.
  • End a callEnds an ongoing Slack call, identified by its ID (obtained from `calls.add`), optionally specifying the call's duration.
  • Fetch conversation historyFetches a chronological list of messages and events from a specified Slack conversation, accessible by the authenticated user/bot, with options for pagination and time range filtering. IMPORTANT LIMITATION: This action only returns messages from the main channel timeline. Threaded replies are NOT returned by this endpoint. To retrieve threaded replies, use the SLACK_FETCH_MESSAGE_THREAD_FROM_A_CONVERSATION action (conversations.replies API) instead. The oldest/latest timestamp filters work reliably for filtering the main channel timeline, but cannot be used to retrieve individual threaded replies - even if you know the exact reply timestamp, setting oldest=latest to that timestamp will return an empty messages array. To get threaded replies: 1. Use this action to get parent messages (which include thread_ts, reply_count, latest_reply fields) 2. Use SLACK_FETCH_MESSAGE_THREAD_FROM_A_CONVERSATION with the parent's thread_ts to fetch all replies in that thread
  • Fetch item reactionsFetches reactions for a Slack message, file, or file comment. Exactly one identifier path must be provided: `channel`+`timestamp`, `file`, or `file_comment`. Mixing identifiers (e.g., providing both `channel`+`timestamp` and `file`) causes errors. If the response omits the `reactions` field, the item has zero reactions.
  • Retrieve conversation repliesRetrieves replies to a specific parent message in a Slack conversation, using the channel ID and the parent message's timestamp (`ts`). Note: The parent message in the response contains metadata (reply_count, reply_users, latest_reply) that indicates expected thread activity. If the returned messages array contains fewer replies than reply_count indicates, check: (1) has_more=true means pagination is needed, (2) recently posted replies may have timing delays, (3) some replies may be filtered by permissions or deleted. The composio_execution_message field will warn about any detected mismatches.
  • Fetch team infoFetches comprehensive metadata about the current Slack team, or a specified team if the provided ID is accessible.
  • Find channelsFind channels in a Slack workspace by any criteria - name, topic, purpose, or description. Returns channel IDs (C*/G* prefixed) required by most Slack tools — always resolve names to IDs here before passing to other tools. NOTE: This action searches channels and conversations visible to the authenticated user. Empty results may indicate: - No channels match the search query in name, topic, or purpose - The target private channel or DM is not accessible to the authenticated user because they are not a member - The connection lacks required read scopes (channels:read, groups:read, im:read, mpim:read). If empty, retry with exact_match=false or exclude_archived=false to avoid false negatives. In large workspaces, paginate using next_cursor to avoid missing matches. Check 'composio_execution_message' and 'total_channels_searched' in the response for details.
  • Lookup users by emailRetrieves the Slack user object for an active user by their registered email address; requires the users:read.email OAuth scope. Fails with 'users_not_found' if the email is unregistered, the user is inactive, the account is a guest, or the email is hidden by workspace privacy settings.
  • Find usersFind users in a Slack workspace by any criteria - email, name, display name, or other text. Includes optimized email lookup for exact email matches. Zero results may reflect email visibility restrictions or workspace policies, not global absence. Repeated calls may trigger HTTP 429; honor the Retry-After header.
  • Fetch bot user informationFetches information for a specified, existing Slack bot user; will not work for regular user accounts or other integration types.
  • Retrieve call informationRetrieves a point-in-time snapshot of a specific Slack call's information.
  • Get Slack List itemFetches a single item (row) from a Slack List via `slackLists.items.info`. Returns the row's `column_id`-keyed typed values along with metadata about the parent List. Set `include_is_subscribed` to also report whether the calling user is subscribed to the row. Requires a user token with the `lists:read` scope.
  • Get reminder informationRetrieves detailed information for an existing Slack reminder specified by its ID; this is a read-only operation.
  • Get remote fileRetrieve information about a remote file added to Slack via the files.remote API. Does not work for standard Slack-hosted file uploads.
  • Retrieve team profile detailsRetrieves all profile field definitions for a Slack team, optionally filtered by visibility, to understand the team's profile structure.
  • Get unread messages from userRetrieves unread direct messages from a specific user by opening their DM conversation, checking for unread messages, and fetching message history since the last read timestamp. Use this action when you need to check if a specific user has sent unread direct messages to the authenticated user, or when monitoring incoming DMs from particular users. Returns an empty messages array if there are no unread messages from the specified user. Note: This action only works for direct messages (DMs), not channel messages or group conversations.
  • Get team DND statusRetrieves a user's current Do Not Disturb status.
  • Retrieve user presenceRetrieves a Slack user's current real-time presence (e.g., 'active', 'away') to determine their availability, noting this action does not provide historical data or status reasons.
  • Invite users to a Slack channelInvites users to an existing Slack channel using their valid Slack User IDs. Response is always HTTP 200; inspect `ok`, `error`, and `errors` fields to confirm users were added.
  • Join conversation by channel idJoins an existing Slack conversation (public channel, private channel, or multi-person direct message) by its ID, if the authenticated user has permission. Joining an already-joined channel returns a non-fatal no-op response. Private or restricted channel joins may fail with a permission error.
  • Leave conversation channelLeaves a Slack conversation given its channel ID; fails if leaving as the last member of a private channel or if used on a Slack Connect channel.
  • List all channelsLists conversations available to the user with various filters and search options. Always use resolved `channel_id` (not display names) for downstream operations, as names may be non-unique. The `created` field in results is a Unix epoch timestamp (UTC). Pagination across large workspaces may return HTTP 429 with a `Retry-After` header; honor the delay and resume from the last successful cursor.
  • List all usersRetrieves a paginated list of all users with profile details, status, and team memberships in a Slack workspace; data may not be real-time. Filter response fields `is_bot`, `is_app_user`, and `deleted` to build human-only rosters. Profile fields like `email` and `phone` may be absent depending on OAuth scopes and workspace privacy settings. Guest/restricted accounts may be omitted based on scopes—do not treat results as a complete directory. High-frequency calls risk HTTP 429; honor the `Retry-After` header and throttle to ~1–2 requests/second. Use stable user IDs rather than display names for mapping. Prefer SLACK_FIND_USERS for targeted lookups; cache results to avoid full-workspace fetches.
  • List available workspacesList Slack workspaces where both the connection and target user have access. Returns each workspace's team_id and name. Use this when: (1) the user references a workspace by name, (2) a user-specific tool requires team_id and you don't have one, or (3) a user-specific call fails with a team/workspace access error. Match the user's workspace name to a team_id from the results and pass that team_id to subsequent tools. If the name matches zero or multiple workspaces, ask the user to clarify. Only meaningful for org-level installs; single-workspace connections return the workspace only if the specified user's membership is visible to this token.
  • List conversationsList conversations (channels/DMs) accessible to a specified user (or the authenticated user if no user ID is provided), respecting shared membership for non-public channels. Returns conversation IDs (C* for channels, G* for group DMs), not display names. Absence of private channels, DMs, or MPIMs from results indicates token scope or membership limits, not that the conversation is nonexistent.
  • List team custom emojisRetrieves all custom emojis for the Slack workspace (image URLs or aliases), not standard Unicode emojis; does not include usage statistics or creation dates.
  • List Slack filesLists files and their metadata within a Slack workspace, filterable by user, channel, timestamp, or type; returns metadata only, not file content. Results are limited to files visible to the authenticated user — files in private channels or restricted to certain members require appropriate membership and permissions. For large workspaces, check `paging.pages` in the response to determine total pages when paginating.
  • List Slack List itemsLists the rows (items) in a Slack List via `slackLists.items.list`. Each row exposes `column_id`-keyed typed values (e.g. `rich_text`, `select`, `user`, `date`, `number`); the legacy `key`/`value` fields are deprecated. Results are cursor-paginated—you must paginate using `response_metadata.next_cursor` until it is empty, or rows are silently truncated to the first page. Set `archived=true` to return archived rows instead of active ones. Requires a user token with the `lists:read` scope.
  • List pinned items in a channelRetrieves all messages and files pinned to a specified channel; the caller must have access to this channel.
  • List remindersLists all reminders with their details for the authenticated Slack user; returns an empty array if no reminders exist (valid state, not an error). Reminder text is not unique—perform client-side matching on returned objects before extracting a reminder ID for use with SLACK_DELETE_A_SLACK_REMINDER.
  • List remote filesRetrieve information about a team's remote files.
  • List unread channel messagesLists all unread messages in a specified Slack channel for the authenticated user. This action fetches messages that have been posted since the user's last read position in the channel. Use this action when you need to retrieve messages the user hasn't seen yet. The action determines the user's read position and returns all messages posted after that timestamp. Note: This only returns messages from the main channel timeline, not threaded replies. For threaded replies, use SLACK_FETCH_MESSAGE_THREAD_FROM_A_CONVERSATION.
  • List all users in a user groupRetrieves a list of all user IDs within a specified Slack user group, with an option to include users from disabled groups.
  • List user groupsLists user groups in a Slack workspace, including user-created and default groups; results for large workspaces may be paginated.
  • List user reactionsLists all reactions added by a specific user to messages, files, or file comments in Slack, useful for engagement analysis when the item content itself is not required. Results are paginated; check `response_metadata.next_cursor` and iterate with the `cursor` parameter to retrieve complete reaction history.
  • Lookup Canvas SectionsLooks up section IDs in a Slack Canvas for use with targeted edit operations. Section IDs are needed for insert_after, insert_before, delete, and section-specific replace operations.
  • Open DMOpens or resumes a Slack direct message (DM) or multi-person direct message (MPIM) by providing either user IDs or an existing channel ID. Returns `already_open=true` when the DM exists — treat as success and reuse the returned `channel.id` (starts with 'D') for subsequent SLACK_SEND_MESSAGE calls; passing a username, email, or user ID directly to SLACK_SEND_MESSAGE causes `channel_not_found`. Avoid redundant calls when an existing DM channel ID is available.
  • Pin an item to a channelPins a message to a specified Slack channel; the message must not already be pinned.
  • Remove call participantsRegisters participants removed from a Slack call.
  • Remove reaction from itemRemoves an emoji reaction from a message, file, or file comment in Slack. Provide exactly one targeting method: channel+timestamp together, file, or file_comment. Mixing methods or omitting all returns invalid_arguments.
  • Remove remote fileRemoves the Slack reference to an external file (which must have been previously added via the remote files API), specified by either its `external_id` or `file` ID (one of which is required), without deleting the actual external file.
  • Remove user from conversationRemoves a specified user from a Slack conversation (channel); the caller must have permissions to remove users and cannot remove themselves using this action.
  • Rename a conversationRenames a Slack channel, automatically adjusting the new name to meet naming conventions (e.g., converting to lowercase), which may affect integrations using the old name.
  • Retrieve conversation informationRetrieves metadata for a Slack conversation by ID (e.g., name, purpose, creation date, with options for member count/locale), excluding message content. The `channel` parameter is effectively required. Private channels, DMs, or channels where the app lacks membership may return restricted data; check `is_archived` and `is_member` fields in the response to diagnose access issues. Bulk lookups may trigger HTTP 429 rate limiting; honor the `Retry-After` response header.
  • Get conversation membersRetrieves a paginated list of active member IDs (not names, emails, or presence) for a specified Slack public channel, private channel, DM, or MPIM. Returns only user IDs; use a user-lookup tool to enrich member data.
  • Retrieve user DND statusRetrieves a Slack user's current Do Not Disturb (DND) status to determine their availability before interaction; any specified user ID must be a valid Slack user ID.
  • Retrieve detailed file informationRetrieves detailed metadata and paginated comments for a specific Slack file ID; does not download file content.
  • Retrieve detailed user informationRetrieves comprehensive information for a valid Slack user ID, excluding message history and channel memberships. Sensitive fields like `email` and `phone` require the `users:read.email` scope and may be silently omitted based on workspace privacy policies.
  • Retrieve user profile informationRetrieves profile information for a specified Slack user (defaults to the authenticated user if `user` ID is omitted); a provided `user` ID must be valid. Sensitive fields like email and phone may be silently omitted if required scopes (e.g., `users:read.email`) are not granted or workspace privacy policies restrict access.
  • Revoke a file's public urlRevokes a Slack file's public URL, making it private; this is a no-op if not already public and is irreversible.
  • Schedule messageSchedules a message to a Slack channel, DM, or private group for a future time (`post_at`), requiring `text`, `blocks`, or `attachments` for content; scheduling is limited to 120 days in advance.
  • Search all contentTool to search all messages and files. Use when you need unified content search across channels and files in one call. Results are scoped to content visible to the authenticated token; missing hits in private or restricted channels reflect permission/membership gaps. Response separates messages and files into distinct sections — explicitly read the files section for document results. Results are index-based and may lag several minutes behind real-time; use SLACK_FETCH_CONVERSATION_HISTORY for near-real-time per-channel coverage. Paginated searches exceeding ~1 req/sec may return HTTP 429 too_many_requests; honor the Retry-After header and resume from the last page.
  • Search messagesWorkspace‑wide Slack message search with date ranges and filters. Use `query` modifiers (e.g., in:#channel, from:@user, before/after:YYYY-MM-DD), sorting (score/timestamp), and pagination.
  • Send ephemeral messageSends an ephemeral message visible only to the specified `user` in a channel; other channel members cannot see it. Both the bot and the target user must be members of the specified channel.
  • Share a me message in a channelSends a 'me message' (e.g., '/me is typing') to a Slack channel, where it's displayed as a third-person user action; messages are plain text and the channel must exist and be accessible.
  • Send messagePosts a message to a Slack channel, DM, or private group. Provide exactly one visible content mode: `markdown_text` for normal Markdown content, or `blocks` for raw Slack Block Kit layouts. Use `fallback_text` only with `blocks`; it maps to Slack's top-level `text` fallback. Fails with `not_in_channel`, `channel_not_found`, or `channel_is_archived` if the bot lacks access. Rate-limited at ~1 req/sec (HTTP 429, honor `Retry-After`). Not idempotent — duplicate calls post duplicate messages.
  • Set a conversation's purposeSets the purpose (a short description of its topic/goal, displayed in the header) for a Slack conversation; the calling user must be a member.
  • Set Slack List accessGrants or sets sharing access on a Slack List via `slackLists.access.set`. Grant `read`, `write`, or `owner` access to either channels (`channel_ids`) or users (`user_ids`) — exactly one of the two is required. The `owner` level is user-only and subject to additional server-side rules. Requires a user token with the `lists:write` scope.
  • Set conversation read cursorMarks a message, specified by its timestamp (`ts`), as the most recently read for the authenticated user in the given `channel`, provided the user is a member of the channel and the message exists within it.
  • Set conversation topicSets or updates the topic for a specified Slack conversation.
  • Set user presenceManually sets a user's Slack presence, overriding automatic detection; this setting persists across connections but can be overridden by user actions or Slack's auto-away (e.g., after 10 mins of inactivity).
  • Share a remote file in channelsShares a remote file, which must already be registered with Slack, into specified Slack channels or direct message conversations.
  • Start callRegisters a new call in Slack using `calls.add` for third-party call integration; `created_by` is required if not using a user-specific token.
  • Unarchive channelReverses conversation archival.
  • Unpin message from channelUnpins a message, identified by its timestamp, from a specified channel if the message is currently pinned there; this operation is destructive.
  • Update call informationUpdates the title, join URL, or desktop app join URL for an existing Slack call identified by its ID.
  • Update Slack ListUpdates a Slack List's metadata via `slackLists.update`. Only the List's `name`, `description_blocks`, and `todo_mode` are editable here. The List to update is identified by its `id` (not `list_id`). Descriptions are rich text — a plain string is wrapped into a `rich_text` block automatically. Requires a user token with the `lists:write` scope.
  • Update Slack List itemUpdates one or more cells in an EXISTING Slack List row via `slackLists.items.update`. Each cell is identified by `row_id` (an existing row ID matching `^Rec[A-Z0-9]{8,}$`) and `column_id` and carries a typed value; text columns require Block Kit `rich_text` (a plain string is wrapped automatically), and `select` takes the column's choice values (e.g. `["todo"]`). Use it to UPDATE existing rows; the live API rejects `row_id_to_create` inside a cell (despite Slack's inline example), so to ADD a row use `create_slack_list_item`. Requires a user token with the `lists:write` scope.
  • Update an existing remote fileUpdates metadata or content details for an existing remote file in Slack; this action cannot upload new files or change the fundamental file type.
  • Update a Slack messageUpdates a Slack message by timestamp. Provide exactly one visible content mode: `markdown_text` for normal Markdown content, or `blocks` for raw Slack Block Kit layouts. Use `fallback_text` only with `blocks`; it maps to Slack's top-level `text` fallback.
  • Update Slack user groupUpdates an existing Slack User Group, which must be specified by an existing `usergroup` ID, with new optional details such as its name, description, handle, or default channels.
  • Update user group membersReplaces all members of an existing Slack User Group with a new list of valid user IDs.
  • Upload or create a file in SlackUpload files, images, screenshots, documents, or any media to Slack channels or threads. Supports all file types including images (PNG, JPG, JPEG, GIF), documents (PDF, DOCX, TXT), code files, and more. Can share files publicly in channels or as thread replies with optional comments. Large files may fail with `upload_too_large`; use SLACK_ADD_A_REMOTE_FILE_FROM_A_SERVICE for large uploads. If the API returns `ok=false` with `method_deprecated`, fall back to SLACK_ADD_A_REMOTE_FILE_FROM_A_SERVICE or SLACK_SEND_MESSAGE with a URL.