The Workbot command is created by piecing 3 elements together, the app, action, and action data: If no, command will show up as a button in the Slack channel when the user types app name. If yes, command will not show up as a button in the Slack channel when the user types app name. Shows up in the Workbot app page under Commands. Short description of what the command does. You can use this file in subsequent operations using the Workbot action Download Attachment. Parameters may have the type file, which accepts file content (for example, text, binary content) as input. The input to ask from the user so as to successfully carry out recipe actions, defined in a specific format. The record that the Workbot command works with, for example, What the Workbot command is doing with the action data, for example,ģrd part of the Workbot command. The app that the Workbot command is working with for example,Ģnd part of the Workbot command. New command trigger input fieldġst part of the Workbot command. The following table lists the configurable input fields in the trigger, and what each field does.

When it's called, Workbot proceeds to carry out the recipe actions. When a recipe with this trigger starts, Workbot monitors for the new command. This trigger involves configuring a custom Workbot command. # New command trigger (building custom commands)

The Workbot for Slack connector has 5 triggers: With Workbot, you can create custom workflows that execute via your Slack commands, and optionally retrieve relevant data for you back to Slack. The recipe trigger picks up the Workbot command as a trigger event, and the recipe determines the actions to carry out. Workbot will handle these commands and interact with your connected apps to do things, such as display details of a customer account, close opportunities, display a list of invoices or tickets, or create/update existing tickets.Įach Workbot command is processed using a Workato recipe. Workbot for Slack allows you to send commands to Workbot on Slack.

Slack gif command