Skip to main content
Version: 8.7

Message Send connector

The Message Send connector can publish or correlate BPMN messages.
It either calls the PublishMessage RPC of the Zeebe API to send messages buffered by Zeebe, or the Correlate a message REST API to get the ID of the process instance that received the message without buffering.

The element template allows you to select the mode:

  • publish message (with buffer)
  • correlate message (with result)

and fill all parameters directly in the modeler.

note

This connector is available since Camunda 8.7.2

Publish message (buffered) parameters

ParameterTypeDescriptionDefault / Optional
Message namestringName of the message. Must match a receiving message event.Required
Correlation keystringValue for correlating with a process instance. Can be empty to start a new instance.Optional
PayloadJSONVariables to transfer to the receiving process instance. Example: {"customerName": cust_name}. Multiple variables can be defined.Required
Time to liveintTime in milliseconds to buffer the message.No buffer
Message IDstringUnique message ID for idempotency. Ensures the message is delivered only once until correlated.Optional
Tenant IDstringTenant ID of the receiving instance.<default>
Request timeoutintTimeout for the publish message command.Connector default

Response

FieldTypeDescription
messageKeyint64Unique ID of the published message
tenantIdstringTenant ID of the message

Correlate message (with result) parameters

ParameterTypeDescriptionDefault / Optional
Message namestringName of the message. Must match a receiving message event.Required
Correlation keystringValue for correlating with a process instance. Can be empty to start a new instance.Optional
PayloadJSONVariables to transfer to the receiving process instance. Example: {"customerName": cust_name}. Multiple variables can be defined.Required
Tenant IDstringTenant ID of the receiving instance.<default>
Request timeoutintTimeout for the correlate message command.Connector default

Response

FieldTypeDescription
messageKeyint64Unique ID of the correlated message
processInstanceKeyint64Key of the first process instance the message correlated with
tenantIdstringTenant ID of the message

The connector raises an incident with a detailed error message containing the 404 status Not found if the message could not be correlated.