HTTP Request

About HTTP Request

The HTTP Request node sends an HTTP request from the workflow to an external endpoint.

It is a service node and can be used to send workflow data, variables, and document-related information to another system.

How HTTP Request works

When the workflow reaches this node, it sends the configured request to the specified HTTPS endpoint.

The workflow then continues through either the success or fail path depending on the response.

Settings

The node currently includes the following settings:

Node Name
Description
URL
Method
Headers
Request Body
Number of Retries
Ignore certificate errors
Follow redirects

URL

The URL field defines the endpoint the request is sent to.

Only HTTPS URLs are allowed.

Method

The available request methods are:

GET
POST
PUT
PATCH
DELETE

Headers and body

The Headers field is a JSON field used to define request headers, such as content type or authorization.

Example:

{
  "Content-Type": "application/json",
  "Authorization": "Bearer YOUR_API_KEY"
}

The Request Body field defines the data sent with the request. Workflow variables can be included in the JSON body.

Example:

{
  "dossierID": "{dossierID}",
  "documentCollectionUrl": "{documentCollectionUrl}"
}

Retry and redirect behavior

The Number of Retries setting controls how many times failed requests are retried automatically.

The supported range is 0–10, with 3 as the default.

The Follow redirects option allows the request to automatically follow HTTP 3xx redirects. This option is enabled by default. The Number of Retries setting controls how many times failed requests (due to network errors or 5xx server errors) are automatically retried. Failed 4xx errors are not retried. Each retry attempt includes exponential backoff to avoid overwhelming the destination service.

Security options

The Ignore certificate errors option skips SSL/TLS certificate verification.

This should normally remain disabled unless there is a specific reason to bypass certificate validation.

Output Paths

The node includes the following output paths based on HTTP response code:

Success (2xx) – Request returned a successful HTTP status code (200-299)
Fail (4xx/5xx) – Request returned a client error (400-499) or server error (500-599) after retries

Note: 3xx redirect responses are handled by the "Follow redirects" option. If enabled, the request automatically follows the redirect chain and returns the final response code. If disabled, 3xx responses route through the Fail path.

Security Notes

Use HTTPS endpoints and handle credentials carefully.

Authorization values should be placed in headers where appropriate, and sensitive values should only be included when required by the receiving system.

Avoid disabling certificate validation unless it is specifically needed for the integration.