Event Trigger

Discover more about the Event Trigger and how to use it on the Digibee Integration Platform.

An event is a message that notifies other connectors about a state change, an action, or an occurrence. The Event Trigger responds to a specific event generated by another pipeline through the Event Publisher.

Learn more about How to use event-driven architecture on the Digibee Integration Platform.

Parameters

Configure the trigger using the parameters below.

Parameter	Description	Default value	Data type
Event Name	Name of the event the trigger responds to.	event-trigger	String
Expiration	Time the event remains in the queue, in milliseconds. If the value is equal to 0 or greater than 6h, the expiration will be set to 1/4 of the value configured in Maximum Timeout.	600000	Integer
Maximum Timeout	Maximum time, in milliseconds, that the pipeline can take to process the information before returning a response. Default value: 30000. Maximum limit: 900000.	30000	Integer
Allow Redelivery of Messages	When enabled, allows messages to be redelivered if a failure occurs in the Pipeline Engine.	False	Boolean

Message 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 component.

{
  "id": "1",
  "description": "Description of the case"
}

Output

The connector forwards the message received from the previous connector without making any changes. Based on the example above, the forwarded message will be:

{
  "id": "1",
  "description": "Description of the case"
}

Event Trigger in action

To implement an event-driven architecture, you must define:

• The pipeline responsible for publishing the event, acting as the publisher.

• One or more pipelines responsible for consuming the event, acting as subscribers.

To configure the pipeline that will publish the event:

• Add the Event Publisher to the publisher pipeline.

• Configure the event name in the Event property of the Event Publisher.

• If you want to send a payload along with the event, define the content of the Body property.

To configure the pipeline that will consume the event:

• Change the trigger type to Event in the subscriber pipeline.

• Open the trigger settings and enter the event name in the Event Name property. This value must be exactly the same as the one configured in the Event Publisher of the publisher pipeline.

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 25 events, which is the default limit, processing of the current event is interrupted.