# Slackbot

Slackbot automates responses and reminders within Slack, assisting with tasks like onboarding, FAQs, and notifications to streamline team productivity

- **Category:** team chat
- **Auth:** OAUTH2
- **Composio Managed App Available?** Yes
- **Tools:** 87
- **Triggers:** 9
- **Slug:** `SLACKBOT`
- **Version:** 20260309_00

## Tools

### Add call participants

**Slug:** `SLACKBOT_ADD_CALL_PARTICIPANTS`

Registers new participants added to a Slack call.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | ID of the call returned by the add method. |
| `users` | string | Yes | The list of users to add as participants in the call. users is a JSON array (formatted as a string) containing information for each user. Each element must include a `slack_id`. For example: `[{"slack_id": "U1H77"}]` or `[{"slack_id": "U1H77"}, {"slack_id": "U2ABC123"}]`. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Add reaction to message

**Slug:** `SLACKBOT_ADD_REACTION_TO_AN_ITEM`

Adds a specified emoji reaction to an existing message in a Slack channel, identified by its timestamp; does not remove or retrieve reactions.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | Yes | Name of the emoji to add as a reaction (e.g., 'thumbsup'). This is the emoji name without colons. For emojis with skin tone modifiers, append '::skin-tone-X' where X is a number from 2 to 6 (e.g., 'wave::skin-tone-3'). The emoji must already exist in the workspace; custom or non-existent emoji names will fail silently. |
| `channel` | string | Yes | ID of the channel where the message to add the reaction to was posted. |
| `timestamp` | string | Yes | Timestamp of the message to which the reaction will be added. This is a unique identifier for the message, typically a string representing a float value like '1234567890.123456'. Must be the exact message timestamp; permalinks or approximate values will not work. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Add a remote file

**Slug:** `SLACKBOT_ADD_REMOTE_FILE`

Adds 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `title` | string | Yes | Title of the remote file to be displayed in Slack. |
| `filetype` | string | No | File type (e.g., 'pdf', 'docx', 'png') to help Slack display appropriate icons or previews. |
| `external_id` | string | Yes | Unique identifier for the file, defined by the calling application, used for future API references (e.g., updating, deleting). |
| `external_url` | string | Yes | Publicly accessible or permissioned URL of the remote file, used by Slack to access its content or metadata. |
| `preview_image` | string | No | Base64-encoded image (e.g., PNG, JPEG) used as the file's preview in Slack. |
| `indexable_file_contents` | string | No | Plain text content of the file, indexed by Slack for search. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Archive a Slack conversation

**Slug:** `SLACKBOT_ARCHIVE_CONVERSATION`

Archives 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `channel` | string | No | ID of the Slack conversation to archive. This ID uniquely identifies a channel (e.g., public, private). |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Close conversation channel

**Slug:** `SLACKBOT_CLOSE_DM`

Closes 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `channel` | string | Yes | The ID of the direct message or multi-person direct message channel to close. Example: D1234567890 or G0123456789. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create a reminder

**Slug:** `SLACKBOT_CREATE_A_REMINDER`

Creates 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').

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `text` | string | Yes | The textual content of the reminder message. |
| `time` | string | Yes | Specifies when the reminder should occur. This can be a Unix timestamp (integer, up to five years from now), the number of seconds until the reminder (integer, if within 24 hours, e.g., '300' for 5 minutes), or a natural language description (string, e.g., "in 15 minutes," or "every Thursday at 2pm", "daily"). Natural language is parsed relative to the user"s workspace timezone; use Unix timestamps when target timezone is uncertain. |
| `user` | string | No | The ID of the user who will receive the reminder (e.g., 'U012AB3CD4E'). If not specified, the reminder will be sent to the user who created it. NOTE: Setting reminders for other users is no longer supported for user tokens - only bot tokens can set reminders for other users. |
| `team_id` | string | No | Encoded team id. Required if using an org-level token to specify which workspace the reminder should be created in. |
| `recurrence` | object | No | Recurrence settings for a reminder. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Slack Canvas

**Slug:** `SLACKBOT_CREATE_CANVAS`

Creates a new Slack Canvas with the specified title and optional content.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `title` | string | No | The title of the canvas to create. If not provided, Slack will generate a default title. |
| `channel_id` | string | No | Optional channel ID (e.g., 'C1234567890'). If provided, the canvas will be automatically added as a tab in this channel with write permissions. |
| `document_content` | object | No | Optional canvas content in Slack's document format. If not provided, creates an empty canvas. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create channel

**Slug:** `SLACKBOT_CREATE_CHANNEL`

Initiates a public or private channel-based conversation in a Slack workspace. Immediately creates the channel; invoke only after explicit user confirmation.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | Yes | Name of the public or private channel to create Must be lowercase, unique, and contain no spaces or periods; max 80 characters. |
| `team_id` | string | No | encoded team id to create the channel in, required if org token is used |
| `is_private` | boolean | No | Create a private channel instead of a public one |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create a Slack user group

**Slug:** `SLACKBOT_CREATE_USER_GROUP`

Creates a new User Group (often referred to as a subteam) in a Slack workspace.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | Yes | Unique name for the User Group. Must be unique among all User Groups in the workspace. |
| `handle` | string | No | Unique mention handle. Must be unique across channels, users, and other User Groups. Max 21 chars; lowercase letters, numbers, hyphens, underscores only. |
| `team_id` | string | No | Encoded team ID where the User Group should be created. Required if using an org token. Will be ignored if the API call is sent using a workspace-level token. |
| `channels` | string | No | Comma-separated encoded channel IDs for default channels, suggested when mentioning or inviting the group. |
| `description` | string | No | Short description for the User Group. |
| `include_count` | boolean | No | Include the User Group's user count in the response. Server defaults to `false` if omitted. |
| `enable_section` | boolean | No | Configure this user group to show as a sidebar section for all group members. Only relevant if group has 1 or more default channels added. |
| `additional_channels` | string | No | Comma-separated encoded channel IDs for which the User Group can custom add usergroup members to. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Customize URL unfurl

**Slug:** `SLACKBOT_CUSTOMIZE_URL_UNFURL`

Customizes URL previews (unfurling) in a specific Slack message using a URL-encoded JSON in `unfurls` to define custom content or remove existing previews.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `ts` | string | No | Timestamp of the message to customize URL unfurling for. Must be provided with `channel`, or alternatively provide `unfurl_id` and `source` together. |
| `source` | string | No | Link source: either 'composer' or 'conversations_history'. Must be provided with `unfurl_id`. |
| `channel` | string | No | Channel, private group, or DM channel to send message to. Can be an encoded ID, or a name. Must be provided with `ts`, or alternatively provide `unfurl_id` and `source` together. |
| `unfurls` | string | No | JSON string mapping URLs to custom unfurl content (Slack attachment format or blocks). Pass as a plain JSON string (not URL-encoded). To remove an existing unfurl, provide an empty object for that URL. |
| `metadata` | string | No | JSON object with 'entities' field providing Work Object array. Either `unfurls` or `metadata` is required. Pass as a JSON string. |
| `unfurl_id` | string | No | Link ID to unfurl. Must be provided with `source`. Alternative to using `channel` and `ts` parameters. |
| `user_auth_url` | string | No | URL-encoded custom URL for user authentication with your app to enable unfurling. Used when `user_auth_required` is true. |
| `user_auth_blocks` | string | No | JSON array of structured blocks (URL-encoded) sent as ephemeral authentication invitation. Alternative to `user_auth_message` for richer formatting. Used when `user_auth_required` is true. |
| `user_auth_message` | string | No | Ephemeral message text prompting user authentication with your app for domain-specific unfurling. Used when `user_auth_required` is true and authorization is pending. |
| `user_auth_required` | boolean | No | Set to `true` if user authentication is required to unfurl links for a domain, enabling an authentication flow using `user_auth_url` and `user_auth_message`. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Slack Canvas

**Slug:** `SLACKBOT_DELETE_CANVAS`

Deletes a Slack Canvas permanently and irreversibly. Always confirm with the user before calling this tool.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `canvas_id` | string | Yes | The unique identifier of the canvas to delete |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete a file by ID

**Slug:** `SLACKBOT_DELETE_FILE`

Permanently 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `file` | string | Yes | ID of the file to delete. Typically obtained when a file is uploaded or listed. |
| `team_id` | string | No | The team/workspace ID where the file exists. Required for Enterprise Grid org-level tokens. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete file comment

**Slug:** `SLACKBOT_DELETE_FILE_COMMENT`

Deletes a specific comment from a file in Slack; this action is irreversible.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | ID of the comment to delete. This can be obtained when the comment is created or by listing file comments. |
| `file` | string | Yes | ID of the file to delete a comment from. The file ID can be obtained using the `files.info` method or when a file is shared. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete a Slack reminder

**Slug:** `SLACKBOT_DELETE_REMINDER`

Deletes an existing Slack reminder, typically when it is no longer relevant or a task is completed; this operation is irreversible.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `team_id` | string | No | Encoded team id, required if org token is used. |
| `reminder` | string | Yes | The unique identifier of the reminder to be deleted. This ID is obtained when a reminder is created or listed. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete a message from a chat

**Slug:** `SLACKBOT_DELETES_A_MESSAGE_FROM_A_CHAT`

Deletes 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `ts` | string | No | Timestamp of the message to be deleted. Must be the exact Slack message timestamp string with fractional precision, e.g., '1234567890.123456'. Thread replies use their own `ts`; ephemeral messages and certain app-posted messages cannot be deleted via this method even with a valid timestamp. |
| `as_user` | boolean | No | Legacy parameter for classic Slack apps. Pass true to delete the message as the authed user. Bot tokens can only delete messages posted by that bot. This parameter is primarily for legacy apps and is generally not needed with modern bot tokens. |
| `channel` | string | No | The ID of the channel, private group, or direct message conversation containing the message to be deleted. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete scheduled chat message

**Slug:** `SLACKBOT_DELETE_SCHEDULED_MESSAGE`

Deletes a pending, unsent scheduled message from the specified Slack channel, identified by its `scheduled_message_id`.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `as_user` | boolean | No | Pass true to delete the message as the authed user with chat:write:user scope. Bot users in this context are considered authed users. If not provided, defaults to false. |
| `channel` | string | Yes | ID of the channel, private group, or DM conversation where the message is scheduled. |
| `scheduled_message_id` | string | Yes | Unique ID (`scheduled_message_id`) of the message to be deleted; obtained from `chat.scheduleMessage` response. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Disable a Slack user group

**Slug:** `SLACKBOT_DISABLE_USER_GROUP`

Disables 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `team_id` | string | No | Encoded team ID where the User Group exists. Required if using an org-level token. |
| `usergroup` | string | Yes | Unique encoded ID of the User Group to disable. |
| `include_count` | boolean | No | If true, include the number of users in the User Group in the response. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Download Slack file

**Slug:** `SLACKBOT_DOWNLOAD_FILE`

Tool 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `file` | string | Yes | ID of the file to download. This is a required field. File IDs start with 'F' followed by alphanumeric characters (e.g., 'F123ABCDEF0'). |
| `page` | integer | No | Page number of comment results to retrieve. Used for comment pagination. Slack's default is 1 if not provided. `cursor`-based pagination is generally preferred. |
| `count` | integer | No | Number of comments to retrieve per page. Used for comment pagination. Slack's default is 100 if not provided. |
| `limit` | integer | No | The maximum number of comments to retrieve. This is an upper limit, not a guarantee of how many will be returned. Primarily used for comment pagination. |
| `cursor` | string | No | Pagination cursor for retrieving comments. Set to `next_cursor` from a previous response's `response_metadata` to fetch the next page of comments. Essential for navigating through large sets of comments. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Edit Slack Canvas

**Slug:** `SLACKBOT_EDIT_CANVAS`

Edits a Slack Canvas with granular control over content placement. Supports replace, insert (before/after/start/end) operations for flexible content management.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `canvas_id` | string | Yes | The unique identifier of the canvas to edit |
| `operation` | string ("replace" | "insert_after" | "insert_before" | "insert_at_start" | "insert_at_end" | "delete" | "rename") | No | Type of edit operation: 'replace' (replaces entire canvas or specific section if section_id provided), 'insert_after' (inserts content after section_id), 'insert_before' (inserts content before section_id), 'insert_at_start' (prepends content to beginning), 'insert_at_end' (appends content to end), 'delete' (deletes specific section by section_id), 'rename' (renames canvas title using title_content) |
| `section_id` | string | No | Section ID for targeted operations. Required for: 'insert_after', 'insert_before', 'delete'. Optional for: 'replace' (if omitted, replaces entire canvas). Not used for: 'insert_at_start', 'insert_at_end'. Use canvases.sections.lookup method to get section IDs from existing canvas. |
| `title_content` | object | No | The new title for the canvas in markdown format. Required only for 'rename' operation. Supports markdown format including emojis (e.g., ':white_check_mark:'). |
| `document_content` | object | No | The content to add/replace in Slack's document format. Required for all operations except 'delete' and 'rename'. Use canvases.sections.lookup to find section IDs for targeted operations. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Share file public url

**Slug:** `SLACKBOT_ENABLE_PUBLIC_SHARING_OF_A_FILE`

Enables 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `file` | string | Yes | The ID of the file to be shared publicly. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Enable a user group

**Slug:** `SLACKBOT_ENABLE_USER_GROUP`

Enables 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `team_id` | string | No | Encoded team id where the user group is, required if org token is used. Ignored for workspace-level tokens. |
| `usergroup` | string | Yes | The unique encoded ID of the User Group to enable. This ID typically starts with 'S'. |
| `include_count` | boolean | No | If true, includes the count of users in the User Group in the response. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### End a call

**Slug:** `SLACKBOT_END_CALL`

Ends an ongoing Slack call, identified by its ID (obtained from `calls.add`), optionally specifying the call's duration.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Unique identifier of the call to be ended, obtained from the `calls.add` method. |
| `duration` | integer | No | Duration of the call in seconds. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Fetch conversation history

**Slug:** `SLACKBOT_FETCH_CONVERSATION_HISTORY`

Fetches 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

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `limit` | integer | No | Maximum number of messages to return (1-1000). The action automatically paginates through API requests to fetch the requested number of messages. Note: Per-request API limits vary by app type (Marketplace/internal apps: up to 999 per request; non-Marketplace apps: 15 per request as of May 2025). Recommended: 200 or fewer for optimal performance. |
| `cursor` | string | No | Pagination cursor from `next_cursor` of a previous response to fetch subsequent pages. See Slack's pagination documentation for details. |
| `latest` | string | No | End of the time range of messages to include in results. Accepts a Unix timestamp or a Slack timestamp (e.g., '1234567890.000000'). NOTE: This filter only applies to main channel messages, not threaded replies. Use SLACK_FETCH_MESSAGE_THREAD_FROM_A_CONVERSATION to retrieve replies. |
| `oldest` | string | No | Start of the time range of messages to include in results. Accepts a Unix timestamp or a Slack timestamp (e.g., '1234567890.000000'). NOTE: This filter only applies to main channel messages, not threaded replies. Use SLACK_FETCH_MESSAGE_THREAD_FROM_A_CONVERSATION to retrieve replies. |
| `channel` | string | Yes | The ID of the public channel, private channel, direct message, or multi-person direct message to fetch history from. |
| `inclusive` | boolean | No | When true, includes messages at the exact 'oldest' or 'latest' boundary timestamps in results. When false (default), excludes boundary messages. Only applies when 'oldest' or 'latest' is specified. |
| `include_all_metadata` | boolean | No | Return all metadata associated with messages in the conversation history. When true, includes additional metadata fields that may be present on messages. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Fetch item reactions

**Slug:** `SLACKBOT_FETCH_ITEM_REACTIONS`

Fetches 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `file` | string | No | File ID. Use instead of channel/timestamp or file comment ID. |
| `full` | boolean | No | If true, returns the complete list of users for each reaction. |
| `channel` | string | No | Channel ID. Required if `timestamp` is provided and no file or file comment ID is given. |
| `team_id` | string | No | Required if using an org-level token. The team/workspace ID where the item exists. Ignored if using a workspace-level token. |
| `timestamp` | string | No | Message timestamp (e.g., '1234567890.123456'). Required if `channel` is provided and no file or file comment ID is given. Thread reply timestamps are tracked separately from the parent message; use the reply's own timestamp to fetch its reactions. |
| `file_comment` | string | No | File comment ID. Use instead of channel/timestamp or file ID. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Retrieve conversation replies

**Slug:** `SLACKBOT_FETCH_MESSAGE_THREAD_FROM_A_CONVERSATION`

Retrieves 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `ts` | string | No | Timestamp of the parent message in the thread. Must be an existing message. If no replies, only the parent message itself is returned. Must be the exact full timestamp string of the root/parent message — not a reply's ts, a truncated value, a permalink, or an integer; these silently return wrong results. |
| `limit` | integer | No | Maximum number of messages to return. Fewer may be returned even if more are available. |
| `cursor` | string | No | Pagination cursor from `response_metadata.next_cursor` of a previous response to get subsequent pages. If omitted, fetches the first page. |
| `latest` | string | No | Latest message timestamp in the time range to include results. |
| `oldest` | string | No | Oldest message timestamp in the time range to include results. Must be a UTC-based Slack ts string; incorrect timezone conversion or rounding can produce empty result windows. |
| `channel` | string | No | ID of the conversation (channel, direct message, etc.) to fetch the thread from. Must be a channel ID, not a channel name. Token must have membership in private channels or DMs, otherwise returns empty results or `not_in_channel`/`channel_not_found`. |
| `team_id` | string | No | Required for org-wide apps: the workspace ID to use for this request. If using a workspace-level token, this parameter is optional and will be ignored. |
| `inclusive` | boolean | No | Whether to include messages with `latest` or `oldest` timestamps in results. Effective only if `latest` or `oldest` is specified. |
| `include_all_metadata` | boolean | No | Return all metadata associated with messages in the thread. When true, includes additional metadata fields that may be present on messages. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Fetch team info

**Slug:** `SLACKBOT_FETCH_TEAM_INFO`

Fetches comprehensive metadata about the current Slack team, or a specified team if the provided ID is accessible.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `team` | string | No | The ID of the team to retrieve information for. If omitted, information for the current team (associated with the authentication token) is returned. The token must have permissions to view the specified team, especially for teams accessible via external shared channels. |
| `domain` | string | No | Query by domain instead of team (only when team is null). This only works for domains in the same enterprise as the querying team token. This also expects the domain to belong to a team and not the enterprise itself. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Find channels

**Slug:** `SLACKBOT_FIND_CHANNELS`

Find 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 can only search channels visible to the bot. Empty results may indicate: - No channels match the search query in name, topic, or purpose - The target channel is private and the bot hasn't been invited - The bot lacks required scopes (channels:read, groups: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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `limit` | integer | No | Maximum number of channels to return (1 to 999). Defaults to 50. Slack recommends no more than 200 results at a time for optimal performance. |
| `query` | string | Yes | Search query to find channels. Searches across channel name, topic, purpose, and description (case-insensitive partial matching). Leading '#' prefix is automatically stripped. |
| `types` | string | No | Comma-separated list of channel types to include: `public_channel`, `private_channel`, `mpim` (multi-person direct message), `im` (direct message). Defaults to public and private channels. |
| `team_id` | string | No | The ID of the workspace to list channels from. Required when using an org-level token to specify which workspace to retrieve channels from. This field is ignored when using a workspace-level token. |
| `exact_match` | boolean | No | When true, only return channels whose name exactly matches the query (case-insensitive). Also matches against previous channel names and the 'general' flag. When false, returns partial matches across name, topic, and purpose. Defaults to false. |
| `member_only` | boolean | No | Only return channels the user is a member of. Defaults to false. |
| `exclude_archived` | boolean | No | Exclude archived channels from search results. Defaults to true. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Lookup users by email (Deprecated)

**Slug:** `SLACKBOT_FIND_USER_BY_EMAIL_ADDRESS`

DEPRECATED: Use FindUsers instead. Retrieves 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `email` | string | Yes | The email address of the user to look up. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Find users

**Slug:** `SLACKBOT_FIND_USERS`

Find 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `email` | string | No | Email address to search for. This is a convenience parameter that automatically performs an email-based search. Either email or search_query parameter is required. |
| `limit` | integer | No | Maximum number of users to return (1 to 1000). Slack recommends no more than 200 for optimal performance. Defaults to 50. Large workspaces may require pagination or repeated queries to cover all users. |
| `team_id` | string | No | The ID of the Slack workspace (e.g., 'T123456789'). Required when using an org-level token. For workspace-level tokens, this is optional and will be ignored. |
| `exact_match` | boolean | No | When true, only returns users with exact matches on name, display name, real name, first name, last name, or email fields (case-insensitive). For email queries, uses Slack's dedicated email lookup endpoint. When false, allows partial/substring matching. Defaults to false. |
| `include_bots` | boolean | No | Include bot users in search results. Defaults to false. |
| `search_query` | string | No | Search query to find users. Can be a Slack user ID (e.g., 'U012ABCDEF'), email address, or name. For user IDs (starting with 'U' or 'W'), uses Slack's users.info API directly. For email addresses with exact_match=true, uses Slack's email lookup endpoint. For other queries, searches across name, display name, real name, email, first name, last name, and status text (case-insensitive partial matching). Either search_query (or 'query' as alias), or email parameter is required. Name-based queries can return multiple matches — verify exactly one user ID before passing to downstream tools like SLACK_OPEN_DM or SLACK_SEND_MESSAGE; disambiguate using email or real_name fields. |
| `include_locale` | boolean | No | Include the `locale` field for each user. Defaults to `false`. |
| `include_deleted` | boolean | No | Include deleted/deactivated users in search results. Defaults to false. |
| `include_restricted` | boolean | No | Include restricted (guest) users in search results. Defaults to true. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Fetch bot user information

**Slug:** `SLACKBOT_GET_BOT_USER`

Fetches information for a specified, existing Slack bot user; will not work for regular user accounts or other integration types.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `bot` | string | No | The ID of the bot user to retrieve information for. This typically starts with 'B'. |
| `team_id` | string | No | The ID of the workspace/team. Required when using an org-level token. This typically starts with 'T'. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Retrieve call information

**Slug:** `SLACKBOT_GET_CALL_INFO`

Retrieves a point-in-time snapshot of a specific Slack call's information.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Unique identifier of the Slack call for which to retrieve information. This ID is typically returned when a call is initiated (e.g., by the `calls.add` method). |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Slack Canvas

**Slug:** `SLACKBOT_GET_CANVAS`

Retrieves a specific Slack Canvas by its ID, including its content and metadata.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page number for comment pagination (1-based, max 100). Works with count parameter. |
| `count` | integer | No | Maximum number of comments to return per page (1-1000). Controls pagination of the comments field in the response. |
| `limit` | integer | No | Maximum number of comments to return (alternative to count parameter). Recommended to use 200 or less for cursor-based pagination. |
| `cursor` | string | No | Cursor for pagination of comments. Use the next_cursor value from response_metadata to retrieve the next page. This is the preferred pagination method over page parameter. |
| `canvas_id` | string | Yes | The unique identifier of the canvas to retrieve The app must have access to the canvas; private or restricted canvases are not retrievable even with a valid ID. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get reminder information

**Slug:** `SLACKBOT_GET_REMINDER`

Retrieves detailed information for an existing Slack reminder specified by its ID; this is a read-only operation.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `team_id` | string | No | Encoded team id. Required if org token is passed. |
| `reminder` | string | No | The unique identifier of the reminder to retrieve information for. This ID typically starts with 'Rm'. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get remote file

**Slug:** `SLACKBOT_GET_REMOTE_FILE`

Retrieve information about a remote file added to Slack via the files.remote API. Does not work for standard Slack-hosted file uploads.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `file` | string | No | Specify a file by providing its ID. |
| `external_id` | string | No | Creator defined GUID for the file. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Retrieve team profile details

**Slug:** `SLACKBOT_GET_TEAM_PROFILE`

Retrieves all profile field definitions for a Slack team, optionally filtered by visibility, to understand the team's profile structure.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `team_id` | string | No | The team_id is only relevant when using an org-level token. This field will be ignored if the API call is sent using a workspace-level token. |
| `visibility` | string ("all" | "visible" | "hidden") | No | Enum for visibility filter values. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get team DND status

**Slug:** `SLACKBOT_GET_USER_DND_STATUS`

Retrieves a user's current Do Not Disturb status.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `users` | string | Yes | Comma-separated list of users to fetch Do Not Disturb status for |
| `team_id` | string | No | The workspace ID (team_id) to fetch DND status from. Required when using an org-level token in Enterprise Grid organizations. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Retrieve user presence

**Slug:** `SLACKBOT_GET_USER_PRESENCE`

Retrieves 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `user` | string | No | The ID of the user to query for presence information. This is a string identifier, typically starting with 'U' or 'W' (e.g., 'U123ABC456'). If not provided, presence information for the authenticated user will be returned. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Invite users to a Slack channel

**Slug:** `SLACKBOT_INVITE_USERS_TO_A_CHANNEL`

Invites 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `force` | boolean | No | When set to true and multiple user IDs are provided, continue inviting the valid ones while disregarding invalid IDs. Default is false. |
| `users` | string | No | Comma-separated string of valid Slack User IDs to invite. Up to 1000 user IDs can be included. |
| `channel` | string | No | ID of the public or private Slack channel to invite users to; must be an existing channel. Typically starts with 'C' (public) or 'G' (private/group). Bot must already be a member of private channels to invite others. Archived channels will cause failure. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Join conversation by channel id

**Slug:** `SLACKBOT_JOIN_AN_EXISTING_CONVERSATION`

Joins 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `channel` | string | Yes | ID of the Slack conversation (public channel, private channel, or multi-person direct message) to join. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Leave conversation channel

**Slug:** `SLACKBOT_LEAVE_CONVERSATION`

Leaves 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `channel` | string | Yes | ID of the conversation to leave (e.g., C1234567890). |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List all channels

**Slug:** `SLACKBOT_LIST_ALL_CHANNELS`

Lists 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `limit` | integer | No | Maximum number of channels to return per page (1 to 1000). Fewer channels may be returned than requested. This schema defaults to 1 if omitted. |
| `types` | string | No | Comma-separated list of conversation types to include: `public_channel` (regular #channels everyone can join), `private_channel` (invite-only channels), `im` (1-on-1 direct messages), `mpim` (group direct messages with 3+ people). Defaults to `public_channel` if omitted. Private channels, IMs, and MPIMs only appear if the authenticated user/bot is a member and the token has the required scopes; absence from results reflects access limits, not non-existence. |
| `cursor` | string | No | Pagination cursor (from a previous response's `next_cursor`) for the next page of results. Omit for the first page. Loop on `response_metadata.next_cursor` until it is empty to retrieve all channels; stopping early silently omits results. |
| `team_id` | string | No | Encoded team id to list channels in. Required if using an org-level token. |
| `exclude_archived` | boolean | No | Excludes archived channels if true. The API defaults to false (archived channels are included). |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List all users

**Slug:** `SLACKBOT_LIST_ALL_USERS`

Retrieves 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `limit` | integer | No | Maximum number of items to return per page; fewer may be returned if the end of the list is reached. Recommended to set a value (e.g., 100) as Slack may error for large workspaces if omitted. |
| `cursor` | string | No | Pagination cursor for fetching subsequent pages. Set to `next_cursor` from a previous response's `response_metadata`. Omit for the first page. Paginate until `next_cursor` is empty—stopping early silently undercounts users. Page size is capped at ~200 users. |
| `team_id` | string | No | The workspace/team ID to list users from. Required when using an org-level token (Enterprise Grid). This field is ignored when using a workspace-level token. Use admin.teams.list to get available team IDs. |
| `include_locale` | boolean | No | Include the `locale` field for each user. Defaults to `false`. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Slack Canvases

**Slug:** `SLACKBOT_LIST_CANVASES`

Lists Slack Canvases with filtering by channel, user, timestamp, and page-based pagination. Uses Slack's files.list API with types=canvas filter. Only canvases accessible to the authenticated app are returned; missing canvases indicate permissions restrictions, not empty data. Use `paging.pages` in the response to determine total pages; iterate `page` with `count` to retrieve all results. Known limitations: - The 'user' filter may return canvases accessible to the specified user, not just canvases they created. - The 'ts_from' and 'ts_to' timestamp filters may not work reliably for canvas types. Consider client-side filtering on the 'created' field in the response if precise date filtering is required.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page number for pagination (1-based) |
| `user` | string | No | Optional user ID to filter canvases created by a specific user. Note: This filter may return canvases accessible to the user (not just created by them) due to Slack API behavior with canvas types. |
| `count` | integer | No | Maximum number of canvases to return per page (1-1000) |
| `ts_to` | integer | No | Filter canvases created before this Unix timestamp (inclusive). Pass as integer epoch seconds. Note: This filter may not work reliably for canvas types in the Slack API. |
| `channel` | string | No | Optional channel ID (e.g., 'C1234567890') to filter canvases. Must be a channel ID, not name. |
| `team_id` | string | No | Team/Workspace ID for Enterprise Grid organizations (starts with 'T'). Required when using org-level tokens. For single-workspace installations, this parameter is optional and will be ignored. |
| `ts_from` | integer | No | Filter canvases created after this Unix timestamp (inclusive). Pass as integer epoch seconds. Note: This filter may not work reliably for canvas types in the Slack API. |
| `show_files_hidden_by_limit` | boolean | No | Display truncated file metadata for older files when workspace has exceeded file limits. When true, shows metadata for files that would normally be hidden due to workspace storage limits. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List conversations

**Slug:** `SLACKBOT_LIST_CONVERSATIONS`

List 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `user` | string | No | The ID of the user whose conversations will be listed. If not provided, conversations for the authenticated user are returned. Non-public channels are restricted to those where the calling user (authenticating user) shares membership. |
| `limit` | integer | No | The maximum number of items to return per page. Must be an integer, typically between 1 and 1000 (e.g., 100). If omitted, the API's default limit (often 100) applies. Fewer items than the limit may be returned. |
| `types` | string | No | Comma-separated list of conversation types to include: `public_channel` (regular #channels everyone can join), `private_channel` (invite-only channels), `im` (1-on-1 direct messages), `mpim` (group direct messages with 3+ people). If omitted, all types are included. If omitted, the API defaults to `public_channel` only — explicitly specify all desired types to include private channels, DMs, or MPIMs. For `im` results, only user IDs are returned; use a user-lookup tool to resolve display names. |
| `cursor` | string | No | Pagination cursor for retrieving the next set of results. Obtain this from the `next_cursor` field in a previous response's `response_metadata`. If omitted, the first page is fetched. Must loop on `next_cursor` until it is empty to avoid silently missing conversations. |
| `team_id` | string | No | The team (workspace) ID to filter conversations by. Required for Enterprise Grid tokens to specify which workspace. Can be obtained from team.info API. |
| `exclude_archived` | boolean | No | Set to `true` to exclude archived channels from the list. If `false` or omitted, archived channels are typically included (the API's default behavior for omission will apply, usually including them). |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List team custom emojis

**Slug:** `SLACKBOT_LIST_CUSTOM_EMOJIS`

Retrieves all custom emojis for the Slack workspace (image URLs or aliases), not standard Unicode emojis; does not include usage statistics or creation dates.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `include_categories` | boolean | No | Include a list of categories for Unicode emoji and the emoji in each category. When true, the response will include 'categories' and 'categories_version' fields. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Slack files

**Slug:** `SLACKBOT_LIST_FILES_WITH_FILTERS_IN_SLACK`

Lists 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | string | No | Specifies the page number of the results to retrieve when paginating. Default is 1. |
| `user` | string | No | Filter files created by a single user. Provide the Slack User ID. |
| `count` | string | No | Specifies the number of files to return per page. Default is 100, maximum is 1000. |
| `ts_to` | integer | No | Filter files created before this Unix timestamp (inclusive). |
| `types` | string | No | Filter by file type (comma-separated). Valid types: `all` (everything), `spaces` (Posts/long-form content), `snippets` (code snippets), `images`, `pdfs`, `gdocs` (Google Docs), `zips`. Defaults to 'all'. |
| `channel` | string | No | Filter files appearing in a specific channel, indicated by its Slack Channel ID. |
| `team_id` | string | No | The team/workspace ID to list files from. Required for Enterprise Grid workspaces. |
| `ts_from` | integer | No | Filter files created after this Unix timestamp (inclusive). |
| `show_files_hidden_by_limit` | boolean | No | Show truncated file info for files hidden due to being too old or if the team owning the file is over the storage limit. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List pinned items in a channel

**Slug:** `SLACKBOT_LIST_PINNED_ITEMS`

Retrieves all messages and files pinned to a specified channel; the caller must have access to this channel.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `channel` | string | Yes | The ID of the channel to retrieve pinned items from. This can be a public channel ID, private group ID, or direct message channel ID. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List reminders

**Slug:** `SLACKBOT_LIST_REMINDERS`

Lists 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_MARK_REMINDER_AS_COMPLETE or SLACK_DELETE_A_SLACK_REMINDER.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `team_id` | string | No | Encoded team id. Required if org token is passed. Omitting this when using an org-level token will cause the call to fail. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List remote files

**Slug:** `SLACKBOT_LIST_REMOTE_FILES`

Retrieve information about a team's remote files.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `limit` | integer | No | The maximum number of items to return. |
| `ts_to` | number | No | Filter files created before this timestamp (inclusive). |
| `cursor` | string | No | Paginate through collections of data by setting the cursor parameter to a next_cursor attribute returned by a previous request's response_metadata. Default value fetches the first 'page' of the collection. See pagination for more detail. |
| `channel` | string | No | Filter files appearing in a specific channel, indicated by its ID. |
| `ts_from` | number | No | Filter files created after this timestamp (inclusive). |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List all users in a user group

**Slug:** `SLACKBOT_LIST_USER_GROUP_MEMBERS`

Retrieves a list of all user IDs within a specified Slack user group, with an option to include users from disabled groups.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `team_id` | string | No | The encoded ID of the team/workspace. Only relevant when using an org-level token. This field will be ignored if the API call is sent using a workspace-level token. |
| `usergroup` | string | Yes | The encoded ID of the User Group to list users from. This ID is an alphanumeric string. |
| `include_disabled` | boolean | No | Set to `true` to include users from disabled user groups. If omitted, the default Slack API behavior for handling disabled groups (typically excluding them) will apply. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List user groups

**Slug:** `SLACKBOT_LIST_USER_GROUPS`

Lists user groups in a Slack workspace, including user-created and default groups; results for large workspaces may be paginated.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `team_id` | string | No | Encoded team ID to list user groups in. Required when using an org-level token. |
| `include_count` | boolean | No | Include the number of users in each user group. Defaults to false. |
| `include_users` | boolean | No | Include the list of user IDs for each user group. Defaults to false. |
| `include_disabled` | boolean | No | Include disabled user groups in the results. Defaults to false. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List user reactions

**Slug:** `SLACKBOT_LIST_USER_REACTIONS`

Lists 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `full` | boolean | No | If true, return the complete reaction list, which may include reactions to deleted items. Significantly inflates payload size; enable only when reactions to deleted items are explicitly needed. |
| `page` | integer | No | Page number of results to return. |
| `user` | string | No | Reactions made by this user. Defaults to the authed user. |
| `count` | integer | No | Number of items to return per page. |
| `limit` | integer | No | Maximum number of items to return; fewer items may be returned. Use with cursor-based pagination. |
| `cursor` | string | No | Pagination cursor. Set to `next_cursor` from a previous response's `response_metadata`. See Slack API pagination documentation for details. |
| `team_id` | string | No | Required when using an org-level token. The ID of the workspace to list reactions from. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Lookup Canvas Sections

**Slug:** `SLACKBOT_LOOKUP_CANVAS_SECTIONS`

Looks 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `criteria` | object | Yes | Search criteria to find sections. Use 'contains_text' to search for text within sections. Returns section IDs that match the criteria. |
| `canvas_id` | string | Yes | The unique identifier of the canvas to lookup sections in |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Mark reminder as complete

**Slug:** `SLACKBOT_MARK_REMINDER_AS_COMPLETE`

Marks a specific Slack reminder as complete using its `reminder` ID; **DEPRECATED**: This Slack API endpoint ('reminders.complete') was deprecated in March 2023 and is not recommended for new applications.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `team_id` | string | No | Encoded team id. Required if using an org-level token to specify which workspace the reminder belongs to. |
| `reminder` | string | No | The unique identifier of the Slack reminder to be marked as complete. This ID is typically obtained when a reminder is created or listed. Must be a reminder ID (format: 'Rm12345678'), not reminder text or name; use SLACK_LIST_REMINDERS to retrieve valid IDs. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Open DM

**Slug:** `SLACKBOT_OPEN_DM`

Opens 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `users` | string | No | Comma-separated string of user IDs (1 for a DM, or 2-8 for an MPIM) to open/resume a conversation. Order is preserved for MPIMs. Either `channel` or `users` must be provided. Accepts list input (will be converted to comma-separated string). Also accepts `user_ids` as alias. Do not pass emails, display names, or workspace usernames — only Slack user IDs (e.g., `U0123456789`). Do not provide both `users` and `channel` simultaneously. |
| `channel` | string | No | ID or name of an existing DM or MPIM channel to open/resume. Either `channel` or `users` must be provided. |
| `return_im` | boolean | No | If `true`, returns the full DM channel object. Applies only when opening a DM via a single user ID in `users` (not with `channel`). |
| `prevent_creation` | boolean | No | Do not create a direct message or multi-person direct message. This is used to see if there is an existing dm or mpdm. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Pin an item to a channel

**Slug:** `SLACKBOT_PIN_ITEM`

Pins a message to a specified Slack channel; the message must not already be pinned.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `channel` | string | Yes | The ID of the channel where the message will be pinned. |
| `timestamp` | string | No | Timestamp of the message to pin, in 'epoch_time.microseconds' format (e.g., '1624464000.000200'). If not provided, the most recent message in the channel will be pinned. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Remove call participants

**Slug:** `SLACKBOT_REMOVE_CALL_PARTICIPANTS`

Registers participants removed from a Slack call.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | ID of the call returned by the add method. |
| `users` | string | Yes | The list of users to remove as participants in the call. users is a JSON array with each user having a `slack_id` or `external_id`. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Remove reaction from item

**Slug:** `SLACKBOT_REMOVE_REACTION_FROM_ITEM`

Removes 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `file` | string | No | ID of the file to remove the reaction from. |
| `name` | string | Yes | Name of the emoji reaction to remove (e.g., 'thumbsup'), without colons. Must be Slack's canonical emoji name; non-canonical names return a 'no_reaction' error. |
| `channel` | string | No | Channel ID of the message. Required if `timestamp` is provided. |
| `timestamp` | string | No | Timestamp of the message. Required if `channel` is provided. |
| `file_comment` | string | No | ID of the file comment to remove the reaction from. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Remove remote file

**Slug:** `SLACKBOT_REMOVE_REMOTE_FILE`

Removes 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `file` | string | No | Slack-specific file ID. |
| `token` | string | No | Authentication token. |
| `external_id` | string | No | Creator-defined, globally unique ID (GUID) for the file. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Remove user from conversation

**Slug:** `SLACKBOT_REMOVE_USER_FROM_CONVERSATION`

Removes a specified user from a Slack conversation (channel); the caller must have permissions to remove users and cannot remove themselves using this action.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `user` | string | No | The ID of the user to be removed from the conversation. |
| `channel` | string | No | ID of the conversation (channel) to remove the user from. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Rename a conversation

**Slug:** `SLACKBOT_RENAME_CONVERSATION`

Renames 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | No | New name for the conversation. Must be 80 characters or less and contain only lowercase letters, numbers, hyphens, and underscores. |
| `channel` | string | No | ID of the conversation (channel) to rename. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Retrieve conversation information

**Slug:** `SLACKBOT_RETRIEVE_CONVERSATION_INFORMATION`

Retrieves 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `channel` | string | No | The ID of the conversation (channel, direct message, or multi-person direct message) to retrieve information for. Effectively required — omitting this parameter yields no useful data despite being marked optional. |
| `include_locale` | boolean | No | If true, the response will include the locale setting for the conversation. Defaults to false. |
| `include_num_members` | boolean | No | If true, the response will include the number of members in the conversation. Defaults to false. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get conversation members

**Slug:** `SLACKBOT_RETRIEVE_CONVERSATION_MEMBERS_LIST`

Retrieves 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `limit` | integer | No | The maximum number of members to return per page. Fewer items may be returned than the requested limit, even if more members exist and the end of the list hasn't been reached. |
| `cursor` | string | No | Pagination cursor value for fetching specific pages of results. To retrieve the next page, provide the `next_cursor` value obtained from the `response_metadata` of the previous API call. If omitted or empty, the first page of members is fetched. For more details on pagination, refer to Slack API documentation. Loop by passing `next_cursor` into subsequent calls until `next_cursor` is empty to avoid silently truncating large member lists. |
| `channel` | string | No | ID of the conversation (public channel, private channel, direct message, or multi-person direct message) for which to retrieve the member list. Public channel IDs typically start with 'C', private channels or multi-person direct messages (MPIMs) with 'G', and direct messages (DMs) with 'D'. Channel names are NOT accepted — only IDs. Obtain IDs via SLACK_FIND_CHANNELS or SLACK_LIST_CONVERSATIONS. For private channels and MPIMs, the app must have required scopes and be a member of the conversation, otherwise members may not be returned. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Retrieve user DND status

**Slug:** `SLACKBOT_RETRIEVE_CURRENT_USER_DND_STATUS`

Retrieves 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `user` | string | No | User ID to fetch DND status for. If not provided, fetches the DND status for the authenticated user. |
| `team_id` | string | No | Encoded team ID where the passed user param belongs. Required if an org token is used. If no user param is passed, then a team which has access to the app should be passed. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Retrieve detailed file information

**Slug:** `SLACKBOT_RETRIEVE_DETAILED_INFORMATION_ABOUT_A_FILE`

Retrieves detailed metadata and paginated comments for a specific Slack file ID; does not download file content.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `file` | string | No | ID of the file to retrieve information for. This is a required field. |
| `page` | string | No | Page number of comment results to retrieve. Expects a string representing an integer (e.g., '2'). Used for comment pagination. Slack's default is 1 if not provided. `cursor`-based pagination is generally preferred. |
| `count` | string | No | Number of comments to retrieve per page. Expects a string representing an integer (e.g., '20'). Used for comment pagination. Slack's default is 100 if not provided. |
| `limit` | integer | No | The maximum number of comments to retrieve. This is an upper limit, not a guarantee of how many will be returned. Primarily used for comment pagination. |
| `cursor` | string | No | Pagination cursor for retrieving comments. Set to `next_cursor` from a previous response's `response_metadata` to fetch the next page of comments. Essential for navigating through large sets of comments. See [pagination](https://slack.dev) for more details. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Retrieve detailed user information

**Slug:** `SLACKBOT_RETRIEVE_DETAILED_USER_INFORMATION`

Retrieves 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `user` | string | No | The ID of the user to retrieve information for. Must be a Slack user ID (U- or W-prefixed); passing emails, display names, or other non-ID strings returns a `user_not_found` error. |
| `include_locale` | boolean | No | Set to `true` to include the user's locale (e.g., `en-US`) in the response. Defaults to `false`. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Retrieve user profile information

**Slug:** `SLACKBOT_RETRIEVE_USER_PROFILE_INFORMATION`

Retrieves 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `user` | string | No | User ID to retrieve profile information for; defaults to the authenticated user. |
| `include_labels` | boolean | No | Include human-readable labels for custom profile fields. API defaults to false. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Revoke a file's public url

**Slug:** `SLACKBOT_REVOKE_FILE_PUBLIC_SHARING`

Revokes a Slack file's public URL, making it private; this is a no-op if not already public and is irreversible.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `file` | string | Yes | The ID of the file for which to revoke the public URL. This unique identifier typically starts with 'F'. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Schedule message

**Slug:** `SLACKBOT_SCHEDULE_MESSAGE`

Schedules 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `text` | string | No | This sends raw text only, use markdown_text field for formatting. Primary text of the message; formatting with `mrkdwn` applies. Required if `blocks` and `attachments` are not provided. |
| `parse` | string | No | Message text treatment: `full` for special formatting, `none` otherwise (default). See Slack's `chat.postMessage` docs for options. |
| `blocks` | string | No | **DEPRECATED**: Use `markdown_text` field instead. JSON array of structured blocks as a URL-encoded string for message layout and design. Required if `text` and `attachments` are not provided. |
| `channel` | string | No | Channel, private group, or DM channel ID (e.g., C1234567890) or name (e.g., #general) to send the message to. Bot must be a member of the target channel; missing membership returns `not_in_channel` error. |
| `post_at` | string | No | Unix EPOCH timestamp (integer seconds since 1970-01-01 00:00:00 UTC) for the future message send time. Must be strictly greater than current time (past values return `time_in_past` error). Always convert local times to UTC epoch seconds before use; Slack evaluates in UTC only. |
| `team_id` | string | No | Team ID for Enterprise Grid workspaces. Required for orgs with multiple workspaces. |
| `thread_ts` | string | No | Timestamp of the parent message for the scheduled message to be a thread reply. Must be float seconds (e.g., `1234567890.123456`). |
| `link_names` | boolean | No | Pass true to automatically link channel names (e.g., #general) and usernames (e.g., @user). NOTE: This parameter is deprecated by Slack; the linking behavior is primarily controlled by Slack's default message parsing. For explicit control, use the 'parse' parameter instead (set to 'full' to enable auto-linking). |
| `attachments` | string | No | This is Slack's legacy 'secondary attachments' field for adding rich formatting elements like colored sidebars, structured fields, and author info. Pass as a JSON string array. NOT for file/image uploads. To send files or images, use 'SLACK_UPLOAD_OR_CREATE_A_FILE_IN_SLACK' instead. |
| `unfurl_links` | boolean | No | Pass false to disable automatic link unfurling. Defaults to true. NOTE: Due to a known Slack API limitation, this parameter may not be respected for scheduled messages (works correctly for chat.postMessage but may be ignored by chat.scheduleMessage). |
| `unfurl_media` | boolean | No | Pass false to disable automatic media unfurling. Defaults to true. NOTE: Due to a known Slack API limitation, this parameter may not be respected for scheduled messages (works correctly for chat.postMessage but may be ignored by chat.scheduleMessage). |
| `markdown_text` | string | No | **PREFERRED**: Write your scheduled message in markdown for nicely formatted display. Supports headers (#), bold (**text**), italic (*text*), strikethrough (~~text~~), code (```), links ([text](url)), quotes (>), and dividers (---). Your message will be posted with beautiful formatting. |
| `reply_broadcast` | boolean | No | With `thread_ts`, makes reply visible to all in channel, not just thread members. Defaults to `false`. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Send ephemeral message

**Slug:** `SLACKBOT_SEND_EPHEMERAL_MESSAGE`

Sends 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `text` | string | No | The message text to display. Required unless 'blocks' or 'attachments' is provided. When using blocks, this serves as fallback text for notifications. Supports markdown formatting. |
| `user` | string | Yes | User ID of the user to send the ephemeral message to. |
| `parse` | string | No | Controls text parsing behavior. Use 'full' to enable automatic linking of @mentions, #channels, and URLs. Use 'none' to disable special parsing (URLs will still be clickable). Defaults to 'none'. |
| `blocks` | string | No | A JSON-based array of structured blocks, presented as a URL-encoded string. |
| `as_user` | boolean | No | Legacy parameter for authenticated user authorship. Defaults to true without chat:write:bot scope, false otherwise. Setting to true requires chat:write:user scope for the authenticated user to author the message. |
| `channel` | string | Yes | Channel, private group, or DM channel to send message to. Can be an encoded ID, or a name. |
| `team_id` | string | No | Team ID for Enterprise Grid workspaces. Required when using an org-level token to specify which workspace the message should be sent to. |
| `icon_url` | string | No | URL to an image to use as the icon for this message. Must be used in conjunction with as_user set to false, otherwise ignored. See authorship below. |
| `username` | string | No | Set your bot's user name. Must be used in conjunction with as_user set to false, otherwise ignored. See authorship below. |
| `thread_ts` | string | No | Provide another message's ts value to make this message a reply. Avoid using a reply's ts value; use its parent instead. |
| `icon_emoji` | string | No | Emoji to use as the icon for this message. Overrides icon_url. Must be used in conjunction with as_user set to false, otherwise ignored. See authorship below. |
| `link_names` | boolean | No | Find and link channel names and usernames. |
| `attachments` | string | No | This is Slack's legacy 'secondary attachments' field for adding rich formatting elements like colored sidebars, structured fields, and author info. Pass as a JSON string array. NOT for file/image uploads. To send files or images, use 'SLACK_UPLOAD_OR_CREATE_A_FILE_IN_SLACK' instead. |
| `markdown_text` | string | No | PREFERRED: Write your ephemeral message in markdown for nicely formatted display. Supports: headers (# ## ###), bold (**text** or __text__), italic (*text* or _text_), strikethrough (~~text~~), inline code (`code`), code blocks (```), links ([text](url)), block quotes (>), lists (- item, 1. item), dividers (--- or ***). IMPORTANT: Use \n for line breaks (e.g., 'Line 1\nLine 2'), not actual newlines. Incompatible with blocks or text parameters. Maximum 12,000 characters. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Share a me message in a channel

**Slug:** `SLACKBOT_SEND_ME_MESSAGE`

Sends 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `text` | string | No | Content of the 'me message', displayed as an action performed by the user (e.g., if text is 'is feeling happy', it appears as '*User is feeling happy*'). |
| `channel` | string | No | Specifies the target channel by its public ID (e.g., 'C1234567890'), private group ID, IM channel ID, or name (e.g., '#general', '@username'). |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Send message

**Slug:** `SLACKBOT_SEND_MESSAGE`

Posts a message to a Slack channel, DM, or private group; requires at least one content field (`markdown_text`, `text`, `blocks`, or `attachments`) — omitting all causes a `no_text` error. Fails with `not_in_channel`, `channel_not_found`, or `channel_is_archived` if the bot lacks access. Body limit ~4000 characters. Rate-limited at ~1 req/sec (HTTP 429, honor `Retry-After`). Not idempotent — duplicate calls post duplicate messages.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `text` | string | No | DEPRECATED: This sends raw text only, use markdown_text field. Primary textual content. Recommended fallback if using `blocks` or `attachments`. Supports mrkdwn unless `mrkdwn` is `false`. |
| `parse` | string | No | Message text parsing behavior. Set to 'full' to parse as user-typed (auto-links @mentions, #channels). Omit for default behavior (no special parsing). |
| `blocks` | string | No | DEPRECATED: Use `markdown_text` field instead. Block Kit layout blocks for rich/interactive messages. Accepts either a URL-encoded JSON string or a list of block dictionaries. See Slack API Block Kit docs for structure. |
| `mrkdwn` | boolean | No | Controls Slack mrkdwn formatting for the top-level `text` field ONLY. Set to `false` to disable formatting (text appears as-is with literal asterisks, underscores, etc.). Default `true` enables mrkdwn formatting (*bold*, _italic_, etc.). NOTE: This parameter has NO effect on `blocks` or `markdown_text` - block content always uses its own formatting rules. |
| `channel` | string | Yes | ID or name of the channel, private group, or IM channel to send the message to. Can be specified as either 'channel' or 'channel_id'. Do NOT include the '#' prefix (e.g., use 'general' not '#general') - any leading '#' will be automatically stripped. For DMs, use the channel ID returned by SLACK_OPEN_DM (starts with 'D'); usernames, emails, and user IDs are not valid DM targets. |
| `thread_ts` | string | No | Timestamp (`ts`) of an existing message to make this a threaded reply. Use `ts` of the parent message, not another reply. Example: '1476746824.000004'. |
| `link_names` | boolean | No | Automatically hyperlink channel names (e.g., #channel) and usernames (e.g., @user) in message text. Defaults to `false` for bot messages. |
| `attachments` | string | No | This is Slack's legacy 'secondary attachments' field for adding rich formatting elements like colored sidebars, structured fields, and author info to messages. Pass as a JSON string array. NOT for file/image uploads. To send a message with attachments of files or images, use the 'SLACK_UPLOAD_OR_CREATE_A_FILE_IN_SLACK' instead. |
| `unfurl_links` | boolean | No | Enable unfurling of text-based URLs. Defaults `false` for bots, `true` if `as_user` is `true`. |
| `unfurl_media` | boolean | No | Enable media previews (images, videos) from URLs. Set to `true` (default) to show media previews, `false` to hide them. |
| `markdown_text` | string | No | PREFERRED: Write your message in markdown for nicely formatted display. Supports: headers (# ## ###), bold (**text** or __text__), italic (*text* or _text_), strikethrough (~~text~~), inline code (`code`), code blocks (```), links ([text](url)), block quotes (>), lists (- item, 1. item), dividers (--- or ***), context blocks (:::context with images), and section buttons (:::section-button). IMPORTANT: Use \n for line breaks (e.g., 'Line 1\nLine 2'), not actual newlines. USER MENTIONS: To tag users, use their user ID with <@USER_ID> format (e.g., <@U1234567890>), not username. NOTE: Slack enforces a 50-block limit per message. Very long messages with extensive formatting may exceed this limit. If your message is very long, consider splitting it into multiple shorter messages or using simpler formatting. |
| `reply_broadcast` | boolean | No | If `true` for a threaded reply, also posts to main channel. Defaults to `false`. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Set a conversation's purpose

**Slug:** `SLACKBOT_SET_CONVERSATION_PURPOSE`

Sets the purpose (a short description of its topic/goal, displayed in the header) for a Slack conversation; the calling user must be a member.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `channel` | string | No | The ID of the conversation (channel, direct message, or group message) to set the purpose for. |
| `purpose` | string | No | The new purpose for the conversation. This text will be displayed as the channel description. The maximum length is 250 characters. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Set conversation read cursor

**Slug:** `SLACKBOT_SET_READ_CURSOR_IN_A_CONVERSATION`

Marks 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `ts` | string | No | The timestamp of the message to mark as the most recently read. Must be a Slack timestamp string with microsecond precision in the format 'UNIX_TIMESTAMP.MICROSECONDS' (e.g., '1625800000.000200'). |
| `channel` | string | No | The ID of the public channel, private channel, or direct message to set the read cursor for. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Set conversation topic

**Slug:** `SLACKBOT_SET_THE_TOPIC_OF_A_CONVERSATION`

Sets or updates the topic for a specified Slack conversation.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `topic` | string | No | The new topic for the conversation. It must be a string up to 250 characters long. Text formatting and linkification are not supported. |
| `channel` | string | No | The ID of the public channel, private channel, direct message, or multi-person direct message conversation for which the topic will be set. Must be a channel ID (C/G/D prefix), not a human-readable name like '#general'. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Mark user as active

**Slug:** `SLACKBOT_SET_USER_ACTIVE`

Tool to mark a user as active in Slack. Note: This endpoint is deprecated and non-functional - it exists for backwards compatibility but does not perform any action.

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Set user presence

**Slug:** `SLACKBOT_SET_USER_PRESENCE`

Manually 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).

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `presence` | string ("auto" | "away") | Yes | The presence state to set for the user. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Share a remote file in channels

**Slug:** `SLACKBOT_SHARE_REMOTE_FILE`

Shares a remote file, which must already be registered with Slack, into specified Slack channels or direct message conversations.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `file` | string | No | The unique ID of the remote file registered with Slack. Either this `file` field or the `external_id` field (or both) is required to identify the file. |
| `channels` | string | Yes | A comma-separated list of channel IDs where the remote file will be shared. These can include public channel IDs, private channel IDs, or direct message channel IDs. |
| `external_id` | string | No | The globally unique identifier (GUID) for the remote file, as provided by the app that registered it with Slack. Either this `external_id` field or the `file` field (or both) is required to identify the file. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Start call

**Slug:** `SLACKBOT_START_CALL`

Registers a new call in Slack using `calls.add` for third-party call integration; `created_by` is required if not using a user-specific token.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `title` | string | No | The name or title for the call. This will be displayed in Slack to identify the call. |
| `users` | string | No | A JSON string representing an array of user objects to be registered as participants in the call. Each user object in the array should define a participant using their `slack_id` (Slack User ID) and/or an `external_id` (an identifier from the third-party application, unique to that user within that application). For instance: `'''[{"slack_id": "U012A3BCD4E"}, {"external_id": "user-xyz@example.com", "slack_id": "U012A3BCD4F"}]'''`. |
| `join_url` | string | Yes | The URL required for a client to join the call (e.g., a web join link). This field is mandatory. Must be a valid third-party call system URL (e.g., web join link), not a Slack channel or message URL. |
| `created_by` | string | No | Slack user ID of the creator; optional (defaults to authenticated user) if using a user token, otherwise required. |
| `date_start` | integer | No | The start time of the call, specified as a UTC UNIX timestamp in seconds. For example, `1678886400` corresponds to March 15, 2023, at 12:00 PM UTC. |
| `external_unique_id` | string | Yes | A unique identifier for the call, supplied by the third-party call provider. This ID must be unique across all calls from that specific service. This field is required. |
| `external_display_id` | string | No | An optional, human-readable identifier for the call, supplied by the third-party call provider. If provided, this ID will be displayed in the Slack call object interface. |
| `desktop_app_join_url` | string | No | An optional URL that, when provided, allows Slack clients to attempt to directly launch the third-party call application. This is typically a deep link URI for the specific application. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Unarchive channel

**Slug:** `SLACKBOT_UNARCHIVE_CHANNEL`

Reverses conversation archival.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `channel` | string | Yes | ID of conversation to unarchive |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Unpin message from channel

**Slug:** `SLACKBOT_UNPIN_ITEM`

Unpins a message, identified by its timestamp, from a specified channel if the message is currently pinned there; this operation is destructive.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `channel` | string | Yes | The ID of the channel where the message is pinned (e.g., a public channel, private channel, or direct message). |
| `timestamp` | string | No | Timestamp of the message to unpin. This is required to identify the specific message to be removed from the channel's pinned items. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update call information

**Slug:** `SLACKBOT_UPDATE_CALL_INFO`

Updates the title, join URL, or desktop app join URL for an existing Slack call identified by its ID.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Unique identifier of the call to update, obtained when a call is created (e.g., via `calls.add` Slack API method). |
| `title` | string | No | New title for the call. |
| `join_url` | string | No | New URL for clients to join the call. |
| `desktop_app_join_url` | string | No | URL to directly launch the third-party call application from Slack clients. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update an existing remote file

**Slug:** `SLACKBOT_UPDATE_REMOTE_FILE`

Updates metadata or content details for an existing remote file in Slack; this action cannot upload new files or change the fundamental file type.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `file` | string | No | Slack's unique identifier for the remote file (e.g., `F12345678`). Used to identify the file if `external_id` is not provided. One of `file` or `external_id` is required to specify the file to update. |
| `title` | string | No | New title for the remote file. If omitted, the current title remains unchanged. |
| `token` | string | No | Authentication token for authorizing the API request to Slack. |
| `filetype` | string | No | New filetype for the remote file. This typically describes the kind of file, e.g., `pdf`, `gdoc`, `image`, `text`. See Slack API documentation for specific supported `filetype` values. Providing an inaccurate filetype might affect how the file is handled or displayed. |
| `external_id` | string | No | Creator-defined Globally Unique Identifier (GUID) for the remote file. Used to identify the file if `file` ID is not provided. One of `file` or `external_id` is required to specify the file to update. |
| `external_url` | string | No | New publicly accessible URL for the remote file. If provided, this updates the link associated with the file in Slack. |
| `preview_image` | string | No | A string that references the new preview image for the document. The referenced image data will be sent as `multipart/form-data`. This could be a local file path (if supported by the client), a public URL, or base64 encoded image data. Max 1MB. Updates the file's preview in Slack. |
| `indexable_file_contents` | string | No | Plain text content extracted from the remote file, used by Slack to improve searchability. This can be a summary or the full text. Maximum 1MB. If provided, updates the searchable content. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update a Slack message

**Slug:** `SLACKBOT_UPDATES_A_MESSAGE`

Updates a Slack message, identified by `channel` ID and `ts` timestamp, by modifying its `text`, `attachments`, or `blocks`; provide at least one content field, noting `attachments`/`blocks` are replaced if included (`[]` clears them).

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `ts` | string | Yes | Timestamp of the message to update (string, Unix time with microseconds, e.g., `'1234567890.123456'`). |
| `text` | string | No | This sends raw text only, use markdown_text field for formatting. New message text (plain or mrkdwn). Not required if `blocks` or `attachments` are provided. See Slack formatting rules. |
| `parse` | string ("none" | "full") | No | Parse mode for `text`: `'full'` (auto-links @mentions and #channels) or `'none'` (literal text). If not provided, uses Slack's default behavior. |
| `blocks` | string | No | **DEPRECATED**: Use `markdown_text` field instead. Block Kit layout blocks for rich/interactive messages. Accepts either a JSON string array or a list of block dictionaries. Replaces existing blocks if field is provided; use `[]` to clear. Omit field to leave blocks untouched. Required if `text` and `attachments` are absent. See Slack API for format. |
| `as_user` | boolean | No | Pass `true` to update the message as the authenticated user; applicable to bot users as well. |
| `channel` | string | Yes | The ID of the channel containing the message to be updated. |
| `file_ids` | array | No | Array of file IDs to attach to the updated message. Files must already be uploaded to Slack. |
| `metadata` | object | No | JSON object containing `event_type` (string) and `event_payload` (dict) fields for adding custom metadata to the message. |
| `link_names` | boolean | No | Set to `true` to link channel/user names in `text`. If not provided, Slack's default update behavior may override original message's linking settings. |
| `attachments` | string | No | This is Slack's legacy 'secondary attachments' field for adding rich formatting elements like colored sidebars, structured fields, and author info. Accepts either a JSON string array or a list of attachment dictionaries. Replaces existing attachments if provided; use `[]` to clear. NOT for file/image uploads. To send files or images, use 'SLACK_UPLOAD_OR_CREATE_A_FILE_IN_SLACK' instead. |
| `markdown_text` | string | No | **PREFERRED**: Write your updated message in markdown for nicely formatted display. Supports headers (#), bold (**text**), italic (*text*), strikethrough (~~text~~), code (```), links ([text](url)), quotes (>), and dividers (---). Your message will be posted with beautiful formatting. |
| `reply_broadcast` | boolean | No | If `true` and the message is a thread reply, broadcast the updated message to the channel. Defaults to `false`. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Slack user group

**Slug:** `SLACKBOT_UPDATE_USER_GROUP`

Updates 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | No | New name for the User Group. Must be unique among User Groups. |
| `handle` | string | No | New mention handle. Must be unique among channels, users, and User Groups. |
| `team_id` | string | No | Encoded team (workspace) ID where the User Group exists. Required if using an org-level token. Will be ignored if the API call is sent using a workspace-level token. |
| `channels` | string | No | Comma-separated encoded channel IDs to set as default channels. |
| `usergroup` | string | Yes | Encoded ID of the existing User Group to update. |
| `description` | string | No | New short description for the User Group. |
| `include_count` | boolean | No | If true, include the number of users in the User Group in the response. |
| `enable_section` | boolean | No | Configure this user group to show as a sidebar section for all group members. Only relevant if group has 1 or more default channels added. |
| `additional_channels` | string | No | Comma-separated encoded channel IDs for which the User Group can custom add usergroup members to. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update user group members

**Slug:** `SLACKBOT_UPDATE_USER_GROUP_MEMBERS`

Replaces all members of an existing Slack User Group with a new list of valid user IDs.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `users` | string | Yes | Comma-separated string of encoded user IDs for the new, complete member list, replacing all existing members. User IDs typically start with 'U' or 'W'. |
| `team_id` | string | No | Encoded team ID where the User Group exists. Required when using an org-level token (Enterprise Grid). Ignored for workspace-level tokens. |
| `usergroup` | string | Yes | The encoded ID of the User Group whose members are to be updated. This ID typically starts with 'S'. |
| `include_count` | boolean | No | If true, the response `usergroup` object includes `user_count` and potentially `channel_count` fields, reflecting counts after the update. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Upload or create a file in Slack

**Slug:** `SLACKBOT_UPLOAD_OR_CREATE_A_FILE_IN_SLACK`

Upload 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `file` | object | No | File to upload. Either 'content' or 'file' must be provided, but not both. |
| `title` | string | No | Title of the file, displayed in Slack. |
| `token` | string | No | Authentication token; requires 'files:write' scope. |
| `content` | string | No | Text content of the file; use for text-based files. Either 'content' or 'file' must be provided, but not both. |
| `channels` | string | No | Channel ID where the file will be shared; if omitted, file is private to the uploader. Use channel ID (e.g., C1234567890) not channel name. Note: Due to API changes, only the first channel ID is used if multiple are provided. App must be a member of the target channel or the upload fails with `not_in_channel` or `channel_not_found`. |
| `filename` | string | No | Filename to be displayed in Slack. Required when using 'content' parameter. |
| `filetype` | string | No | Deprecated: File type detection is now automatic. This parameter is preserved for backward compatibility but no longer affects file uploads. |
| `thread_ts` | string | No | Timestamp of a parent message to upload this file as a reply; use the original message's 'ts' value (e.g., '1234567890.123456'). |
| `initial_comment` | string | No | Optional message to introduce the file in specified 'channels'. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | object | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |


## Triggers

### New Channel Created Trigger

**Slug:** `SLACKBOT_CHANNEL_CREATED`

**Type:** webhook

Triggered when a new channel is created in Slack.

#### Payload

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `created` | integer | Yes | The timestamp of when the channel was created, formatted as a Unix timestamp |
| `creator` | string | Yes | The ID of the user who created the channel |
| `id` | string | Yes | The ID of the channel |
| `name` | string | Yes | The name of the channel |

### Reaction Added Trigger

**Slug:** `SLACKBOT_REACTION_ADDED`

**Type:** webhook

Triggered when a reaction is added to a message in Slack.

#### Payload

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `bot_id` | string | Yes | The ID of the bot that posted the message |
| `channel_type` | string | Yes | The type of the channel where the message was posted |
| `event_ts` | string | Yes | The timestamp of the reaction event. Formatted as a Unix timestamp |
| `message_channel` | string | Yes | The ID of the channel where the message that was reacted to is located |
| `message_ts` | string | Yes | The timestamp of the message that was reacted to. Formatted as a Unix timestamp |
| `message_user` | string | Yes | The ID of the user who owns the message that was reacted to |
| `reaction` | string | Yes | The type of reaction that was added |
| `team_id` | string | Yes | The ID of the team where the message was posted |
| `user` | string | Yes | The ID of the user who added the reaction |

### Reaction Removed Trigger

**Slug:** `SLACKBOT_REACTION_REMOVED`

**Type:** webhook

Triggered when a reaction is removed from a message.

#### Payload

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `bot_id` | string | Yes | The ID of the bot that posted the message |
| `channel_type` | string | Yes | The type of the channel where the message was posted |
| `event_ts` | string | Yes | The timestamp of the reaction event. Formatted as a Unix timestamp |
| `message_channel` | string | Yes | The ID of the channel where the message that was reacted to is located |
| `message_ts` | string | Yes | The timestamp of the message that was reacted to. Formatted as a Unix timestamp |
| `message_user` | string | Yes | The ID of the user who owns the message that was reacted to |
| `reaction` | string | Yes | The type of reaction that was added |
| `team_id` | string | Yes | The ID of the team where the message was posted |
| `user` | string | Yes | The ID of the user who added the reaction |

### New Bot Message Received Trigger

**Slug:** `SLACKBOT_RECEIVE_BOT_MESSAGE`

**Type:** webhook

Triggered when a new bot message is posted to a Slack channel.

#### Payload

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `attachments` | array | No | Attachments included with the bot message, if any. Slack apps (like Datadog) often send their content via attachments rather than the top-level text field. |
| `bot_id` | string | No | The ID of the bot that posted the message |
| `channel` | string | Yes | The ID of the channel where the bot message was posted |
| `channel_type` | string | No | The type of the channel where the bot message was posted |
| `files` | array | No | Files uploaded with the bot message, if any. Present when subtype is 'file_share'. Contains file metadata including name, mimetype, and URLs. |
| `subtype` | string | Yes | The subtype of the message (should be 'bot_message') |
| `team_id` | string | No | The ID of the team where the bot message was posted |
| `text` | string | Yes | The text content of the bot message |
| `ts` | string | Yes | The timestamp of the bot message |
| `username` | string | No | The username of the bot that posted the message |

### New Direct Message Received Trigger

**Slug:** `SLACKBOT_RECEIVE_DIRECT_MESSAGE`

**Type:** webhook

Triggered when a new direct message (DM) is sent to a user in Slack.

#### Payload

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `attachments` | array | No | Attachments included with the direct message, if any. Some Slack apps (like Datadog) send content via attachments rather than the top-level text field. |
| `bot_id` | string | Yes | The ID of the bot that sent the direct message |
| `channel` | string | Yes | The ID of the direct message channel |
| `channel_type` | string | Yes | The type of the channel (should be 'im' for direct messages) |
| `files` | array | No | Files uploaded with the direct message, if any. Present when subtype is 'file_share'. Contains file metadata including name, mimetype, and URLs. |
| `team_id` | string | Yes | The ID of the team where the direct message was sent |
| `text` | string | Yes | The text content of the direct message |
| `ts` | string | Yes | The timestamp of the direct message |
| `user` | string | Yes | The ID of the user who sent the direct message |

### New Private Channel Message Received Trigger

**Slug:** `SLACKBOT_RECEIVE_GROUP_MESSAGE`

**Type:** webhook

Triggered when a new message is posted to a private channel in Slack.

#### Payload

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `attachments` | array | No | Attachments included with the message, if any. Some Slack apps (like Datadog) send content via attachments rather than the top-level text field. |
| `bot_id` | string | Yes | The ID of the bot that sent the message |
| `channel` | string | Yes | The ID of the private channel |
| `channel_type` | string | Yes | The type of the channel (should be 'group' for private channels) |
| `files` | array | No | Files uploaded with the message, if any. Present when subtype is 'file_share'. Contains file metadata including name, mimetype, and URLs. |
| `team_id` | string | Yes | The ID of the team where the message was sent |
| `text` | string | Yes | The text content of the message |
| `ts` | string | Yes | The timestamp of the message |
| `user` | string | Yes | The ID of the user who sent the message in the private channel |

### New Message Received Trigger

**Slug:** `SLACKBOT_RECEIVE_MESSAGE`

**Type:** webhook

Triggered when a new message is posted to a Slack channel.

#### Payload

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `attachments` | array | No | Attachments included with the message, if any. Some Slack apps (like Datadog) send content via attachments rather than the top-level text field. |
| `bot_id` | string | No | The ID of the bot that posted the message |
| `channel` | string | Yes | The ID of the channel where the message was posted |
| `channel_type` | string | No | The type of the channel where the message was posted |
| `files` | array | No | Files uploaded with the message, if any. Present when subtype is 'file_share'. Contains file metadata including name, mimetype, and URLs. |
| `team_id` | string | No | The ID of the team where the message was posted |
| `text` | string | Yes | The text content of the message |
| `ts` | string | Yes | The timestamp of the message |
| `user` | string | No | The ID of the user who posted the message |

### New Multi-Person Direct Message Received Trigger

**Slug:** `SLACKBOT_RECEIVE_MPIM_MESSAGE`

**Type:** webhook

Triggered when a new message is posted to a multi-person direct message in Slack.

#### Payload

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `attachments` | array | No | Attachments included with the message, if any. Some Slack apps (like Datadog) send content via attachments rather than the top-level text field. |
| `bot_id` | string | Yes | The ID of the bot that sent the message |
| `channel` | string | Yes | The ID of the multi-person direct message channel |
| `channel_type` | string | Yes | The type of the channel (should be 'mpim' for multi-person direct messages) |
| `files` | array | No | Files uploaded with the message, if any. Present when subtype is 'file_share'. Contains file metadata including name, mimetype, and URLs. |
| `team_id` | string | Yes | The ID of the team where the message was sent |
| `text` | string | Yes | The text content of the message |
| `ts` | string | Yes | The timestamp of the message |
| `user` | string | Yes | The ID of the user who sent the message in the multi-person direct message |

### Thread Reply Received Trigger

**Slug:** `SLACKBOT_RECEIVE_THREAD_REPLY`

**Type:** webhook

Triggered when reply is added to a message in a thread.
    Excludes the parent message_replied event by design (ts != thread_ts check).

#### Payload

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `attachments` | array | No | Attachments included with the thread reply, if any. Some Slack apps (like Datadog) send content via attachments rather than the top-level text field. |
| `bot_id` | string | No | The ID of the bot that posted the message |
| `channel` | string | Yes | The ID of the channel where the message was posted |
| `channel_type` | string | No | The type of the channel where the message was posted |
| `files` | array | No | Files uploaded with the thread reply, if any. Present when subtype is 'file_share'. Contains file metadata including name, mimetype, and URLs. |
| `parent_user_id` | string | No | The ID of the user who posted the parent message |
| `reply_count` | integer | No | The number of replies in the thread |
| `team_id` | string | No | The ID of the team where the message was posted |
| `text` | string | No | The text content of the message (may be None for block-only replies) |
| `thread_ts` | string | Yes | The timestamp of the parent message in the thread |
| `ts` | string | Yes | The timestamp of the message |
| `user` | string | No | The ID of the user who posted the message |
