Playbook Discovered Outputs and Map Inputs

what if you want to test your action to see the possible outputs? this can be done at the action level let's take a look at the how to test the actions/connectors that turbine supports scenario owen is an orchestrator who is trying to get data from jira project owen’s company has custom fields in their project owen can test the action, view the result data and update the outputs with his tested data owen’s playbook receives a webhook event however, the webhook body is not available for easy mapping in the playbook owen sends a webhook to his playbook and updates the output with the webhook event history let's take a look at how owen tests the jira inputs and customizes the outputs first, owen goes to the swimlane content and installs the atlassian jira connector this provides him with several atlassian actions he creates his playbook and adds the desired jira connector click configure and navigate to the test tab owen knows that all testing must occur from the test tab he cannot test from the inputs tab enter the inputs and click test the results pane below, provides the raw json data, but turbine turns that into an easy to read format under the discovered outputs tab owen notices that the original inputs are not providing the exact data he is trying to get from jira so he goes to the discovered outputs click discovered outputs to see the known outputs (shown with a check mark) and remaining outputs (shown without check marks) since he wants to add the x output, he clicks the plus icon next to it now he wants to confirm his outputs click the outputs tab to view all of the outputs that were custom (that owen just added) conclusion the custom outputs are now available and owen can use them downstream as he builds the playbook