Triggers13 min read

Triggers are specific events that drive a specific process application based on conditions defined. There are different triggers that you can use to trigger a process flow based on the requirement.

Conversational Trigger

Conversational Trigger refer to the triggers that occur through a conversational bot. You must associate Kore.ai conversational bots and use them to trigger your process app. To let the conversational bot trigger the process app, the bot is provided with permissions to perform the trigger action.

To configure a Conversational Trigger, follow the below steps:

After you log in to the Process App, it lands you on the Flow tab.
On the right pane, click Conversational under Triggers.
On the Conversational Trigger window, by default, the Configure tab is selected.
On the Configure page, click + Variable to add process variables. Variables allow you to use data from bots across your process app flow. Adding a variable is optional. If you want to trigger the process during a conversation, you can add it.
Select a Data Type (String, Boolean, Number, Date) from the drop-down list.
Similarly, you can add multiple variables with different data types.
Click the Instructions tab to find the instructions to configure.
1. Define Payload – Add the payload that is expected from the bot that acts as a trigger to the process app.
2. To let the bot trigger the process app, the bot is provided with permissions to perform the trigger action. You can add permissions from Settings > Bot Permissions. You can also enable the bot permissions after the Process App configuration.
3. After you grant permissions, the developer must go to the bot builder dialog definition screen to add the process node and select the process app to trigger and perform the context mapping to pass the context data from the bot to the process app. You can also do this independently after creating and configuring the trigger.
4. Click Done.

Digital Form Trigger

A Digital Form helps you to collect the required data. It allows your users to enter the data you want to process a certain request. Digital Form triggers refer to the triggers that occur through the submission of a digital form. For example, let us consider an employee expense report. An employee has submitted an expense report of $1000. After the submission, the system fetches the user-related information through an API request and follows the approval process. In this scenario, the system uses the API request. The process flow of the Digital Form Trigger is explained below.

To configure a digital form, follow the below steps:

After you log in to the Process App, it lands you on the Flow tab.
On the right pane, click Digital Form under Triggers.
On the Digital Form Trigger window, select a form or Create New Form from the Forms drop-down list.
On the New Form dialog box, enter the following details:
- Name – Enter a name for the digital form. For example, Expense Report
- Display Name – Enter a display name to easily identify the name.
- Description – Enter a short description of the digital form
Click either Create & Design Form to create a form and redirect the user to the form builder page to design the form, or Create and Build Process Flow to allow the user to create a form and continue working on building the process app flow.
On the Digital Form Trigger window, click Add Access Control. It lands you on the Forms page and you can add a component in the master form. You can only update Read-only, Is-Visible, and Visibility settings through access control.
Under the HTML to embed form section, you can find the HTML code. Click Copy to copy the HTML code. You can use this HTML iframe code to embed the trigger form in your website. This is needed only if you do not use the portal and the process app is for public access.
For Form URL, click the copy icon to copy the URL (representing the trigger form along with the selected instance) displayed in the textbox.
Note: This URL is non-editable.
Click Done. You can find the trigger created on the Process Builder.
Start to build the flow by notifying the initiator (employee).
On the left pane, you can find the Events section. Drag and drop the Notify stencil from this section to the builder.
Click the Notify stencil to open the Notify window.
On the Notify window, enter the following details:
1. Name – Enter a name for the notification message.
2. Delivery Mode – Select the mode of communication to notify the employee.
3. Recipients – Enter the email address of the employee to receive a notification. You can also use context or variables from the trigger.
4. Subject – Enter the subject for the notification email.
5. Compose Message – Enter the relevant text related to the notification. It also supports context and the addition of variables so that you can include them while composing the message.
Close the Notify window.
Make an API request to fetch the Manager details of the initiator (employee).
On the left pane, you can find the Integrations section. Drag and drop the Connect to API stencil from this section to the builder.
Click the Connect to API stencil to open the Connect to API window.
On the Connect to API window, enter the following details:
1. Name – Enter the name of the API request.
2. Type – Select the API request type: REST or SOAP
3. Integration Mode – Select the integration mode: Synchronous or Asynchronous.
4. URL: Click Define Request under the URL field.
  1. On the Define Request page, enter the following details:
    1. Request Type – GET
    2. Request URL – https://608fd39c38473400170203a8.mockapi.io/api/v1/leaverequests (This is an example URL, not for business purposes)
    3. This API does not require any Header Parameters.
    4. Click the Test Request tab.
    5. Click Test on the top-right of the page. Wait for the test to be completed and you get a Status Code: 200.
    6. You can see an array of records returned by the API call. In the next step, values are parsed using JavaScript.
    7. Click Save on the top-right of the page.
Close the Connect to API window.
After the successful completion of the API request, the system fetches the Manager details and assigns the task (expense report approval).
On the left pane, you can find the Tasks section. Drag and drop the Human Task stencil from this section to the builder.
Click the Human Task stencil to open the Human Task window.
On the Human Task window, enter the following details:
1. Name – Enter a name for the human task.
2. Task Results – You can find Approve and Reject options. Choose to approve or reject the task. You can also rename these options or click Add an Outcome to add more options like On-Hold.
Click the Notifications tab to configure the notification settings.
Select a Delivery Mode from the drop-down list: Bot or API or Email.
Under the Response section, select a Get Response option to send the Manager’s response. These options differ based on the delivery mode selected. If the delivery mode is email, you can get responses through a form or email. If the delivery mode is bot, you can get responses through a form or conversational experience. If the delivery mode is API, you can get responses through APIs. In this example, the selected delivery mode is email.
1. Get Response through a Form – If selected, the Form URL will be inserted into the message composed in the Compose Message section.
2. Get Response through Email – If selected, Buttons for the result outcomes are appended to the message composed in the Compose Message section.
Under the Compose Message section, enter the following details:
1. Subject – Enter the subject for the response mail.
2. Compose Message – Enter the details of the response message.
3. Click {..} to add variables to the message. You can also use Context in the message.
Click the Assignment tab to configure the recipient settings. You can select any of the below options:
1. Single Recipient – If selected, you can send the response to the recipient configured in this section.
  1. Enter the recipient email address in the Recipient ID field.
2. Multiple Recipients – If selected, you can send the response to multiple recipients configured in this section.
  1. Enter recipient email addresses separated by a comma in the Recipient ID field.
  2. Under the Assignment Logic section, select an option:
    1. Assign to All – If selected, the system assigns the task to all recipients.
    2. Least Occupied – If selected, the system assigns the task to the recipient with the least number of open tasks.
3. Group – If selected, you can send the response to a group. Only one of the recipients from the group can complete the task
  1. Enter the group email addresses separated by a comma in the Group ID field.
Close the Human Task window.
After assigning the task, the Manager can approve or reject the task. To perform this action, you need a logic stencil. You do not always need logic to perform this task, it depends on the use case. But, in this example, a logic stencil is used.
On the left pane, you can find the Logic section. Drag and drop the Split stencil from this section to the builder.
The Split stencil is added to the builder with two branches (Branch1 and Branch2).
Click the Split stencil to open the Split window.
On the Split window, enter the following details:
1. Name – Enter a name for the split action. For example, Manager Decision.
2. Branches – Edit the branches (Branch1 and Branch2) as Approved and Rejected.
3. Split Logic – Select any of the below options:
  1. Execute all Branches – If selected, all branches are executed simultaneously.
  2. Execute on Condition – If selected, you can define a condition in the Define Condition section below. You can define conditions based on Process Fields, Context, and Process Context. For example, let us select Process Fields.
    1. Under the If condition, Select Field Value and Less than from the respective drop-down lists. In the Value field, enter $2000.
    2. From the Go to Branch drop-down list, select Approved.
    3. In the Add Else-If section, select Rejected from the Else Go To Branch drop-down list.
Close the Split window.
The next step is to notify the employee about the status of the expense report. Drag and drop the Notify stencil below the Approved and Rejected branches on the builder.
Open the Notify stencil of Approved and Rejected branches and configure the notification details.
The final step is to end the process flow.
On the left pane, you can find the Logic section. Drag and drop the End stencil from this section to the builder.
Click the End stencil to open the End window.
On the End window, select any of the below options:
1. End this Path – If selected, the system will end the current path and all other paths remain active.
2. Terminate all Paths – If selected, the system will terminate all active paths and end the process flow.

Webhook Trigger

Webhook Trigger allows you to trigger the Process App from a third-party application. This helps you to make the API call using client ID and client secret for authentication.

To configure a Webhook Trigger, follow the below steps:

After you log in to the Process App, it lands you on the Flow tab.
On the right pane, click Webhook under Triggers.
On the Webhook Trigger window, configure the following details:
1. App – Select an app from the drop-down list or create a new one. To create a new app, follow the below steps:
  1. From the drop-down list, select Create New.
  2. On the Create New App dialog box, enter the App Name and select the Authentication Algorithm (HS256/RS256) from the drop-down list.
  3. Click Confirm.
2. Variables – Click + Variable to add process variables. Variables allow you to use data from bots across your process app flow.
Click Done.

Callable Trigger

Callable Trigger refer to the triggers invoked from another process app. For example, let us consider Process App A which is already designed and Process App B that uses a callable trigger. In the above example, it is not defined which flow triggers Process App B. Instead, a call a subflow task is added in Process App A to trigger Process App B. After the callable task is added, the system automatically links these two flows and adds Process App A as a trigger to Process App B. On the Callable Triggers window, you can see the name of Process App A (as a trigger) and any other triggers/process applications that trigger Process App B.

To configure a Callable Trigger, follow the below steps:

After you log in to the Process App, it lands you on the Flow tab.
On the right pane, click Callable under Triggers.
On the Callable Trigger window, by default, the Variables tab is selected.
On the Variables page, click + Variable to add process variables. Variables are passed from parent process to child process app.
Select a Data Type (String, Boolean, Number, Date) from the drop-down list.
Click Save.
Similarly, you can add multiple variables with different data types.
Click the Process App tab.
You can find the Process Apps. Select a Process App to trigger this workflow.
Click Done.

Email Trigger

Email trigger refers to the trigger that occurs when an email is sent/received. This helps you to initiate a process app just by sending an email. For e.g. you can send an email requesting for a price of the product that you wish to buy, this can initiate a lead and create a task to the appropriate person/group.

To configure email trigger follow below steps

After you log in to the Process App, it lands you on the Flow tab.
On the right pane, click Email under Triggers.
On the Email Trigger window, configure the following details:
1. Email address to trigger – by default, the process app name would be considered as trigger email address, however, you can edit the email trigger name to your choice
  1. The domain of the email trigger will remain static and cannot be changed
2. You can add the email trigger with/without a condition
  1. If you want the process app to be triggered only if the email contains certain keywords you could do that.
    1. For e.g. Trigger only if subject contains “Enterprise”
    2. In this case whenever an email is received to the email address chosen above in step 4a, the process app will check if the subject line of the email has Enterprise, and if yes, the process app is triggered.
  2. You can add multiple conditions as per your business need

On this Page