Send Reply

Description

Sends a reply to a message in a channel.

Project compatibility

Windows | Cross-platform

Configuration

• Connection ID - The connection established in Integration Service. Access the dropdown menu to choose, add, or manage connections.

• Channel names/IDs - The names or IDs of the channel. Select the channel from the available drop-down list or enter the channel name or ID, in comma-separated format. This field supports String type input.
• Message timestamp - The timestamp (message ID) of the message. You can retrieve this from the output of the Send Message to Channel activity or from a Button Clicked trigger. You can also retrieve it from the message or thread URL in Slack (select More actions > Copy link) in the Slack. If the URL is https://uipathsanbox.slack.com/archives/C04A69QDF5W/p1667548719250469, then you can get thread_ts by adding a dot (.) after the tenth digit of the trailing ID (starting after p). So, for the above example, the thread_ts would be 1667548719.250469. This field supports String type input.
• Message - The formatted text of the message to be sent. This is also the main block section text. This field supports String type input. See Formatting text for app surfaces for formatting rules.
• Send as - Whether to send the message as the app bot, i.e., using Bot token, or yourself, i.e., user token. Select one of the two options from the available drop-down list.
• Message fields - Enter field/values in the following format: field1:value;field2:value. These fields are displayed below the main section text in a two-column format. You can also enter variables such as ID, name, event trigger output etc. This field supports String type input.
• Buttons actions - Button action properties in comma-separated format: action ID (required), action name (required), style (primary/danger), confirmation title, confirm ok title, confirm deny title. A maximum of five button actions separated by ; can be provided. For example: action1,Approve,primary;action2,Reject,danger;Confirm,Sure?,Yes,No. All action properties (except style) are customer/user defined. Action names IDs must be unique among buttons. Confirmation title, text, ok title, deny title must be used together. This field supports String type input.
• Image URL - The URL of the secondary image attachment can be shared as part of the message. The image is always at the bottom of the entire message block. This field supports String type input.

Manage Properties

Use the Manage Properties wizard to configure or use any of the object's standard or custom fields. You can select fields to add them to the activity canvas. The added standard or custom fields are available in the Properties panel (in Studio Desktop) or under Show additional properties (in Studio Web).

Additional properties

• Formatting options (parse) - Change how messages are treated. Select none for removing hyperlinks and full to ignore the Slack default formatting.
• Link names - Specifies whether to link and mention all the user groups automatically if the respective names are mentioned in the text message. Boolean value.
• Unfurl links - Specifies whether to display the preview of the links mentioned in the text message. Boolean value.
• Bot name - Only supported with Bot Token connection. Customize the bot’s user name when sending messages. If no value is entered, the default bot name is UiPath.passed.
• Bot icon - Only supported with Bot Token connection. Customize the bot’s icon with an emoji available in the workspace. For example, :chart_with_upwards_trend:. If you provide an emoji that is not available in the workspace, it is ignored.

Output

• Message Timestamp - The timestamp (message ID) of the sent message. Automatically generated output variable.
• Conversation reply - The output send reply. Automatically generated output variable.

Example

You can provide the following input for Buttons actions and Message fields:

The final Slack button message looks as follows:

When you click the Reject button, a confirmation dialog box is displayed:

You can configure the response to the above button clicks in a separate workflow using the Button Clicked event. To ensure the button is clicked only once, use Send Button Response in the workflow along with Button Clicked to replace or delete the button message after first click.

For a detailed user guide, see Use Slack Buttons when an opportunity is won in the CRM system.