Feature Documentation: Action Dependencies and Data Resolvers

This guide explains how to dynamically chain actions together within the Developer Portal using Resolvers. This mechanism allows the system to automatically populate an input field in one action using the output data from another action.

1. Setting Up a Data "Resolver" (Output Configuration)

When configuring or editing an action, you can designate exactly one specific output parameter to act as a system-wide data provider.

• How to configure it: Navigate to the Output tab within the Action Editor. Locate the specific data field (e.g., $.body.users[0].firstName) and select Set as resolver. Once activated, a green Resolver ✓ badge will appear next to the property.

• Modification Constraint: A designated resolver can be changed or removed at any time, provided that no other action in the system has already subscribed to use it.

2. Subscribing to a Dependency (Input Configuration)

To automatically map a resolver's output to another action's input, use the Add new input or Edit input configuration modal.

1. Open the input configuration modal for the field you want to automate.

2. Check the box labeled Dependency resolved by.

3. Use the dropdown menu next to it to select the specific action that has the active data resolver configured.

4. Provide a system Name, user-facing Label, and save the configuration. The field will now automatically inherit its values during execution.

3. Monitoring Dependencies in the Action List

To give you an immediate overview of your data workflows, the main API action dashboard displays status indicator badges next to each action's state flag:

• Resolver ✓ (Green Badge): Indicates that this action contains an output parameter serving as a data provider for another part of the system.

• Resolved by (Blue Badge): Indicates that this action has an input dependency relying on a previously configured resolver action to populate its data.