Remote Procedure Calls

To find the RPC debug tool:

1

Navigate to the Custom apps area.

2

Select your custom app from the list.

3

Click the Remote Procedures tab.

4

Select the RPC you want to debug.

5

Click Test RPC.

RPC page

Compare the tabs below to how to access information about your RPCs in Make.

Communication tab

After creating a new RPC, you can modify the default template in the Communications tab for your needs.

Default Communication

Customized Communication

Inside RPC, you can use the relative path and the full form of the URL.

However, we advise using the relative path across all your RPCs and modules.

A relative path is added to the "baseUrl" that you need to specify inside the app Base.

Parameters tab

By default, the Parameters tab is empty. Here you can add any parameter you need. You can also add mappable parameters from a module. Learn more about using RPC parameters.

Default Parameters

Customized Parameters

Any parameter created inside an RPC will be available only for RPC debugging. It will not be visible inside your modules or inside scenarios.

To preview and test parameters, click on the Test RPC button.

Default Preview

Customized Preview with Parameters

RPC debug tool

The RPC debug tool works the same way modules do.

1. Specify the connection and other fields (parameters) if needed.

2. Click the Test button.

3. The call, which you specified before in the RPC communication, will be executed.

You will see the output that you specified in the RPC communication.

If you specified output as "label" and "value" (with the purpose of using it inside a Select parameter), do not expect to see the full server response there.

Input

Output

Communication code

Debug RPCs in the web console

Sometimes you may need to look into the request you're sending and the response from the API.

You can see more details about the RPC you're testing by opening your browser's dev console: Network tab.

The debug values show the request being sent and the response received by the API.