About Alert Tasks

This section describes the process to create a Kore Bot alert task. An alert task is a notification message that is sent to a Kore account Messages page on the Bots tab or a space when an event occurs for the specified Bot.

The Bot is a web site, web application, or system that you want to trigger a notification to send a message to a Kore account. For example, a Kore alert task using the Bot for Twitter can be used to initiate a notification every time you get a new follower on Twitter without having to open Twitter.

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

Kore provides many built-in Bots with predefined alert tasks. For more information, see Integrations for Kore Bots. You can also create a new custom Bot, and then define new alerts based on that Bot. 

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 Alerts

The full set of steps that you need to define an alert task in Bot Builder depends on the alert task Connection Type and the Bot, but there are seven basic steps to create an alert.

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

Note: When modifying an existing alert task, Review is Step 1 and subsequent steps renumbered accordingly.

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

Step 3:  Request Object for an Alert - The alert task request object gets data from your Bot for the notification message displayed to the end-user. The configuration settings for a request object are based on the Connection Type that you define for the alert request object. For more information, see:

Step 4:  Response Object for an Alert Task - After an alert task notification message is sent to Kore, you need to decide how to display the notification message to the end-user, and what parts of the message payload of the alert task from the Bot should be displayed.

Step 5:  Error Messages for Alert Tasks - Alert task notification messages are distributed over the Internet using standard HTTP. Any HTTP error messages are displayed to the end-user and you may want to disable, add, or customize these HTTP error messages for your alert task.

Step 6:  Settings for an Alert Task - For alert tasks, you must define the Trigger Interval options, and the Default Trigger Interval, which is the default interval between data requests for an alert task. Optionally, enable and define alert reminders.

Step 7:  Review for an Alert Task - Collects data from all steps and shows the current settings for the alert, such as Version, timestamps, Status, Request Chain, Filters, Trigger Interval, Flow Mapping, and Response Object.

Note: For new alert tasks, Review is Step 7. When modifying an existing alert task, Review is Step 1.

Next Steps

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

After you define your alert task and have tested the settings, you can also add an action task to your alert task to create a flow. A flow is an action task event triggered by your alert task event. For example, if you have an alert task that generates a notification message from Twitter each time you get a new follower, you could map an action task to your alert task to automatically follow the follower. For more information, see About Action Tasks.