Structs

Overview

Creates a struct reference to a file using a directory path and file name. This struct is used across various systems for handling file-based operations such as loading or saving files. It serves as a general-purpose file descriptor, simplifying access to files on the user's machine.

Inputs

• File Directory – The full system path to the folder containing the file.

• File Name – The name of the file, including its extension (e.g., example.json, output.txt).

Outputs

• HTTPPro File Data – A unified struct representing the target file. It can be used in nodes related to reading, writing, uploading, or processing both JSON and binary file types. This is the core struct used for file-based operations in this plugin.

Overview

Creates a struct HTTP body for use in both ASYNC and non-ASYNC HTTP requests. This body includes headers, raw string data, or a JSON object, depending on your setup. You define the data payload you want to send in the request using this struct. If you use the "JSON Body", the "String Body" will be ignored, and vice versa. This node allows you to configure the content of your request in a clean and reusable format.

NOTE: If no headers are provided, the content type defaults to application/json.

NOTE: If you are sending a GET request, any data payload is ignored. (Json Body + String Body)

Inputs

• Headers – A map of header key–value pairs that should be included with the request.

• Json Body – A fully constructed JSON object to include as the request body.

• String Body – A plain text or formatted string payload (e.g., XML, CSV, or custom text).

Outputs

• HTTPBody – A clean struct that holds all configured request data. Can be passed into both ASYNC and non-ASYNC HTTP nodes for sending POST requests.

Overview

Creates a struct Download Settings used to configure how an HTTP download should be handled. This struct allows you to define whether the response should be saved directly to a file or handled in memory, and to apply custom headers for the request.

NOTE: If no headers are provided, the content type defaults to application/json.

Inputs

• Should Save To File – Boolean value. If true, the downloaded data will be saved directly to disk using the provided File path. If false, data will be handled in memory.

• File – The target file path for saving the download. This is required if "Should Save To File" is enabled.

• Headers – Optional key-value pairs to include in the HTTP download request headers.

Outputs

• Download Settings – A struct representing the full download configuration, allowing full control over how data is processed or stored.

Overview

Creates a struct settings object used to configure multipart HTTP requests. This struct is essential when sending multipart form data, allowing you to define how the boundary string is generated and which headers to include in the request. This node supports both ASYNC and non-ASYNC multipart form submissions.

NOTE: If no headers are provided, the content type defaults to multipart/form-data.

Inputs

• Random Boundary – Boolean. If true, a unique boundary string is automatically generated for the multipart request. When enabled, the Boundary input is ignored.

• Boundary – A manually defined string to use as the boundary separator in the multipart body. Only used if Random Boundary is false.

• Headers – Optional key-value pairs to attach to the HTTP request. If omitted, a default multipart header will be applied automatically.

Outputs

• HTTPRequest Settings – A struct that encapsulates all multipart-specific request settings. Pass this into nodes that send multipart HTTP requests to control boundary formatting and headers.

Overview

Creates a struct that will contain all the information about the files you want to upload. This struct includes both the file’s binary content and detailed metadata such as content types, field names, and additional multipart fields. It’s designed for full compatibility with advanced file upload scenarios (e.g. APIs that require specific field names or multiple data parts).

This node provides fine control over what data is included in the upload, and how it’s formatted, making it flexible for a wide range of HTTP endpoints.

Inputs

• Include File Content Type – If true, the value from File Content Type will be included in the upload request. If false, it is ignored.

• Field Name – The name of the form field where the file should be placed in the request.

• File Content Type – The MIME type of the uploaded file (e.g., "image/png", "application/json"). Used only if Include File Content Type is true.

• File Name – The name of the file to be uploaded, including its extension.

• File Binary – The raw binary content of the file to be uploaded.

• Include Multi Part Content Type – If true, the Multi Part Content Type array will be included in the request. If false, it is ignored.

• Multi Part Content Type – An array of strings representing additional content-type entries for extra multipart fields. Used when uploading form fields alongside files.

• Multipart Data – A key-value map of additional multipart fields to include with the request.

Outputs

• Upload File Data – A reusable struct that encapsulates all file upload data and metadata. Feed this into multipart upload requests for file transfer.