Testing an Action

It is possible to verify if an action is correctly configured within the Integrations Manager, while the action is still on Draft status and thus, still editable.


An action can be tested regardless of its status.

The first step is to click Test Action (Figure 15).

Figure 15 - Test ActionFigure 15 - Test Action

Figure 15 - Test Action

This will open the modal (Figure 16). In this modal, it is possible to add/edit the:

  • Value for the query parameters (2).
  • Input JSON (3).
Figure 16 - Test Action ModalFigure 16 - Test Action Modal

Figure 16 - Test Action Modal

Both query parameters and input JSON will only be editable if the action has configured query parameters or input schema, respectively.


On (1) from Figure 16, the URL that will be called is depicted with the corresponding query parameters values.

Finally, clicking Execute (4 - Figure 16) will execute the action. The result of the execution will then appear as depicted in Figure 17. The result is divided in two parts: the HTTP Response Status Code (1) and Response Body (2), from Figure 17.

Figure 17 - Result of Execute on Test Action modalFigure 17 - Result of Execute on Test Action modal

Figure 17 - Result of Execute on Test Action modal


This will execute the action in the URL presented in (1) from Figure 16, as explained in the warning (5) from Figure 16. If the action is, for instance, creating a new contact, a contact will be created in the external system, if the execution is successful.


Clicking Close (3 - Figure 17) will close the modal and return to visualization of the action (Figure 12 from this page).
Clicking Back to test (4 - Figure 17) takes you back to the Test Action modal of Figure 16.

There is a chance that an error is returned on the test process. This might be due to the timeout being reached while waiting for the API response. When this happens, the error below will be shown.

Figure 18 - Error while waiting for the API responseFigure 18 - Error while waiting for the API response

Figure 18 - Error while waiting for the API response


Although an issue might have occurred, this does not mean that the action was not properly executed on the external system, as the error only indicates that a response was not properly received.
A validation must be made in the external system if the action has in fact caused a change, or you must try again.


Executing an Action outside Connections

Please note that if you are able to successfully execute an action on a product other than Connections (e.g. Postman), it does not mean the same configuration will work on Connections, as they are different products with different capabilities.

Did this page help you?