Once you create and test all the endpoints of an action, you can test the action using our web app before making it live for your users.

A little about Actions

An action is a step that is initiated by our platform and performed at your end. Learn more about actions and how to create action endpoints

Let's say you implemented an action Create Message in your app, Basecamp.

Testing Action

Before testing your action, we recommend that you test all your endpoints individually, so when testing the action everything works fine. 

From the Basecamp API, we know to create a message you need to send a POST call, along with a payload and some query parameters. Keeping in view these details, like endpoint, activity fields, auto-hooks etc. let’s say you have created your action, created respective endpoints, tested them, now let’s test the action. 

Once the action is saved, under the Actions tab in your app menu you can view the list of actions. In front of the action name, you can view a Test icon as shown below.

In order to test the action, click the Test icon. Once clicked, a Test Interface appears in front of you as shown below. 

You need to select the User Account in the Select Your Account drop-down field. As you select an account the action activity fields appear. Activity fields are the fields where you need to specify the data that need to be sent to your app (Basecamp in this case). The fields that appear for this particular action are shown below. 

The fields that appear can be dependent on each other. Like when you select an account, the respective projects in that account appear and so on. Fill in the fields and Send the test call. 

Success or Error Message

When you send the test call, at the bottom of the form the status of the call along with a message is displayed. It tells us whether the action was performed or not. It can display both success or error message. 

You can view the details of the call sent by clicking the View Details button at the right side as shown below. 

When you view the details another form opens as shown below.

 Let us see the individual elements of the form below:

Once you view the details, you can view the following elements:

Request URI: Displays the URL that was called as a result of this endpoint

Request Headers: The headers that were attached along the request, depending on the app (Basecamp in this case) documentation

Response Headers: The headers that were received along the response

Request Body: Displays the structure of the request body sent to the external API

Response Body: The shape of the response received after transforming it using Response Template

Saving Activity Output

At the end of the form, you can view a Save Output button as shown below.

If you click it, the response received is saved as the activity output. The output then appears in the Action Output field that appears in the action details in the Actions tab. You can view the Action Output field below. 

The activity output helps in mapping data. 

When the action is tested properly and looks good to go, add it to a template and test it with your test users. Once all looks good, publish template and let your users start creating integrations. 

Happy Integrating!

Did this answer your question?