What is an HTTP Request Node?
The HTTP Request Node is a powerful execution step within Jodoo Automation that facilitates seamless integration with external systems by executing API calls. It allows for robust data exchange without the need for custom front-end development.
This node is designed to send an HTTP request to a specified external URL, retrieve the response data, and parse it. The parsed data is then made available for use by subsequent nodes in the Automation workflow, enabling complex, automated data processes.
When to Use it
The HTTP Request Node is used to initiate data interactions with external systems directly from within the Automation process. This is ideal for scenarios such as:
Real-time Data Retrieval: Fetching up-to-date information (e.g., stock prices, weather data, or exchange rates) from third-party APIs.
System-to-System Communication: Triggering actions or submitting data to other business applications (e.g., a CRM, ERP, or logistics platform). For example, automatically calling a logistics API with a tracking number submitted in a Jodoo form, then using the returned details to update the form or notify the user.
Prerequiste
This is a paid feature. For details, contact our Sales Team.
How to Set it up?
Step 1 Adding the Node
After setting up the Trigger Node in your Jodoo Automation workflow, add the HTTP Request Node as an execution step based on your process requirements.
Step 2 Configuring Request URL
Request Method
The node supports two standard HTTP methods:
GET: Used for data retrieval. Parameters are appended to the URL as a query string. For example:
?code=123
POST: Used for submitting data. Data is typically sent in the request body.
Note: Only the HTTPS protocol is supported. The request URL cannot be a Jodoo API endpoint.
URL Field Insertion
The URL supports dynamic insertion of field values from upstream nodes. When using the GET method, these fields are used to construct the query string.
Field Name | Parsing Value Format |
Single Line | Text |
Multi Line | Text |
Number | Number |
Radio | Text |
Checkbox | Text (comma separated) |
Dropdown | Text |
Multi Select | Text (comma separated) |
Date&Time | Timestamp, e.g., "2025-09-16T16:00:00.000Z" |
Serial Number | Text |
Submission Time | Timestamp, e.g., "2025-09-16T 16:00:00.000Z" |
Update Time | Timestamp, e.g., "2025-09-16T 16:00:00.000Z" |
Trigger Time | Timestamp, e.g., "2025-09-16T 16:00:00.000Z" |
Extended Field | Text |
Step 3 Configuring Headers and Body
GET Requests: Only Request Headers can be configured.
POST Requests: Both Request Headers and Request Body can be configured.
Request Headers
Headers are configured as Key-Value pairs. The Value field supports dynamic insertion of upstream field values. A maximum of 50 headers is allowed per request.
Request Body
The body format must align with the external API's requirements.
Format | Configuration |
No Body | No configuration required. |
TEXT | Supports direct insertion of upstream field values. |
form-data / x-www-form-urlencoded | Configured as Key-Value pairs. The Value field supports dynamic insertion of upstream field values. |
Note:
The request body currently does not support JSON format. A maximum of 50 body parameters is allowed.
Step 4 Choosing return value format
The node supports parsing responses in two formats:
Return Value Format | Parsing Result |
JSON | Parsed into structured data types: Text, Number, Text Array, and Subform (which can contain Text, Number, or Text Array). |
TEXT | Always parsed as a single Text value. |
Step 5 Setting timeout and debugging
•Request Timeout: The timeout can be customized up to a maximum of 600 seconds.
•Debugging: After configuration, you must debug the interface to parse the response structure for use by downstream nodes. The maximum supported response body size is 256 KB.
Troubleshooting and Error Codes
The following table lists common error codes returned by the HTTP Request Node:
Error Code | Error Message | Suggested Action |
100134 | Invalid URL format or unable to parse | Verify the request address is correctly formatted. |
100135 | Protocol mismatch | Ensure the request address uses the HTTPS protocol. |
100136 | Invalid target port | Check network/security settings or try an alternative port (if using IP: Port access ). |
100137 | Unable to access the target server | Verify the request address is correct and the server is reachable. |
100138 | Invalid or forbidden client IP address | Confirm the client IP is a public IP and not restricted by the target server's policies. |
100140 | HTTP request call exception | Review the configuration and external API documentation. |
100141 | Return body exceeds 256 KB | The response size limit was exceeded. |
100146 | Node execution timeout | Re-execute the node using the "Retry" button. |