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 17).

Modal Editor

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

• Value for the query parameters (2).
• Input JSON (3).

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 18, the URL that will be called is depicted with the corresponding query parameters values.

Executing the Action

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

🚧

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

Closing the Modal

Clicking Close (3 - Figure 19) will close the modal, bringing you back to the visualization of the action (Figure 13 from this page).
Clicking Back to test (4 - Figure 19) takes you back to the Test Action modal of Figure 18.

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.

📘

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.

Troubleshooting

If you have questions or technical issues, please open a ticket using this form.