About Action Tasks

This section describes the process to create a Bot action ask. An action task executes an event in the corresponding Bot system, website, or web application. In Bot Builder, you can create two types of tasks, an action task, or an alert task. For more information, see About Alert Tasks. This topic describes the process to create a new action task using the Kore Bot Builder tool.

A Bot is a web site, web application, or system that you want to trigger and send a notification message to a Kore account, or to initiate an action for that Bot. For example, a Kore task using the Bot for Twitter can be used to initiate a message every time you get a new follower on Twitter without having to open Twitter. When the message is displayed in the Kore account, the user could initiate an action task, to follow the new follower.

Before you can define an action task, you must first select or define a Bot for the corresponding task. For more information, see Creating a New Bot.

Kore provides many built-in Bots with predefined tasks. For more information, see Integrations for Kore Bots.

Note: Only users with paid individual accounts, and users that are members of a space or company currently enrolled in a Kore Premium plan can deploy Bots created in Bot Builder to other users.

Process for Defining Action Tasks

The steps that you need to complete to define an action task consists of six basic steps.

Step 1:  Basic Settings for an Action Task - The first step is to define how the task is displayed to the end-user, for example, the task name, descriptions for the task, screenshots, the content information provided by the task, and so forth.

Note: For new tasks, Review is Step 6. When modifying an existing task, Review is Step 1 and subsequent steps renumbered accordingly.

Step 2:  Authentication for an Action Task - If required for your task, you will define the authentication, for example, basic authorization, OAuth, or API Key.

Step 3:  Request Object for an Action Task - If required for your task, you can define a request object to, for example, provide a dynamic drop-down choice for the end-user to select from to complete the task.

Step 4:  Response Object for an Action Task - The action response object provides a message to the end-user to inform the end-user of the status or completion of the task.

Step 5: Error Messages for an Action Task - Tasks are events that take place over the Internet using standard HTTP. Any HTTP error messages related to the task are displayed to the end-user and you may want to disable, add, or customize these HTTP error messages for your task.

Step 6:  Review for an Action Task - Review settings for all steps in a single page before saving your task.

Note: For new tasks, Review is Step 6. When modifying an existing task, Review is Step 1 and subsequent steps renumbered accordingly.

Next Steps

To get started defining an task, you must first describe the task basic settings. For more information, see Basic Settings for an Action Task.

Comments

  • Avatar
    Help Docs

    This is a test comment.