When should I use a Message End Event?

Use Message End Events when process completion should notify external participants-sending completion callbacks, triggering follow-up processes, or responding to original requesters.

How is the Message End Event different from related elements?

Message End Events send to specific recipients (one-to-one) and terminate the path. Signal End Events broadcast (one-to-many). Message Intermediate Throw Events send without terminating.

eventsmessage triggerVariant of End Event

Message End Event

A Message End Event terminates a process path while sending a message to an external participant. It combines process completion with outbound communication in a single element.

What is a Message End Event?

A Message End Event ends a sequence flow path and sends a message to an external participant. It combines termination with outbound communication-useful when process completion should notify external systems or other processes.

Visual Representation

The event shows a thick-bordered circle containing a filled envelope icon. The thick border indicates End Event; the filled envelope indicates outgoing message.

Key Characteristics

End with communication: Terminates path and sends message
External recipient: Message goes to participant outside the process
Correlation information: Can include data for recipient to correlate
Common pattern: Frequently used to notify requesters of completion

See it in action

The ordering process ends by sending a message to the supplier

Read: Beauty Paradise →

Common mistake

Using a Message End Event when the process continues after sending. Message End Events terminate the path — use a Message Intermediate Throw Event or Send Task if the process continues.

How it connects

Message StartMessage End Events send messages that can trigger Message Start Events in other pools Send TaskSend Tasks also send messages but are activities; Message End Events combine sending with process termination Message ThrowMessage Throw Events send mid-process; Message End Events send as the final action EndPlain End Events just terminate; Message End Events send a notification on termination

Common Use Cases

Request Completion Response

End the request process by sending a "RequestCompleted" message back to the requesting system.

Inter-Process Trigger

Complete this process and trigger a follow-up process by sending it a start message.

Integration Callback

End synchronous portion and send async completion callback to the calling system.

Frequently Asked Questions

Model this in Crismo

Create BPMN diagrams with AI assistance. Free, no signup needed.

Open in Editor Browse All Elements