> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flowx.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Message throw intermediate event
> A Message Throw Intermediate Event is an event in a process where a message is sent to trigger communication or action with another part of the process. It represents the act of throwing a message to initiate a specific task or notification.
**Why this matters:** The Message Throw Intermediate Event enables communication between different parts of a process or between separate processes entirely. It allows you to send data and trigger actions in other process instances, making it essential for coordinating complex workflows.
## Configuring a message throw intermediate event
A Message Throw Intermediate Event sends a message that can be correlated with a catch event—either a [Message Catch Intermediate Event](./message-catch-intermediate-event) in a running process or a [Message Start Event](../message-catch-start-event) to initiate a new process instance. The event creates a connection between the sending and receiving components, allowing information or instructions to be transmitted. Once the message is thrown, the process continues its flow.
### General config
Select the catch message event that this throw event should communicate with. The dropdown contains all catch messages from the process definitions accessible to the user.
Define the message for the catch event first. This ensures its availability in the dropdown menu when configuring the throw intermediate event.
A business or process variable that uniquely identifies the instance to which the message is sent. The engine extracts the value of this key at runtime and uses it to find a matching catch event listener.
Common correlation key examples:
* `processInstanceId` — to correlate within the same process
* `parentProcessInstanceId` — to communicate between a parent and subprocess, or between sibling subprocesses that share the same parent
* Custom business keys like `orderId`, `applicationId`, etc.
Define a JSON structure with the data to be sent along with the message. You can use dynamic values from the process data using the `${}` syntax.
Example:
```json theme={"system"}
{
"customerName": "${customer.name}",
"applicationStatus": "${application.status}",
"amount": ${application.amount}
}
```
Assign a stage to the node if needed. Stages help organize and track process progress.
***
The corresponding catch event must be in a **waiting state** before this throw event fires. If the throw executes before the catch node is reached, the message will not be delivered and correlation will fail. This is especially important when working with async subprocesses.
## Use cases
### Correlating with a running process instance
Use the Message Throw Intermediate Event to send data to a [Message Catch Intermediate Event](./message-catch-intermediate-event) that is waiting in another part of the same process or in a different running process instance.
Both the throw and catch events must have matching:
* **Message name** (selected in **Correlate with catch message events** / **Correlate with throwing message events**)
* **Correlation key value** at runtime
### Starting a new process instance
Use the Message Throw Intermediate Event to trigger a [Message Start Event](../message-catch-start-event) and start a new process instance. In this case, no correlation key is needed on the catch side since a new process instance is always created.
For detailed examples of interprocess communication using throw and catch events, see [Intermediate Message Events Examples](./example-intermediate-message-events).
***
## Related documentation
Learn how to configure catch events that receive messages from throw events.
Trigger new process instances using messages from throw events.
Complete examples showing throw and catch event configurations.