The Custom HTTP node calls any HTTP API directly from an automation — for services that do not have a dedicated connector, or for one-off endpoints. It supports REST, GraphQL, and SOAP request styles, lets you set the method, URL, headers, query parameters, and body, and handles authentication (Basic or a custom scheme you configure). You can also control SSL verification, route through a proxy, handle multipart payloads, process streaming responses, and import or export any request as cURL.
Overview
The Custom HTTP node is the general-purpose HTTP client in Unify Automations. Rather than depending on a pre-built connector, you configure every aspect of the request — the style (REST, GraphQL, or SOAP), the endpoint, the method, the headers, the body, and the authentication scheme. The node returns whatever the remote server sends back, including error status codes, so your automation can inspect the outcome and branch accordingly.
Eight actions are available under the Custom HTTP node:
Execute GraphQL Request — Send a GraphQL query or mutation to a GraphQL endpoint.
Execute REST Request — Send a standard HTTP request with full control over method, headers, parameters, and body.
Execute REST Multipart Request — Send a multipart/form-data request that includes file attachments and form fields.
Execute SOAP Request — Send an XML-based SOAP message to a SOAP web service.
Execute SOAP Multipart Request — Send a SOAP message with binary file attachments using MIME multipart encoding.
Execute Streaming REST Request — Send an HTTP request and process the response as a stream of chunks.
Execute Streaming REST Multipart Request — Upload files via multipart and process a streaming response.
Import / Export a Request as cURL — Convert a cURL command into node configuration, or export the current configuration as a cURL command.
Input
The following fields are shared across most Custom HTTP actions. Action-specific fields are documented on each action's page.
Field | Description | Required* |
|---|---|---|
URL | The full endpoint URL the node sends the request to. | Yes |
Authentication Type | Authentication scheme to apply: None, Basic, or Custom. | No |
Username | Login name for Basic authentication. Active only when Authentication Type is Basic. | No |
Password | Password for Basic authentication. Active only when Authentication Type is Basic. | No |
Custom Auth Configuration | Key-value configuration for a custom authentication scheme. Active only when Authentication Type is Custom. | No |
SSL Verification | Toggle to verify the server's SSL/TLS certificate. Enabled by default; disable only in fully trusted, non-production environments. | No |
Proxy URL | Route the request through this HTTP or HTTPS proxy. Use when the target host is only reachable via a proxy. | No |
Run Asynchronously | Execute the request in the background. The automation continues immediately; the response is delivered when the call completes. Not available for streaming actions. | No |
* Required fields must be populated for the node to run.
Output
All Custom HTTP actions return the following output fields after the request completes.
Field | Description |
|---|---|
Status Code | The HTTP status code returned by the remote server (e.g., 200, 404, 500). |
Response Body | The raw response body as a string. Parse it in a subsequent step if you need to access nested fields. |
Response Headers | A map of the response header names and values returned by the server. |
Streaming actions yield response chunks progressively rather than returning a single complete body. See each streaming action's page for details.
Notes
Keep the following in mind when using any Custom HTTP action.
An error status from the remote API — such as 4xx or 5xx — is returned as part of the response, not thrown as an automation failure. Check Status Code in the output and branch your automation accordingly.
A connection-level problem (host unreachable, TLS handshake failure) is different from an HTTP error status: the former halts the node, the latter is a normal response you handle yourself.
SSL Verification is enabled by default. Only disable it in trusted, isolated environments where you control the server certificate.
Run Asynchronously is useful for slow external APIs. The automation does not block on the response, which reduces the chance of a timeout in the automation run.
OAuth tokens must be fetched separately — for example, with another HTTP node or a dedicated connector — and passed as an Authorization header value.