Event triggers - Use the Event triggers page to add and run the trigger-based automations and to create listener URLs for Incoming webhook trigger.

Automation 360

Use the Event triggers page to add and run the trigger-based automations and to create listener URLs for Incoming webhook trigger.

About event triggers

Automations with event triggers are listed under Manage > Public tab. As a Control Room administrator you can view, add, or delete triggers set for the tasks in the Event triggers tab.

Citizen Developers can view and manage the triggers that they configured in the automation from both Public and Private tabs in the Event triggers page.

Over time, you might create several triggers that run various automated tasks. For example, a single task might be run using five different triggers or a single trigger might run five different tasks. As the number of tasks and triggers grows, you can use the Event triggers tab to organize and manage these triggers.

For On-Premises installation, when multiple triggers are configured for a single automation and one of the trigger encounters an error, none of the other corresponding triggers are impacted for Bot Runners. The trigger error events are not displayed in notifications for On-Premises but are displayed for Cloud deployments only.

Supported actions

In Automation 360, click Manage > Event triggers to view the table that lists all the available bots with event triggers. The following actions are available for this table.

  • Select Automation folder path in the search criteria drop-down and enter a keyword in the Search field to find an event trigger.

    For example, if the automation path of an event trigger is Bots\file--created--event--Salesinfo, enter Sales in the Search field to find this event trigger.

  • Use the Run with event triggers option to add event triggers. See Adding event triggers.
  • You can also delete any associated (active or inactive) event triggers from the vertical ellipsis menu.

The Event triggers page displays the following information:

Column Description
Trigger status Displays the overall subscription status of the triggers in the bot. Depending on the configuration of the automation, one of the following status is displayed:
  • Enabled: Displayed if subscriptions are created for all the triggers.
  • Disabled: Displayed if subscriptions are not created for any triggers.
  • Partially enabled: Displayed if subscription is created for at least one trigger.
Bot name Displays the name of the automation. Clicking the name directs the user to the automation in the Bot Editor page in read only mode.
Web triggers Displays the number of web triggers that are available in a bot. The Trigger details modal is displayed when you click the number. The modal contains the following information:
  • Active triggers
  • Inactive triggers
  • Subscribed events
  • Errors
Note: The web triggers count is displayed as -- for the bots that are created from previous releases.
Bot folder path Displays the folder in Public workspace where the automation is checked in.
Bot label Displays the production label of the automation.
User Displays the user associated with the automation when the automation is added using Add event triggers option.
Role Displays the role associated with the automation when the automation is added using Add event triggers option.
Automatic deployment status Displays if automatic deployment is turned on or off.
Modification details
  • Last modified: Displays the last modified time.
  • Modified by: Display the user that made the final modification.
On the device where the Bot Agent is installed, to view trigger details:
  1. Open the Task Manager > Details tab.
  2. Right-click on the column in the list of app entries.
  3. Click Select columns.
  4. Select Command Line item to turn on the column.
To confirm that the triggers are active, verify that the following Java processes are running:
  • Bot Agent or node manager (name is NodeManager.exe)
  • Trigger listener (name is TriggerListener.exe)
Note: When you install or update the Bot Agent, you must add the NodeManager.exe and TriggerListener.exe files to the safe recipients or trusted (allowed) list. You use a trusted list to designate specific files that are pre-approved for access by the Bot Agent.

Consider a scenario where triggers are associated with a Bot Runner user who logs off or signs out of a device. This Bot Runner user must log in to the Control Room on that device to activate the associated triggers.