Skip to main content

HTTP

ActionRole
Make HTTP RequestOutbound HTTP client call.
Respond Text / Respond JSON / Respond HTMLReturn a body to the client (URL / Form / Webhook where allowed).
Respond FileFile download response (URL / Form).
Respond StatusStatus-only response (URL / Form / Webhook).
RedirectLocation redirect (URL / Form / Webhook).
Close WindowResponse that closes the browser window (URL / Form).

Make HTTP Request

Sends an HTTP request and returns the raw response. Inputs
  • URL — Full request URL.
  • MethodGET, POST, PUT, PATCH, or DELETE.
  • Body & Content type — Shown for methods that allow a body (POST, PUT, PATCH). Pick a content type from the list (text types such as application/json use a string body; binary types such as multipart/form-data or image/png use a file body). You can also type a custom MIME string in the combobox.
  • Query parameters — Optional list of name/value pairs appended to the URL.
  • Headers — Optional request headers (name/value pairs).
Outputs
  • response — Response body as text (treat encoding according to the server; binary responses may not round-trip cleanly as string—use integrations that return files when you need bytes).
  • status — Numeric HTTP status code.
  • Headers — Response headers as a destructurable object (string values per header).

Response actions (URL, Form, Webhook)

These nodes finish the HTTP response for workflows started by URL, Form, or (where noted) Webhook triggers. Webhook-capable: Respond Text, Respond JSON, Respond Status, Redirect — also allowed with Webhook in addition to URL/Form. URL + Form only: Respond HTML, Respond File, Close Window.

Respond Text

Inputs
  • body — String body.
  • status — Optional; default 200 (config toggle).
  • content typetext/plain, text/html, or application/json (declares how the client should interpret body).

Respond JSON

Inputs
  • body — Any value; serialized to JSON.
  • status — Optional; default 200.
  • pretty — Pretty-print JSON (default on).

Respond HTML

Inputs
  • body — HTML string.
  • status — Optional; default 200.

Respond File

Inputs
  • file — File to return.
  • status — Optional; default 200.
  • Send content asInline (display in browser) vs Attachment (download).

Respond Status

Inputs
  • status — HTTP status code (wired input / handle on the node; set the code your client should receive).
No body content—status-only response.

Redirect

Inputs
  • url — Location header target.
  • status — Redirect code; default 302 (config describes 301 vs 302 semantics).

Close Window

Inputs
  • status — Optional status for the response wrapper (same pattern as other respond nodes using StatusCodeInput).
Returns a response body that includes JavaScript to close the window (for popup-style flows).