Once the integration is created, it is connected to the WorkFlow's Embed or Script node as mentioned in the article located here.
Button-triggered integrations require that the response code be inserted manually into the conditions for the related paragraph fields that are configured to display the outcome of the integration's action.
These response codes can easily be retrieved from the Response section of the Step 2 Advanced tab:
In the case of the CardConnect Aggregated integration, the first data.response_code = 'card:success'
If you scroll through the rest of the response script code, you will also find:
data.response_code = 'integration:timeout'
data.response_code = 'card:invalid'
data.response_code = 'card:decline'
Depending on the action taken by the integration, the response codes will vary. However, it is always imperative that they be copied into the guided interaction exactly (and without quotes) as they are programmed.
The above screen is configured when using a button field to trigger the integration. For more information on that, click here.