Event Publisher

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

The Event Publisher connector enables event-driven communication between pipelines, notifying other pipelines about a state change, an action, or an occurred fact so they can react to it, leveraging the platform's native event routing.

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

Parameters

The table below lists all configuration parameters for the connector. Parameters that support Double Braces expressions are marked with ✅ in the Supports DB column.

Section Event Publisher Connector

Parameter	Description	Type	Supports DB	Default
Alias	A name for this connector's output, so you can reference it later in the flow with Double Braces.	String	❌	event-publisher-1
Event	Name of the created event to be published for other pipelines to consume.	String	✅	{{ DEFAULT(message.eventName, "new-event") }}
Body	Payload to be sent with the event.	JSON	✅	{{ message.$ }}
Log Each Event Sent	If enabled, generates an input log for each sent event.	Boolean	❌	false
Fail On Error	If enabled, interrupts the pipeline execution when an error occurs. If disabled, execution continues, but the "success" property will be set to false.	Boolean	❌	false

Documentation

Parameter	Description	Type	Supports DB	Default
Documentation	Optional field to describe the connector 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:

1. Add the Event Publisher connector to the pipeline.

2. In the Event parameter, enter the name of the event to publish.

3. To send data with the event, define the payload in the Body parameter.

Then, configure the Subscriber pipeline:

1. Set the pipeline's trigger type to Event Trigger.

2. 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.

Note on redeploying Publisher and Subscriber pipelines

When redeploying a pipeline with Event Publisher, also redeploy the corresponding Subscriber pipeline (the one with the Event Trigger), starting with the Subscriber. If the two sides are temporarily misaligned, event delivery keeps working, but the timeout and redelivery (Allow Redelivery Of Messages) settings may not apply until both pipelines are redeployed. Learn more in How to interpret event publishing and delivery alerts.

Error scenarios

java.util.NoSuchElementException: Timeout waiting for idle object

This error means the connector can't keep up with the number of events sent at the same time. To solve this, you have two options:

• Increase the number of pipeline replicas: distributes the event load more efficiently and reduces pressure on the connector, so it can process events more smoothly.

• Implement error handling with Retry: retries sending the events that caused the error automatically, which helps with temporary load spikes or events that occasionally fail.

Messages flow

Input

The connector waits for a valid message in JSON format. No specific attribute is expected. You can reference the input message with Double Braces in both the Event and Body parameters. For example, say the following message is passed to Event Publisher:

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

You could define a Double Braces expression in the Event parameter to get the value of the eventName attribute:

{{ message.eventName }}

You could configure the Body attribute the same way:

{{ message.body }}

Output

The connector passes along the message received from the previous connector, without any change. In the example above, the output message is:

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

Next steps

Now that you know how Event Publisher works, read Event Trigger to configure the pipeline that consumes the published event.