Which Automation Action should you use to run different workspaces based on upstream message contents?

Which Automation Action should you use to run different workspaces based on upstream message contents?

• A. Run a Workspace
• B. Filter messages
• C. Run a Dynamic Workspace
• D. Merge messages

Answer: (B)

Routing based on what the upstream messages contain is done by using a filter that splits the automation flow into branches according to the message’s attributes or content. The Filter Messages action examines the incoming data and directs each message to the appropriate path. Put a Run a Workspace action on each of those paths so the workflow that runs depends on which condition was met. This lets you trigger different workspaces for different message contents in a clean, maintainable way. If you used a single Run a Workspace action, you’d always execute the same workspace, so the content-driven differentiation wouldn’t be possible. Merging messages doesn’t address routing by content, and a Dynamic Workspace could select a workspace at runtime but requires mapping content to workspace names—the filter-and-branch approach is the straightforward, reliable pattern for this use case.

Routing based on what the upstream messages contain is done by using a filter that splits the automation flow into branches according to the message’s attributes or content. The Filter Messages action examines the incoming data and directs each message to the appropriate path. Put a Run a Workspace action on each of those paths so the workflow that runs depends on which condition was met. This lets you trigger different workspaces for different message contents in a clean, maintainable way.

If you used a single Run a Workspace action, you’d always execute the same workspace, so the content-driven differentiation wouldn’t be possible. Merging messages doesn’t address routing by content, and a Dynamic Workspace could select a workspace at runtime but requires mapping content to workspace names—the filter-and-branch approach is the straightforward, reliable pattern for this use case.