An event is a supported business change that occurred. A trigger is the rule that evaluates that event and determines how it relates to a workflow.
TRIGGERS & EVENTS
Connect events to the next step.
Use supported events and defined conditions to start a workflow or evaluate what can happen next. Keep the result of each trigger execution in view.
- Supported event
- Rule and conditions
- Workflow-related processing
ONE EVENT, DIFFERENT OUTCOMES
An event is a starting point, not a guaranteed action.
This educational example uses a status change for an internal form associated with an existing workflow. The same event can lead to a different recorded result as its rule and workflow requirements are evaluated.
- What was verified?The rule condition did not match.What was the result?
This rule is skipped, so it does not produce a transition.
- What was verified?The rule condition matched, but no transition was eligible.What was the result?
The existing workflow is evaluated without applying a transition.
- What was verified?The conditions and requirements permit a transition.What was the result?
The eligible transition is applied and the processing result is recorded.
A CONTROLLED RESPONSE
Define what starts the response and what follows
Separate the business change from the rule that interprets it and the record that explains what happened next.
AnEventis a supported business change. ATriggeris the rule that evaluates that event and determines what the workflow can do next.
- Source
- The supported event and its business context determine which rules can be considered.
- Rule
- Matching conditions define how the event relates to the workflow, such as evaluating an existing workflow or starting one according to its configuration.
- Result
- The processing record explains what happened or what may need separate follow-up.
TRIGGERS & EVENTS FAQ
Questions about events, rules, and results
Short answers about how a supported business event is evaluated and how its processing result stays visible.
No. A rule can be skipped when its conditions do not match, and a matched rule can still find no eligible transition.
It can start a workflow or evaluate an existing one according to the rule, its handling configuration, and its conditions.
The trigger execution record can show whether processing was skipped, evaluated, applied, denied, or failed, together with its related context.
Trigger rules evaluate defined conditions rather than AI inferences. Any AI-assisted capability has its own scope, permissions, and controls.
A DEFINED RESPONSE
Give business events a defined response.
Connect supported changes to clear conditions and keep each processing result in view.
Start for free