Triggers act as the entry point for event-driven automation. They define when an event is published within a project and enable applications to respond to external events, system activity, or incoming data.
Triggers operate independently of process definitions. They are configured at the project level and publish events that can be consumed by processes and other project assets. They are not placed directly on BPMN diagrams.
You can use triggers when you need to start processes based on external events, react to incoming data or notifications, integrate with systems that push events (webhooks), or automate workflows without user initiation
The workflow of a trigger is as follows:
- An event source is detected, such as an incoming webhook request.
- The trigger evaluates the configured criteria, such as conditions, headers, or parameters.
- If the criteria are met, the trigger publishes an event and payload is generated.
- The published event can initiate or influence automation behavior
Note: Triggers (Incoming Webhooks) cannot access or expose variables from
running process instances. They can start a process, but they cannot read process
variables or return them in a response body. In such case, try using the Hyland Content
REST API. You will find more information in its documentation.
To create a trigger, refer to Creating Triggers.