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:
- Manually or through conversation via AI Colleagues.
- 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 Start Node |
| Error message display | Once the workflow execution fails, we can choose what kind of error we need to show to the user:
|
| 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. |
Updated 5 days ago