DocumentationAdobe Workfront Fusion

Chain modules

Last update: May 20, 2026
IMPORTANT
This feature is in Beta and is not recommended for mission-critical production workflows. As a Beta feature, behavior may change and edge cases may not be fully handled.
For stable integrations, consider triggering a second scenario via webhook using an HTTP Request module — this pattern uses fully supported primitives and gives each scenario independent execution control.
If you choose to use chained scenarios, review Chain multiple scenarios together for design guidance.

Using the Chain modules, you can connect one scenario to another.

For instructions on planning chained scenarios, see Chain multiple scenarios together.

Access requirements

Expand to view access requirements for the functionality in this article.
table 0-row-2 1-row-2 2-row-2 layout-auto html-authored no-header
Adobe Workfront package

Any Adobe Workfront Workflow package and any Adobe Workfront Automation and Integration package

Workfront Ultimate

Workfront Prime and Select packages, with an additional purchase of Workfront Fusion.
Adobe Workfront licenses

Standard

Work or higher
Product If your organization has a Select or Prime Workfront package that does not include Workfront Automation and Integration, your organization must purchase Adobe Workfront Fusion.

For more detail about the information in this table, see Access requirements in documentation.

Chain modules and their fields

Triggers

Receive data from parent

This module is the trigger module in the child scenario, and is triggered by the Call a child scenario module in the parent scenario. It receives data from the parent scenario, which can be processed in the child scenario.

To configure the Receive data from parent module:

  1. To use an existing data structure, in the Data structure field, select the data structure that will be used for the scenario’s input data.

    Or

    To create a new data structure to use as the scenario’s input data, click Add next to the Data structure field and create the data structure.

    For instructions on creating a data structure, see Data structures.

  2. Click OK to save the module.

Actions

Call a child scenario

This module is located in the parent scenario. The fields reflect the data structure set in the Receive data from parent module in the child scenario.

IMPORTANT
Review the following before configuring this module in a production scenario:
  • Do not enable Commit Trigger Last (CTL) on this scenario when Fire and Forget is disabled. CTL will retry the scenario when it suspends waiting for a child response, creating an unbounded retry loop.
  • Use caution when placing this module inside an iterator. Dispatching a child scenario for each item in a large iterator creates significant platform load. Consider inlining the child scenario’s logic or pre-computing shared lookups outside the iterator.
  • Fire and Forget means the parent has no visibility into whether the child ran or succeeded. Use only when child failures are monitored independently.
For full design guidance, see Chain multiple scenarios together.
NOTE
  • You can select an existing child scenario, or create a new one through this module.
  • You can create the data structure when creating child scenario.

To configure the Call a child scenario module

  1. Add the Call a child scenario module to your scenario.

  2. To use an existing child scenario, in the Chain field, select the child scenario that you want to call.

    Or

    To create a new child scenario, click Add next to the Chain field. The child scenario appears in a separate window, with the Receive data from parent and Return response from parent modules in place.

    The fields configured in the trigger module of the child scenario appear in the Call a child scenario module.

  3. Enter or map the information to be passed to the child scenario into the Call a child scenario module.

  4. (Conditional) If you want the parent scenario to continue its execution without waiting for a response from the child scenario, enable the Fire and Forget option.

  5. Click OK to save the module.

NOTE
If you create a new child scenario for this module, the child scenario opens in a separate browser window, allowing you to see and configure both the parent and child scenarios at the same time.

Return response to parent

This is in the child scenario, and sends data in the selected structure to the parent scenario. You can map this data in later modules in the parent scenario.

IMPORTANT
If your child scenario has multiple routes, you must ensure the Return response to parent module is reachable from every execution path. If the Return response module is on a route that is skipped or not executed, the parent scenario will wait indefinitely for a response that never arrives.
Add the Return response to parent module after your router, on a route that always executes regardless of the router’s outcome, or add error handling to ensure a response is always returned even when an error occurs.

To configure the Add Responder module:

  1. To use an existing data structure, in the Data structure field, select the data structure that will be used for the data that the child scenario returns to the parent scenario.

    Or

    To create a new data structure for the data, click Add next to the Data structure field and create the data structure.

    For instructions on creating a data structure, see Data structures.

  2. Click OK to save the module.

recommendation-more-help
workfront-fusion-help-workfront-fusion