# Dynamically call different WorkspaceReceive connectors

**URL:** <https://community.cdata.com/t/dynamically-call-different-workspacereceive-connectors/612>\
**Category:** CData Arc\
**Tags:** question\
**Created:** [January 26, 2024, 5:32pm UTC](https://community.cdata.com/t/dynamically-call-different-workspacereceive-connectors/612 "2024-01-26T17:32:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![russell-jerseypost](https://avatars.discourse-cdn.com/v4/letter/r/439d5e/32.png) [@russell-jerseypost](https://community.cdata.com/u/russell-jerseypost)\
**Post date:** [January 26, 2024, 5:32pm UTC](https://community.cdata.com/t/dynamically-call-different-workspacereceive-connectors/612/1 "2024-01-26T17:32:01Z")

</div>

I have Workspaces A, B and S

Workspace S (for ‘shared’) is a sort of utility or library workspace.

My plan is for Workspaces A & B to set a message header e.g. \_message.header:callingFlow in Event:BeforeSend and then use WorkspaceSend to call the WorkspaceReceive in S.

S then needs to respond back to the correct calling Workspace.

Can a WorkspaceSend in S dynamically call&nbsp;WorkspaceReceive in A or B based on&nbsp; \_message.header:callingFlow ?

Or do I need use maintain a series of Branches (we could have many more calling workspaces in the future)

---

<div class="post-metadata">

**Author:** ![Arturo\_S](https://avatars.discourse-cdn.com/v4/letter/a/a6a055/32.png) [@Arturo\_S](https://community.cdata.com/u/Arturo_S)\
**Post date:** [February 1, 2024, 8:08pm UTC](https://community.cdata.com/t/dynamically-call-different-workspacereceive-connectors/612/2 "2024-02-01T20:08:11Z")

</div>

Hi Russell,

The Branch connector method that you are likely envisioning would be the ideal solution for this use case. The Workspace Send connector does not support dynamically setting the workspace and connector it will send to.

The headers from your files in one workspace will persist when sent to another workspace through the Workspace Send connector. These header values on files received in your Workspace Receive connector can then be parsed by a Branch connector that will route them to the appropriately configured Workspace Send connector in your ‘S’ workspace.

If you are using Arc 2023 with its updated Branch connector, you should be able to handle all of the routing from a single Branch connector, since the updated Branch connector supports any n number of conditions and outputs for you to check the header value against: [CData Arc - Branch Connector | Version 23.4.8839](https://cdn.cdata.com/help/AZJ/mft/Branch.html)

However, if you are on an earlier build of the application you will need to cascade the Branch connectors (use them in series): [CData Arc - Branch Connector | Version 22.0.8473](https://cdn.cdata.com/help/AZH/mft/Branch.html#cascading)