So what is a Kore Bot? Kore users can use a Kore Bot to integrate with business systems or social applications, such as CRM applications, news services, and project management services. In Kore, each business system or social application is referred to as a Bot.
For each Bot, Kore provides built-in alert tasks, which are messages sent to the Kore user account when a specified event occurs in the source system, for example, a new lead or a purchase order in your source system occurs. Based on that alert task, a Kore user can initiate one or more action tasks, such as send an email, or create a new account in Salesforce.
Tasks can be configured individually for one or more Kore users. Some alert tasks have preconfigured action tasks mapped to that alert task. When an action task is mapped to an alert task, it becomes a flow.
Kore offers many Bots that you can use to create tasks. For more information, see Built-in Kore Bots.
Process for Creating a Bot
If you need a task for a Bot not currently provided by Kore, you can create a custom Bot, and then define custom tasks based on that Bot. After you define your tasks, you can then map your action tasks to your alert tasks as flows.
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.
To create a Bot
- In Bot Builder, select an existing Bot or create a new Bot. For more information, see Creating a New Bot.
- Define one or more tasks for the Bot. For more information, see About Alert Tasks and About Action Tasks.
- Map one or more action tasks to an alert task to create a flow. For more information, see Mapping an Action Task to an Alert Task.
- Publish your Bot to your account, a Kore space, or your company account. For more information, see Publishing Alert Tasks and Action Tasks.
After you define a Bot, an alert task, or an action task, you can select the Bot in Bot Builder in the left navigation pane in the YOUR BOTS section shown in the following illustration.
When you select a Bot in Bot Builder, your tasks are displayed in a table with the Description, Status, and Version, and Settings icon.
The Status for tasks can be one of:
- inProgress - The task configuration was started, but not yet complete.
- upgradeInProgress - A copy of a published task used to edit, and when configured, deploy to end-users as an upgrade for the original task.
- configured - The task configuration is complete, but not yet published for use.
- awatingApproval - The task is published for enterprise use, but has not yet been approved by the Enterprise Admin.
- published - The task is published for personal, enterprise, or public use.
The Version for a task displays the published version number. The first version is 1, and subsequent minor upgrades are represented as decimals, for example, 1.1, 1.2, and so forth. Major upgrades are represented as whole numbers, for example 1, 1.1, 2, 3, 4.1.
When you select the Settings icon for a task or flow, you can:
- View - Displays read-only task or flow settings.
- Edit - Displays the task or flow for modification.
- Edit Basic Settings (Only Published tasks) - Click to open the Basic Settings page for the task. Settings on this page can be made to the task without having to upgrade the task.
- Clone - (Only for tasks with Status set to Published) - Create a copy of the task with a new name using the syntax CopyOf - CurrentName(Clone#). For example, for an alert task named Test, the cloned name is CopyOf - Test(57) where 57 represents a unique hexadecimal value for the clone created.
- Upgrade - Creates a copy of a published task used to edit, and when configured, can be deployed to end-users as an upgrade for the original task.
- Publish (Only tasks in Status Configured) - Publish to make the Bot available to your company marketplace or space.
- History - Displays the Version History page for a published task.
- Map Alert Tasks, Map Action Tasks (Only for tasks with Status set to Published) - After a task is published, you can optionally map one or more action tasks to an alert task. For example, when a JIRA alert indicates a new issue, you can map an action task that allows the user to assign the JIRA issue to another JIRA user. You can also map an alert task in one Bot, to an action task in another Bot. For example, a JIRA alert task can be mapped with an Asana action task. When you map an alert task with an action task, it becomes a flow.
- Add Command, Manage Command (Only for published webservice action tasks) - Displays the Add Bot Command or Modify Bot Command dialog for action tasks.
- Delete (Only flows, and unpublished tasks) - Click to permanently delete a task or flow. Published tasks cannot be deleted.
What Can I do Here?
In short, you can do everything from creating and editing a Bot, creating and editing tasks, and mapping your Bot alert tasks with action tasks to create a flow. The following illustration describes the Bot Builder landing page.