Add links

Author: jpipkin1

docs/platform-services/automation-service/automation-service-integrations.md

@@ -134,7 +134,9 @@ To change the data that is output from an action, see [Edit output of an action]
 
 ## Edit output of an action
 
-When actions run, they typically generate output that is passed on to the next step in a playbook. You can edit the output from actions in certified integrations to add, remove, or modify the output of the action. 
+When an integration's action runs, it typically generates output that is passed on to the next step in a playbook. For information about the format of this output, see [Integration Framework Output](/docs/platform-services/automation-service/integration-framework/integration-framework-output/).
+
+You may want to change the output of an action to allow playbooks to execute different activities downstream from the action. Perform the following steps to edit the output of an action:
 
 1. [Open an integration](/docs/platform-services/automation-service/automation-service-integrations/#view-integrations) and do the following:
    1. [Ensure that it is a certified integration](/docs/platform-services/automation-service/automation-service-integrations/#certified-integrations). Only certified integrations allow you to edit the output of their actions. 
@@ -151,7 +153,6 @@ When actions run, they typically generate output that is passed on to the next s
 1. To ensure that the edited output works, [test the action](#test-action) like we did earlier.<br/>For our example, after we test the action notice how the account type is now displayed in the **Show Details** dialog box: <br/><img src={useBaseUrl('img/platform-services/automation-service/action-output-edited-results.png')} alt="New output displayed in test action results" style={{border: '1px solid gray'}} width="500" />
 1. But there is more output than what was configured to display. To see the complete output, click the **JSON details** button:<br/><img src={useBaseUrl('img/platform-services/automation-service/action-output-test-action-json-details.png')} alt="Output JSON details button" style={{border: '1px solid gray'}} width="500" /><br/>Here you can click expand arrows to examine the output in JSON format. Click buttons at the top of the dialog to return to the display view, download the JSON, or copy the output:<br/><img src={useBaseUrl('img/platform-services/automation-service/action-output-json-details.png')} alt="Output in JSON view" style={{border: '1px solid gray'}} width="500" />
 
-
 ## Cloud or Bridge execution
 
 You can set integrations, and their related action execution, to be executed in the cloud or through the Bridge. Only certified integrations can be executed in the cloud, while custom integrations must be executed through the [Bridge](/docs/platform-services/automation-service/automation-service-bridge/).

docs/platform-services/automation-service/integration-framework/integration-framework-output.md

@@ -7,6 +7,8 @@ description: Learn how to work with output from the integration framework.
 
 import useBaseUrl from '@docusaurus/useBaseUrl';
 
+This article describes the format of integration output. To edit the output of an integration, see [Edit output of an action](/docs/platform-services/automation-service/automation-service-integrations/#edit-output-of-an-action).
+
 ## About integration output
 
 Integrations primarily use JSON to pass data between actions and other internal components. There is no requirement that integrations return JSON results; integrations will execute regardless of the data or data type they return. However, in order to pass data returned from an action to a future action in a runbook or to other internal components, the output from an integration action must be returned in JSON, and the JSON fields must be defined in the output:path attributes of the action definition file. In other words, if the action output is not returned in JSON, it will not be able to be used in any other areas.