Web triggers

Event-driven Web triggers are a powerful mechanism that enables your applications to react instantly to specific events within other web services or applications. By automatically initiating automations based on these real-time events, you can streamline workflows, improve efficiency, and ensure your systems stay synchronized with the latest data.

Overview

Automation Anywhere Control Room provides event-driven Web triggers that enable how applications and services interact in real-time. Web triggers are configured within the Control Room to subscribe to specific events occurring in other SaaS applications such as GitHub, Google Calendar, Jira, Microsoft Outlook 365, or ServiceNow. For example, a trigger can be set up to monitor for incident record additions in ServiceNow. Whenever a new record is created, a notification is immediately sent, initiating an automated workflow within the Control Room.

Important: This feature is available on Cloud only, and requires the Enterprise Platform license. For more information about supported version for this feature, see Enterprise Platform.

Event-driven Web triggers offer a reliable, efficient, and scalable real-time data exchange, empowering users to effortlessly connect and synchronize applications. This innovative technology opens new possibilities for businesses to streamline operations, enhance decision-making, and drive growth.

Key benefits of Web triggers
  • Real-time responses: Immediate actions based on events, eliminating delays.
  • Enhanced efficiency: Real-time triggers eliminate the need for manual intervention or scheduled polling, saving time and resources.
  • Enhanced decision making: Ability to anticipate and respond to events before issues escalate.
  • Improved data accuracy: Data is transferred in real time, reducing the risk of inconsistencies or outdated information.
  • Increased automation: Real-time triggers can be used to automate a wide range of tasks, from data entry to complex automations.
Use cases for Web triggers
  • Incident management: Automatically trigger incident response workflows based on alerts from monitoring tools.
  • Customer support: Initiate support cases based on customer inquiries or feedback.
  • Fraud detection: Trigger investigations based on suspicious financial transactions.

These are just a few examples, and the possibilities are vast. By understanding your specific business needs and processes, you can identify numerous opportunities to leverage Web triggers for automation and efficiency gains.

Architecture diagram of Web triggers with various SaaS applications

Note:

The Microsoft Outlook logo, the GitHub logo, the Jira logo, the ServiceNow mark, and the Google Calendar logo are trademarks or registered trademarks of Microsoft Corp., GitHub Inc., Atlassian Corp., ServiceNow, Inc., and Google LLC respectively, and are used for identification purposes only.

Known limitations

This section lists the limitations of Web triggers.
Jira web trigger
The Jira web triggers supports only one subscription account.
ServiceNow web trigger
The ServiceNow web trigger does not require offline access authorisation or token scope for OAuth connection.
Role based trigger limitation
If you modify a specific role or add new users to the role, the web trigger functions according to the role parameters that were existing when the web trigger was created.
Deploying web triggers
It is not required to enable the Automatically deploy to unattended Bot Runners check box when adding an event trigger to Web triggers.

Workflow

The workflow for setting up the Web triggers is as follows:
  1. Create OAuth connections
  2. Create automations with event-listening Web triggers
  3. Adding event triggers