HTTP Request

The HTTP Request Node enables developers to send requests to external services via the HTTP protocol, facilitating data retrieval, submission, and interaction. It supports multiple HTTP request methods and allows developers to configure request parameters, headers, authentication information, request bodies, and other settings to meet diverse data interation requirements.

Additionally, the HTTP Request Node provides timeout configurations and retry mechanisms to ensure request reliability and proper handling of data.

Node Configuration

When implementing data retrieval, submission, and other functionalities using an HTTP Request Node, developers typically need to configure parameters such as API, request parameters, headers, authentication, request body, etc.

Authentication: Supports None, Bearer Token, Basic Auth, and Service Auth methods, enabling quick input of authentication information to complete the authentication.
Request Line: Supports mainstream request methods including GET, POST, PUT, DELETE, and PATCH.
Body: Supports standard formats such as form-data and x-www-urlencoded.
Params/Headers/Cookies: Supports configuration of corresponding parameters.
Timeout Configuration: Allows setting a timeout duration in seconds. Requests exceeding this threshold will be terminated automatically.

Node Output

The HTTP component provides two output modes:

Compressed Escape: The system will compress and escape the returned JSON response, then assign it to the resp field. You can add a "Code" node downstream to process the JSON information within resp.
Custom JSON: Define a custom JSON structure within resp to specify the fields you need. The node will output only those fields. However, please note that the Key must correspond exactly to its position in the original HTTP response structure.

If the HTTP response structure is long, it is recommended to use Compressed Escape mode to reduce configuration complexity. It is advised to handle further processing downstream using a Code node. If the response structure is simple, using Custom JSON is preferred, as it makes downstream references clearer and more intuitive.