ConvertUniverseConvertUniverse Docs

Outputs & Actions

HTTP Request and Webhook Action Nodes Reference

Technical reference for `httpRequest` and `webhook`, including response parsing, SSRF protections, and form-vs-JSON delivery.

Updated 2 min read

Overview

These nodes connect workflows to external APIs:

  • httpRequest fetches data from an external endpoint.
  • webhook sends workflow data to an external endpoint.

Configuration / Settings

NodeSettingDetails
httpRequestmethod, url, responseType, headers, bodybody is used for non-GET methods.
webhookurl, method, sendAs, headerssendAs can be json or form.

Inputs Expected

  • httpRequest does not require upstream input, but URL, headers, and body strings can resolve variables from earlier nodes.
  • webhook usually receives the workflow payload from upstream and forwards it as JSON or multipart form data.

Variables Exported / Outputs

NodeOutput shapeNotes
httpRequestJSON object/array, string, or BlobThe executor decides using responseType and Content-Type.
webhookoriginal inputIt behaves like a send-and-pass-through action.

Important note:

  • httpRequest stores statusCode, statusText, contentType, and headers in execution metadata, not in the main variable payload. Use the node output for {{node_id.field}} expressions, not the metadata fields shown in logs.

Common Use Cases

  • Read JSON from an API, then loop through the returned records.
  • Send generated files or structured data to an external webhook.
  • Fetch configuration data before a branch or template-fill step runs.

Edge Cases

  • Both nodes enforce SSRF protections and block localhost, private IP ranges, and known metadata-service hosts.
  • Invalid JSON in headers or body throws before the request is sent.
  • Binary httpRequest responses are returned as blobs, which makes them compatible with later file nodes.