Web triggers in process automation enable you to create event-driven processes that start immediately when the configured event occurs in the external application. This feature allows you to automate processes without manual intervention, streamline workflows, improve efficiency, and synchronize the processes with the latest data.

Overview

Event-driven web triggers listen for specific events in the external application. When the event occurs, the web trigger starts the downstream process artifacts. These web triggers provide a reliable, efficient, and scalable real-time data exchange, enabling users to connect and synchronize applications. You can configure multiple web triggers in a process for scenarios where the same event in different applications can be the driver for the automation. For more information about web triggers, see Web triggers.

Note: Web triggers cannot be used when a form is set as input in start element in a process.

Workflow

The high-level workflow of creating process automation with web triggers in the Control Room is as follows:

  1. Go to Automation > Create > Process to create a process.
  2. Add the appropriate web triggers from the Triggers panel to the process canvas.
  3. Configure the web trigger to listen for specific events. You can select one or more events to listen for.
  4. Configure the start element.
  5. Add and configure the appropriate tasks, conditions, and events.
  6. Save the process.
  7. Go to Manage > Event triggers on the Control Room home page.
  8. Click Run with triggers and choose the process you created.
  9. Assign an appropriate role or team for the process.
  10. Click Add event triggers. The process is added to the Event triggers page and the trigger is enabled. Once enabled, the trigger starts listening for the events based on the configuration.
  11. When the event occurs in the external application, the trigger starts the downstream process artifacts and completes the process automation cycle.

Trigger response data

When the configured event occurs in the external application, the application sends the trigger response payload to the Control Room. Every trigger has the Response option in the settings panel that allows you to save the response data in a record variable. The response data is available in a key-value pair format and is visible in the Audit log page as Process run by trigger event.

Supported web triggers

The Mozart Orchestrator supports all the web triggers that are available in Automation 360.

Web trigger Description
GitHub Triggers to automate workflows based on GitHub organization and repository webhook events.

GitHub web triggers

Google Calendar Trigger to automate workflows based on calendar events in Google Calendar.

Google Calendar web triggers

Jira Trigger to automate workflows based on Jira issue events.

Jira web triggers

Microsoft 365 Outlook Trigger to automate workflows based on email events in Microsoft 365 Outlook.

Microsoft 365 Outlook web triggers

Microsoft Teams Trigger to automate workflows based on Microsoft Teams chat and team management events.

Microsoft Teams web triggers

ServiceNow Trigger to automate workflows based on ServiceNow record events.

ServiceNow web triggers

SharePoint Trigger to automate workflows based on SharePoint site events.

SharePoint web triggers

Universal web trigger Trigger to automate workflows in any application that supports webhooks and pollers.

Universal web trigger