keep-alive-proxy

n8n community node: HTTP(S) request through a forward HTTP proxy with a persistent keep-alive agent, so consecutive requests reuse the tunnel instead of paying TCP+CONNECT+TLS setup every time. The stock HTTP Request node does not reuse proxied connection

Package Information

Released: this month
Downloads: 0 weekly / 0 monthly
Latest Version: 0.1.2

Available Nodes

Documentation generating…

Keep-Alive Proxy Request icon
Keep-Alive Proxy Request
HTTPS request through an HTTP proxy with persistent connection reuse

Documentation

n8n-nodes-keep-alive-proxy

n8n community node Keep-Alive Proxy Request: makes an HTTPS request through a
forward HTTP proxy using a persistent keep-alive agent, so consecutive requests
reuse the established CONNECT tunnel instead of paying TCP + CONNECT + TLS setup
on every call.

Why

The stock n8n HTTP Request node opens a new proxied connection for every
request: repeated calls through the same proxy re-pay the full tunnel setup
(hundreds of milliseconds per call on long-RTT chains). This node keeps one agent
per proxy URL alive in the n8n process and reuses it across nodes and executions.

Install

n8n → Settings → Community Nodes → Install → n8n-nodes-keep-alive-proxy

Node parameters

Parameter Description
Proxy URL Forward HTTP proxy, e.g. http://host:port (CONNECT style)
Method GET / POST / PUT / DELETE
URL Full https:// target URL
Send Headers Extra headers (name/value pairs)
Send Body Raw body as a string (n8n expressions apply); defaults Content-Type: application/json
Send File (multipart) Attach binary data as a multipart/form-data file, plus optional plain form fields
Binary Property Binary property name holding the file (default data)
Timeout (ms) Request timeout, default 30000

Credentials

Optional: select the built-in Groq API credential — its key is sent as
Authorization: Bearer <key>. Leave empty if you pass your own Authorization
header manually.

The first non-4xx response body is parsed as JSON when possible and returned as
the item JSON; otherwise { data: "<text>" }. Status ≥ 400 fails the node with
the upstream body in the error message.

Limitations

  • Only https:// targets (proxy tunneling via CONNECT).
  • Proxy authentication is not supported yet (unauthenticated forward proxies only).
  • One shared agent per proxy URL (keep-alive sockets, up to 16 concurrent).

Local test

npm install && npm test

License

MIT

Discussion