n8n Respond to Webhook nodeConfigure Respond to Webhook in n8n.

By default the node has a single output branch carrying its own input data. This option adds a second branch holding the response object that was sent to the webhook, so the rest of the workflow can inspect exactly what the caller received. It lives in the Settings tab of the node, not in the main panel.

• Enable Response Output Branch: a boolean that turns the second output on. The node then exposes Input Data, the original branch passing on the node's input, and Response, the object sent back to the webhook.

This selector decides what travels back through the open HTTP connection. Eight choices, from a full JSON dump to an empty body.

• Respond With: allIncomingItems returns every input JSON item, firstIncomingItem only the first, json a custom body set in Response Body, text a text body that ships as HTML by default with Content-Type: text/html, binary a file, jwt a token built from Payload, redirect a jump to Redirect URL, noData an empty body.
• Response Data Source: for a file, automatically picks the single binary in the input, set expects the field name in Input Field Name.

Status codes carry meaning that a body cannot. This option sets the HTTP response code returned to the caller, and defaults to 200 when left alone. Add it whenever the caller reads the code before it reads anything else, which is most machine-to-machine traffic.

• Response Code: a number, defaulting to 200. Typical values come from an expression such as {{ $json.status }} when an earlier node already decided the outcome.

Some callers need more than a body: a content type, a cache directive, a custom key their client reads. This option adds headers to the webhook response, one entry at a time, through the Add Response Header button.

• Name: the name of the header, typed exactly as the caller expects it.
• Value: its value, which accepts an expression like {{ $json.token }} when it changes per execution.

Raw items at the top level of a response are awkward to consume. This option wraps them: it sets the name of the response field that holds all items. It is available when Respond With is on allIncomingItems or firstIncomingItem, and it stays hidden otherwise.

• Put Response in Field: a string naming the wrapper field, for example data, which is also the placeholder shown in the panel.

Long answers do not have to arrive all at once. Turned on, this option sends the data back to the caller using streaming, so the client can display content while the workflow is still producing it. It has one hard requirement on the other end of the flow.

• Enable Streaming: a boolean. It needs a trigger configured with Response mode set to Streaming, otherwise the setting has nothing to stream through.