Event Trigger
Discover more about the Event Trigger and how to use it on the Digibee Integration Platform.
The Event Trigger enables event-driven communication between pipelines, starting a pipeline's execution automatically in response to a specific event published by another pipeline through the Event Publisher connector.
Learn more about how to use event-driven architecture on the Digibee Integration Platform.
Parameters
Configure the trigger using the parameters below.
Event Name
The name of the event the trigger responds to.
String
event-trigger
Expiration
The time, in milliseconds, that the event remains in the queue. If the value is 0 or greater than 6 hours, the expiration is set to 1/4 of the value configured in Maximum Timeout.
Integer
600000
Maximum Timeout
The maximum time, in milliseconds, that the pipeline can take to process the event before returning a response. Maximum limit: 900000.
Integer
30000
Allow Redelivery of Messages
When enabled, allows messages to be redelivered if a failure occurs in the Pipeline Engine.
Boolean
false
Documentation
Optional field to describe the trigger configuration and any relevant business rules.
String
N/A
How does event-based messaging between pipelines work?
An event-driven setup always has two sides: a pipeline that publishes the event and one or more pipelines that consume it.
First, configure the Publisher pipeline:
Add the Event Publisher connector to the pipeline.
In the Event parameter, enter the name of the event to publish.
To send data with the event, define the payload in the Body parameter.
Then, configure the Subscriber pipeline:
Set the pipeline's trigger type to Event Trigger.
In the trigger configuration, enter the event name in the Event Name property. This value must match the one set in the Event parameter of the Publisher pipeline.
With both pipelines configured, every time the Publisher pipeline runs and publishes the event, the Subscriber pipeline is triggered and starts running automatically.
Messages flow
Input
The trigger expects a valid message in JSON format. The received message corresponds exactly to the content defined in the body attribute of the Event Publisher connector.
Output
The connector forwards the message received from the previous connector without making any changes. Based on the example above, the connector forwards:
Limitations
Event routing limits
To protect the messaging infrastructure and prevent infinite loops or excessively long chains that could degrade system performance, the Event Trigger enforces an event routing limit.
When an event triggers a chain of other events (for example, a pipeline triggered by an Event Trigger publishes a new event that triggers the same Event Trigger again), the system tracks the number of chained events.
If this count reaches the default limit of 25 events, the system interrupts processing of the current event.
Last updated
Was this helpful?