You can create automations with event-listening web triggers. Web triggers enable citizen or professional developers to run automations based on real-time event changes that occur in various SaaS applications.

You can create both user-based web triggers and role-based web triggers. Supported SaaS applications are:

  • GitHub
    Note: OAuth connection is not required for GitHub web triggers.
  • Google Calendar
  • Jira
    Note: Jira Web triggers supports only one subscription account.
  • Microsoft 365 Outlook
  • ServiceNow
    Note: ServiceNow web trigger does not require offline access authorization or token scope for OAuth connection.

If you modify a specific role or add new users to the role, the Web triggers run the automation based on the role parameters that were configured when the web trigger was created.

Note: API Tasks supports web triggers listed in the Triggers section.

All the automations with web triggers are listed under Manage > Event triggers.

The Web Triggers column in the Event triggers table displays the number of web triggers that are configured in a bot. Click the number to view the Trigger details. The Trigger details modal displays active triggers, inactive triggers, subscribed events, and any errors in the web triggers. Errors such as subscription failures, authentication issues, and expired triggers are displayed in the errors section.

The following is a high-level overview on how to get started with web triggers.

  1. Create OAuth connections for the SaaS applications. See Create OAuth connection for more information about OAuth connection.
    Note: If the OAuth connection to the SaaS applications fails, check the Error column on the Event Triggers page for more information.
  2. Create or edit an automation. For more information, see Task Bots.
  3. Configure the required Web triggers in the Triggers section in the Bot editor.
  4. Add an appropriate event trigger to the automation. For more information, see Adding event triggers.
  5. Add and configure appropriate actions from the Actions section. For more information, see Actions to build automations
  6. Save and run the automation using Run with triggers option in the Bot editor.