Respond to Webhook Node

Send a custom HTTP response to a webhook trigger. Supports JSON, text, binary, redirect, and more. JWT mode not supported.

Written By pvdyck

Last updated About 3 hours ago

Respond to Webhook Node

The Respond to Webhook node sends a custom HTTP response back to the caller of your Webhook Trigger.

Parameters

ParameterDescription
Respond WithThe response mode (see modes below)
Status CodeHTTP status code to return (default: 200)
Response HeadersCustom headers to include in the response (key-value pairs)

Respond With Modes

ModeDescription
First Incoming ItemRespond with the first input item's JSON
All Incoming ItemsRespond with all input items as a JSON array
JSONRespond with a custom JSON body you define
TextRespond with a custom text/plain body
No DataRespond with an empty body (useful for 204 responses)
BinaryRespond with binary data from the input item
RedirectRedirect to a URL (307 status by default)

Redirect Mode Parameters

ParameterDescription
Redirect URLThe URL to redirect the caller to

Options

OptionDescription
Response HeadersAdd custom headers (e.g., Content-Type, Cache-Control)
Put Output in FieldStore the sent response data in a field for downstream nodes

Limitations

  • JWT mode not supported -- Cannot generate JWT tokens for webhook responses
  • No streaming -- Binary data is returned as a complete response; chunked/streaming transfer is not supported

Tips

  • Place this node at the end of your webhook workflow to control exactly what the caller receives
  • Use "No Data" with status 204 for fire-and-forget acknowledgments
  • Set appropriate Content-Type headers when returning non-JSON data

Related