Alert tasks deliver timely, relevant, and personalized information from enterprise systems to customers and employees by polling the relevant service in real-time or according to a user-defined schedule. These alerts contain detailed information, such as name, ID, notes, amount, and more, in a variety of formats for each channel.
Users can schedule alerts to trigger according to the days, times, and frequencies they specify.
Users can configure alerts to trigger when certain thresholds are met such as amounts, dates, text matches, and more.
Example Use Cases
The following are a few sample use cases for Alert tasks:
- Time or location-based promotional offers
- Scheduled delivery updates
- Inventory level changes
- Critical issue notification
- Pandemic or weather-related awareness
- Cross-company status changes
Configuring Alert Tasks
To configure an Alert task, you need to complete the following settings:
The first step is to define how the task looks to the end-user. The General tab Settings includes details such as task name, connection mode, descriptions, and a few advanced settings such as task demo, search keywords etc.
Configure authentication settings to access third-party web services, with support for Basic Auth, OAuth v2 password grant type, OAuth v1, OAuth v2, and API Key authorization types. You can define an Authorization profile or use an existing one. All authorization profiles, whether you create them at a task level or a bot level, can be used across all bot tasks.
Configure the API request that asks for data from your Bot website, system, or web application for the task. You can configure the API Request Settings an action task for Rest or SOAP APIs. You can define API Parameters, optional API task Initializer, API Request pre- or post-processor, and the API Request. You also need to add a Response Sample expected from your API Request payload.
The Bot response provides a message to the end-user to inform them of the status or completion of the task. On the Bot Response tab for a task, you can define the message to display to the end-user from the API request payload. You can specify a default response for all channels and also compose channel-specific messages. Optionally, you can also include a URL to a report template along with the message to the user.
Define the schedule or filter settings for the alert. schedule alerts to trigger according to the days, times, and frequencies they specify, whereas filtered alerts rigger when certain thresholds are met such as amounts, dates, text matches, and more.
Supported Field Types for Alert Filters:
- Textbox: Displays a text box for the end-user to enter text as the task input field, typically just a few words.
- Textarea: Dropdown list dynamically populated at runtime based on the response from a URL
- Static Dropdown: Displays a drop-down list of choices to the end-user.
- Dynamic Dropdown: Drop-down list dynamically populated at runtime based on the response from a URL
- Check Box: List of choices that the end-user can select one or more of.
- Typeahead: Dynamically populated drop-down list of choices for the end-user at runtime, when the user enters three or more characters that match the search results based on the response from the URL defined for the task (for example, a list of projects for a JIRA task notification message).
- Dynamic Checkbox: List of choices for end-users to select one or more which are dynamically populated at runtime, based on the response from a URL (for example, a list of projects for a JIRA task notification).