Workato actions for MS Teams

Workbot actions allow you to post messages & replies to users or channels as Workbot.

Additionally, Workbot also includes custom actions. This action allows you to utilize Microsoft Graph APIs (v1.0).

Workbot supports 3 actions:

Post reply

Post reply allows you to post a message back to a user when a Workbot command is invoked. Replies are posted directly to the user or in-channel, depending on where the command was invoked.

Post reply Example of a post reply listing open opportunities from Salesforce

This reply can be a simple text message about a task's completion, or more advanced like prompting users on subsequent actions.

You can optionally include 1 fact set (a set of name-value pairs), 1 pick list, buttons and images.

Post reply must always be paired with a Workbot command

Post reply recipe Recipe perspective of the post reply example above

Post message

The post message actions allows you to post a message to a user or a channel. It is similar to Post reply, but with an additional field called Message recipient. This field allows you to specify where to post the message (direct to user, or to channel).

Use post message if you:

  1. Are using Workbot to post event notifications from another application, e.g. New/updated incident in ServiceNow. Since the trigger is not a Workbot command, Post message must be used so you can specify the 'Message recipient' for the event.

  2. Want control over where Workbot should post the message, instead of sending it where the Workbot command was invoked (which is what Post reply does automatically)

  3. Want to use advanced features like updating a previous message.

Message recipient

Message recipient allows you post a message to directly to a user or to a channel you specify. Use the ID datapill (under Conversation) from the output of a Workbot command. To pick a member or channel instead, toggle to "Select from list".

Message recipient Message recipient example

Advanced section

The advanced section has 2 fields: Post as raw JSON and Message to update.

Post as raw JSON

This field is for advanced users who want to fully customize the message formatting. When set to Yes, all other fields will be hidden. Should include "type": "message", followed by "attachments", e.g.

{
    "type": "message",
    "attachments": [
        {
            "contentType": "application/vnd.microsoft.card.adaptive",
            "content": {
                "type": "AdaptiveCard",
                "version": "1.0",
                "body": [
                    {
                        "type": "TextBlock",
                        "text": "Hello World!",
                        "size": "large"
                    }
                ]
            }
        }
    ]
}

For more details, refer to Microsoft's Adaptive Card Designer.

Message to update

Message to update allows you to overwrite a previously posted message from an earlier action step. Simply use the Original message ID datapill (from the output of a Workbot command), or the ID datapill (from the output of a Post message or Post reply action).

Original message ID Original message ID

Message to update example Message to update

Input fields

Post reply fields Post reply & Post message follow the same message structure

Both post reply and post message actions follow a fixed structure, with a preceding Envelope text and Message container. Text input fields support markdown syntax.

The table below lists the input fields in the post reply action.

Group Input Description
Envelope text* First message, preceding any text, images, or other elements in the message container. Support markdown.
Heading* Heading Heading text.
Subheading* Subheading text. Supports markdown.
Link text* Use markdown to add text links, e.g. [Salesforce](https://www.salesforce.com/).
Heading thumbnail Provide image URL of thumbnail. Displays to the left of heading text.
Body* Body text Main body text of message. Supports markdown.
Image Provide image URL. Displays below body text.
Fact set Text* Title of fact.
Value* Value of fact.
Pick list Pick list name* Name of picklist. Displays before choices.
Pick list style Compact displays choices in a drop-down menu, while Expanded displays all choices with radio buttons.
Choice parameter Parameter name to store the choice value. This is a required field when passing parameters to another recipe, otherwise the value will not be passed.
Title Text to display for choice. Cannot contain : or ,.
Value Value to pass to Choice parameter if chosen. Cannot contain : or ,.
Buttons Prompt text for buttons* Prompt that displays before buttons. Useful in providing context for the buttons that follow.
Button text Text to be displayed on the button.



Submit button command Workbot command to execute when button is clicked, e.g. create_ticket. Only after configuring the command in a Workbot for MS Teams trigger block can that command be visible in the dropdown list.
Additional parameters Parameter values to be passed onto the next recipe when button is clicked, e.g.

{
"sys_id": "sys_id"
"summary": "Summary",
"description": "Description"
}
Datapills need to be wrapped in double quotes and parameter names must be in all lowercase. Parameters can be user-specified, like the urgency of an issue in ServiceNow, or recipe information, like the Message ID of a previous MS Teams message.
Advanced Post as raw JSON For advanced users to fully customize the message formatting.
Message to update Use message ID from the output of a post reply or post message action to update that message with this one.
*Supports markdown ## Using dynamic lists in action fields Fact sets, pick lists and buttons can be generated dynamically using a list datapill (for more information on lists, see the [list management guide](https://docs.workato.com/features/list-management.html)) From the fields, click on the horizontal ellipses on the top-right and choose 'Dynamic list'. This should bring up the dynamic list option. ![Dynamic buttons](/assets/images/workbot-for-teams/dynamic-buttons.png) The following table shows what goes into the dynamic buttons fields:
Input field Description
Buttons source list List datapills have a list icon next to them in the datatree, e.g. Salesforce users:
Button text The title of the button to be displayed. Typically, you want to use datapills from the list datapill, e.g. Salesforce user name, a datapill from the Salesforce users list:
Submit button command Choose from a list of existing Workbot command recipes or key in a new command. Clicking on this button will trigger the recipe with the corresponding command trigger.
Additional parameters Key in name-value pairs to pass onto the next recipe as additional parameters. Format should be JSON with name-value pairs, e.g.

{
"opportunity_id": "Opportunity ID",
"stage": "Stage"
}
Datapills need to be wrapped in double quotes and parameter names must be in all lowercase. Parameters can be user-specified, like the urgency of an issue in ServiceNow, or recipe information, like the Message ID of a previous MS Teams message.

Learn more

results matching ""

    No results matching ""