Checking the Send Only Additional Input checkbox allows the Remote Action element to send only the key/value pairs specified in Additional input to the Apex method. The Additional input should have the same keys as the method parameters, and the values should be set to
{{InputData.node}} for each node. For example, AccountId: {{InputData.AccountId}} and ProductId: {{InputData.Details.Products}}.

In OmniStudio Integration Procedures, when you want to reference the output of an element in a nested block (e.g., for use in a Remote Action or another step), you must use dot notation that mirrors the block structure hierarchy.
In the exhibit:
* Action1 is nested inside:
* BlockB, which is nested inside:
* BlockA
Therefore, the correct Send JSON Path to access the result of Action1 is:
CopyEdit
BlockA.BlockB.Action1
This format complies with the standard output reference syntax in Integration Procedures, which follows the pattern:
php-template
CopyEdit
<ParentBlock>.<ChildBlock>.<ActionElement>
Incorrect Options:
* B. BlockA:BlockB:Action1 - Uses colons instead of dots. This is invalid syntax in JSON path resolution within Integration Procedures.
* C. Action1:BlockB:BlockA - Incorrect order and invalid separators.
* D. Action1.BlockB.BlockA - Incorrect order (reversed path).
Reference:
Salesforce OmniStudio Developer Guide # Integration Procedure Element JSON Pathing Best Practices for Send JSON Path # Nested Blocks and Element Referencing

The Add Response To Response JSON property on the DataRaptor Action indicates that the output of the DataRaptor should be added to the response JSON of the Integration Procedure. If this property is not set to true, the response will be empty even if the DataRaptor extracts data successfully.

When an OmniScript receives incomplete data from an Integration Procedure, the issue is typically in Response JSON path mapping or naming mismatches.
A). The missing data is trimmed in the Integration Procedure Action Response JSON Path ?If the Response JSON Path only points to part of the structure, any nested or unrelated values are excluded from the output.
B). The element name for the missing data does not match the JSON node key in the Integration Procedure Response ?OmniScript expects a matching node name to bind the data to UI elements. If the key doesn't match, that field will appear blank.