Respond to Webhook
output.http-response Output v0.1.0 Answers the HTTP trigger's request mid-flow with a status, headers, and body — the run continues afterwards. Runs not started by HTTP pass through unchanged.
Ports
| Direction | Port | Label |
|---|---|---|
| Input | input | Input |
| Output | output | Output |
Properties
| Property | Type | Default | Description |
|---|---|---|---|
Status codestatusCode | int | 200 | HTTP status code to respond with. The first Respond to Webhook node in a run answers the HTTP trigger immediately — the workflow keeps running afterwards. Runs not started by HTTP pass through unchanged. |
Headersheaders | json | {} | Extra response headers as a JSON object, e.g. { "x-request-id": "abc" }. |
Respond withbodyMode | select | "payload" | What to send as the response body: the node's current input payload (as JSON), a custom JSON value, or custom text. payloadjsontext |
Body (JSON)body | json | — | The JSON value to respond with. Shown when bodyMode === "json" |
Body (text)body | string | — | The text to respond with. Shown when bodyMode === "text" |
This page is generated from the node registry by gen-node-docs.mjs on every
site build — ports, properties, defaults and visibility rules cannot drift from the code.