Generic Triggers
You can configure generic triggers to respond to events that are configured to submit data to the Concord REST API.
Currently, Concord supports two different implementations of generic triggers:
version: 1 and version: 2.
Note: Generic triggers are more impactful to server performance than starting processes directly through the Process API. Consult with your system administrator before implementing generic triggers.
Version 2
For example, if you submit a JSON document to the API at /api/v1/events/example,
an example event is triggered. You can capture this event and trigger a flow by
creating a trigger configuration using the same example name:
triggers:
- example:
version: 2
entryPoint: exampleFLow
conditions:
aField: "aValue"
Every incoming example event with a JSON field aField containing aValue kicks
of a process of the exampleFlow.
The generic event end-point provides a simple way of integrating third-party systems with Concord. Simply modify or extend the external system to send events to the Concord API and define the flow in Concord to proceed with the next steps.
Note: standard limitations apply.
Version 1
- example:
version: 1 # optional, depends on the environment's defaults
aField: "aValue"
entryPoint: exampleFLow
Check out the full example for more details.
Note: standard limitations apply.
Migrating Generic trigger from v1 to v2
In version: 2, the trigger conditions are moved into a conditions field:
# v1
- example:
aField: "aValue"
entryPoint: exampleFLow
# v2
- example:
version: 2
conditions:
aField: "aValue"
entryPoint: exampleFLow
