Triggers/Workflow Initiation

What are workflow triggers/initiations?

The initiation step of a workflow is defined as a trigger. The current architecture allows workflow designers to configure initiation of a workflow in 2 ways:

  1. Manually or through conversation via Autonomous Agents
  2. Initiating it via API

The user can configure can configure how to initiate a workflow via API at the Workflow trigger level.

Configurations

Configurations

Description

Fail workflow initiation

This configuration controls the initiation behaviour of the workflow. If any nodes get failed under Synchronous Block between initiator input node and Manual trigger node

Error message display

Once the workflow execution fails, we can choose what kind of error we need to show to the user:

  1. A generic error message 2. An error message configured at action/function node level, which is pushed only if the node fails

Allow execution via web-hook/ Enable API-triggered workflow initiation

If this flag/configuration is enabled, then a workflow can also be initiated via an API call, rather than just through a conversation or through the input form

Trigger actions when request is withdrawn

When enabled, a separate flow can be designed, which is executed every-time an 'In Progress' request is withdrawn.

Limit execution of workflows within a defined time-period

This configuration limits triggering of workflow beyond the set frequency for the set time-period. If workflow is initiated beyond the set configuration, for a particular user (either manually or through REST API), its execution is restricted and error is returned.