Skip to main content
Version: 4.12.1

Outbound Flow Link Component

The Outbound Flow Link component can be used together with the Inbound Flow Link component to connect flows with each other. This enables you to split up bigger integrations in several reusable flows.

This component can be used multiple times in a flow to sent messages to other flows that have an Inbound Flow Link component.


This component has the following configuration options:

Target flow


When opening the properties modal all available target flows will be fetched. These are flows that start with an Inbound Flow Link component that has the same Transport. When they are fetched you can select the flow that you want to connect with.


  • The first flow in the list will be automatically set as the target flow.
  • When the original target flow can't be targeted anymore then the target flow will be reset to the first flow of the list or become empty when there are no target flows. A warning message will show up below the input when this happens.



  • Default
  • Synchronous
  • Asynchronous
  • Queues


The transport mechanism used between flow steps (components). Default is the best setting in most cases.

DefaultYesUses queues between flowsMost cases
SynchronousNoWhen you configure your flow to be synchronous, the output of the next flow will be used as a response to the first flow.For synchronous (request/response) interactions. Especially to keep the message order. Note the calling flow must be running.
AsynchronousYesWhen you configure your flow to be asynchronous, messages are stored an in-memory blocking queue between flows.For asynchronous (fire-and-forget) interactions. Especially to increase performance. Note the calling flow must be running.
QueuesYesSame as default. All messages will pass through a queuing mechanism. This means that the messages are stored on a broker outside of the flow until the next flow has received and acknowledged it.For synchronous (request/response) or asynchronous (fire-and-forget) interactions with large messages and guaranteed delivery.


Exchange pattern


  • One way (default)
  • Request reply


This option determines how the messages are sent to the connected flow. One way means that for every messages that is sent there will be no response from the connected flow. It can be compared with the term "fire and forget". This option is recommended when you don't need the response from the connected flow in your current flow, for example when you sent messages to your own logging solution.

Request reply is the opposite of the One way option. For every message that is sent to the connected flow there will be a response message from the connected flow. This option is recommended when you need the processed message in your current flow.


  • For Request reply the timeout option of the flow may need to be increased when the connected flow takes some time to process the messages.
  • The response to the caller will be the existing Exchange body before reaching the first One way component in the flow.


  • To see the full origin/target flow chain in the tracing, all connected flows should have tracing enabled.