Slack

Handle Initialize Authorization

post

Handle integration initialization request.

Body
or
Responses
chevron-right
200

Successful Response

application/json
Responseany
post
/connectors/slack/integrations

No content

Handle User Has Integration

get

Handle user integration existence check.

Responses
chevron-right
200

Successful Response

application/json
Responseany
get
/connectors/slack/integration-exists
200

Successful Response

No content

Auth Schema

get

Handle authentication schema request.

Responses
chevron-right
200

Successful Response

application/json
Responseany
get
/connectors/slack/auth-schema
200

Successful Response

No content

Get Integration

get
Path parameters
user_identifierstringRequired
Responses
chevron-right
200

Successful Response

application/json
Responseany
get
/connectors/slack/integrations/{user_identifier}

No content

Select Integration

post
Path parameters
user_identifierstringRequired
Responses
chevron-right
200

Successful Response

application/json
Responseany
post
/connectors/slack/integrations/{user_identifier}

No content

Remove Integration

delete
Path parameters
user_identifierstringRequired
Responses
chevron-right
200

Successful Response

application/json
Responseany
delete
/connectors/slack/integrations/{user_identifier}

No content

Success Authorize Callback

get
Responses
chevron-right
200

Successful Response

application/json
Responseany
get
/connectors/slack/success-authorize-callback
200

Successful Response

No content

Conversations List

post

Lists all channels in a Slack team

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
queryany ofOptional

query parameters

or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/conversations_list

Conversations Members

post

Retrieve members of a conversation

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/conversations_members

Conversations Info

post

Retrieves information about a conversation (channel)

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/conversations_info

Users Conversations

post

List conversations the calling user may access

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
queryany ofOptional

Query parameters for the HTTP request

or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/users_conversations

Conversations History

post

Fetches a conversation's history of messages and events

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/conversations_history

Conversations Replies

post

Retrieve a thread of messages posted to a conversation

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/conversations_replies

Conversations Create

post

Initiates a public or private channel-based conversation

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/conversations_create

Conversations Rename

post

Renames a conversation

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/conversations_rename

Conversations Set Purpose

post

Sets the channel description

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/conversations_set_purpose

Conversations Set Topic

post

Sets the topic for a conversation

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/conversations_set_topic

Conversations Archive

post

Archives a conversation

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/conversations_archive

Conversations Unarchive

post

Reverses conversation archival

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/conversations_unarchive

Conversations Open

post

Opens or resumes a direct message or multi-person direct message

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/conversations_open

Conversations Close

post

Closes a direct message or multi-person direct message

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/conversations_close

Chat Post Message

post

Sends a message to a Slack channel, private group, or direct message

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/chat_post_message

Chat Post Ephemeral

post

Sends an ephemeral message to a user in a channel

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/chat_post_ephemeral

Chat Update

post

Updates a message in a Slack channel

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/chat_update

Chat Delete

post

Deletes a message from a conversation

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/chat_delete

Chat Schedule Message

post

Schedules a message to be sent to a channel at a specified time in the future

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/chat_schedule_message

Chat Scheduled Messages List

post

Returns a list of scheduled messages

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
bodyany ofOptional

Body parameters for the request

or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/chat_scheduled_messages_list

Chat Delete Scheduled Message

post

Deletes a pending scheduled message from the queue.

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/chat_delete_scheduled_message

Users List

post

Lists all users in a Slack team

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/users_list

Users Info

post

Gets information about a user

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/users_info

Users Get Presence

post

Gets user presence information

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
queryany ofOptional

Query parameters for the HTTP request

or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/users_get_presence

Users Set Presence

post

Sets user presence information

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/users_set_presence

Emoji List

post

Lists custom emoji for a team

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
queryany ofOptional

Query parameters for the HTTP request

or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/emoji_list

Bookmarks List

post

List bookmarks for a channel in Slack

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/bookmarks_list

Bookmarks Add

post

Add bookmark to a channel

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/bookmarks_add

Bookmarks Edit

post

Edit bookmark in a Slack channel

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/bookmarks_edit

Bookmarks Remove

post

Remove bookmark from the channel

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/bookmarks_remove

Pins List

post

Lists items pinned to a channel

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/pins_list

Pins Add

post

Pins an item to a channel

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/pins_add

Pins Remove

post

Un-pins an item from a channel

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/pins_remove

Reactions List

post

Lists reactions made by a user

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/reactions_list

Reactions Get

post

Gets reactions for an item (file, file comment, channel message, group message, or direct message)

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/reactions_get

Reactions Add

post

Adds a reaction (emoji) to a message in a Slack channel

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/reactions_add

Reactions Remove

post

Removes a reaction (emoji) from an item (file, file comment, channel message, group message, or direct message)

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/reactions_remove

Reminders List

post

Lists all reminders created by or for a given user

Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/reminders_list
200

Successful Response

Reminders Info

post

Gets information about a reminder

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/reminders_info

Search All

post

Searches for messages and files matching a query

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/search_all

Search Files

post

Searches for files matching a query in Slack

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/search_files

Search Messages

post

Searches for messages matching a query

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/slack/search_messages

Last updated