Skip to main content
Feedback

Slack operation

The Slack operation defines how to interact with your Slack account.

The operation represents a specific action (Query, Create, Update, File Upload, etc.) to be performed against a specific Slack record type or object type (files, groups, channels, etc.). Create a separate operation component for each action/object combination required for your integration.

The Slack operation supports the following actions:

  • Get — retrieves channels info, files info, groups info, users info, users presence

  • Query — searches channels history, channels list, files, files list, groups list, group history, users list, usergroups list, messages

  • Create — creates channels, chat messages, groups, child groups, usergroups

  • Delete — deletes chats and files

  • Update — updates chats and usergroups

  • Execute — writes to the following endpoints:

    • Channels — archive, invite, join, kick, leave, mark, rename, setPurpose, setTopic, unarchive
    • Files — revokePublicURL, sharedPublicURL, upload binary, upload text
    • Groups — archive, close, invite, kick, leave, mark, open, rename, setPurpose, setTopic, unarchive
    • Usergroups — disable and enable

  • File Upload - upload files to Slack workspaces and optionally share them in channels. This operation has been enhanced to use Slack's latest file upload API while maintaining full backward compatibility with existing processes. The File Upload operation supports two upload types:

    • File Upload - Text: Upload text content as a file (for example, log files, reports, transcripts, or code snippets; encoded as UTF-8). Required fields: filename, content
    • File Upload - Binary: Upload binary file content (images, PDFs, documents, etc.). Required fields: filename, file

Options tab

Click Import Operation, then use the Import wizard to select the object with which you want to integrate. The following table describes the fields for each action type:

Connector Action - Displays the action you specified in the Import Wizard.

Tracking Direction - Select the document tracking direction for the operation, either Input Documents or Output Documents. This setting enables you to choose which document appears in Process Reporting. Start steps always track output documents regardless of your selection.

note

If the tracking direction is read-only, the feature to change the direction is either unavailable or the developer set the configuration to read-only. The default value you see shows you which document appears in Process Reporting.

Request Profile (Execute, Create, Delete, Update)
The auto-generated request JSON profile.

Response Profile (Query, Execute, Create, Get, Delete, Update)
The auto-generated response JSON profile.

Return Application Error Responses - This setting controls whether an application error prevents an operation from completing:

  • If you clear the setting, the process stops and reports the error on the Process Reporting page.
  • If you select the setting, processing continues and passes the error response to the next component processed as the connection output.
On this Page