Event-Driven Triggers
Rather than requiring manual initiation from the dashboard or bespoke backend orchestration code, the Triggers module in the dashboard allows you to automatically launch workflows whenever specific events occur in your business platform.
How Triggers Work
A Trigger links an incoming Event Key to a Target Workflow using two key configurations:
- Conditions Engine: Evaluates whether the incoming event payload meets your criteria (e.g., transaction amount, user country, risk tier).
- Payload Mappings: Extracts specific fields from the incoming JSON event and injects them as input parameters into the initial nodes of your workflow.
Supported Condition Operators
The trigger rule engine evaluates payload fields against predefined values using the following operators:
| Operator | Symbol / Value | Description |
|---|---|---|
| Equals | eq | Matches if the payload field is strictly equal to the target value. |
| Does Not Equal | neq | Matches if the payload field does not match the target value. |
| Greater Than | gt | Numeric comparison: field value greater than target (value > target). |
| Greater Than or Equal | gte | Numeric comparison: field value greater than or equal to target (value >= target). |
| Less Than | lt | Numeric comparison: field value less than target (value < target). |
| Less Than or Equal | lte | Numeric comparison: field value less than or equal to target (value <= target). |
| Is In | in | Matches if the payload field value is present within a provided array. |
| Contains | contains | Substring match for string fields. |
| Exists | exists | Verifies whether the field key exists in the incoming payload. |
Condition Evaluation Modes
When defining multiple conditions on a trigger, you can choose between:
- All (AND): Every single condition rule must evaluate to true for the workflow to be triggered.
- Any (OR): If any single condition rule evaluates to true, the workflow is launched immediately.
Defining Payload Mappings
Incoming events often use field names that differ from what your workflow nodes expect. The Mappings configuration bridges this gap by mapping JSON paths in your event payload to input parameters of the target workflow.
Example Trigger Configuration
Here is an example of an autonomous trigger configured for high-value user onboarding:
{
"name": "High-Value Transaction KYC Trigger",
"event_key": "user.transaction_limit_requested",
"source_key": "core_banking_engine",
"target_workflow": "wf_7f8a9b2c3d",
"conditionMode": "all",
"conditions": [
{
"field": "payload.requested_tier",
"operator": "eq",
"value": "tier_3"
},
{
"field": "payload.country",
"operator": "in",
"value": ["NG", "GH", "KE"]
}
],
"mappings": [
{ "target": "customer_id", "source": "subject.id" },
{ "target": "bvn", "source": "payload.customer.bvn" },
{ "target": "email", "source": "payload.customer.email" },
{ "target": "tier", "source": "payload.requested_tier" }
]
}You can simulate and test triggers directly from the dashboard using the Test Event Ingestion tool before enabling them in production.