Skip to main content

Proxy Node

What it does​

Forwards the in-flight request through gateway proxy logic to a configured upstream target and returns upstream response metadata for routing.

Inputs/config​

  • Upstream URL/service mapping from collection/proxy configuration.
  • Optional timeout, retries, and auth headers from proxy config.
  • Can consume transformed headers/body from prior nodes.

Outputs/branches​

  • Uses matched_output.
  • success on upstream success.
  • error on upstream/network/timeout failure.

Example usage snippet​

{
  "id": "n2",
  "type": "proxy_node",
  "next": {
    "success": "n3",
    "error": "n_err"
  }
}

Common pitfalls​

  • Expecting proxy auth to auto-apply without correct profile/credential binding.
  • Ignoring non-2xx responses and always routing to success.
  • Not handling timeout and DNS failures in error branch.