This trigger action will execute an HTTP request to a specified server via GET, POST, PUT or DELETE.
Action
This trigger action is found under the Networking heading.
Canvas
When dragged onto the canvas, the appearance of the action is a rectangle with two routing points.
The left routing point (red) is the failure route. This route will be taken if there is an error during execution.
The right routing point (green) is the success route. This route will be taken if action executes successfully.
Form
Parameters
| Name | Type | Required | Descriptions |
|---|---|---|---|
| Method | String | Yes | HTTP defines methods (sometimes referred to as verbs) to indicate the desired action to be performed on the identified resource. This action currently supports GET, POST, PUT, and DELETE methods. |
| URL | String | Yes | URL of the specified server to receive or send the HTTP request. The server must refer to a publicly accessible IP address. Local and private IP addresses will result in an error at the time of execution |
| Content type | String | Type of data that will be contained in the body. | |
| Timeout | Integer | The amount of time (in seconds) the server will wait for a response. The default is 30 seconds if left unset or empty. Minimum value is 0, maximum value is 60 seconds. | |
| Headers | Array | Additional information passed between the client and the server in the form of key:value pairs. | |
| Body | Array | The body of the request. This can either be raw or using the helper form. The format of the body will be dictated by the receiving server. Body: Raw takes precedence over Body: Form. | |
| TLS cert | String | TLS (Transport Layer Security) certificate provides communication security while using HTTP request. Paste the TLS certificate in this field1. | |
| TLS key | String | TLS key required to communicate with the server. Paste the TLS key in this field. |