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.

The Respond to Webhook step on the Studio canvas — The **Respond to Webhook** step as it appears on the Studio canvas — input pins on the left, output ports on the right.

Finding it in the library

Search the builder's node library for Respond to Webhook (it lives under Output). A single click opens the in-editor docs panel shown here — description, ports, and every property, without leaving the canvas. Double-click (or drag) to add it to the workflow.

Respond to Webhook in the node library, with the in-editor docs panel open — The library entry and the in-editor docs panel for **Respond to Webhook** — the same reference this page is generated from.

Wired up in the builder

Respond to Webhook in a real, runnable flow — captured live from the Studio editor, exactly as it looks on your canvas. This is the same workflow used for the example input & output below.

Respond to Webhook wired into a runnable workflow in the Studio builder — **Respond to Webhook** wired into a runnable flow — input on the left, output on the right.

How it’s configured

The node’s Configure panel as it opens in the builder when you select the step — every setting laid out with real values. Click any field to edit it.

The Respond to Webhook node's Configure panel in the Studio builder — The **Configure** panel for **Respond to Webhook**, showing the settings from the flow above.

Ports

Ports are the node’s contract with its neighbours. In the editor a port label renders bold when wired and italic when optional; ◈ ports accept attachment carriers rather than data wires.

Direction	Port	Label	What flows through it
Input	`input`	Input

How data flows through it

Respond to Webhook consumes the content of the incoming envelope — when it is fed directly by a trigger, the trigger’s wrapper is unwrapped at the node boundary so the node sees the actual data, not the metadata shell. Its output becomes the payload for the next node, while the envelope (trace ids, correlation, binary refs) rides along untouched. In the Runs view you always see the whole envelope for both sides of this node.

Expressions in the config

String-typed properties accept {{ }} expressions evaluated against the incoming item at run time — e.g. {{ $json.customer.email }}. On this node that’s body. JSON- and code-typed fields never interpolate — they are passed through literally.

Build it with AI

Every node in this reference is reachable through Flowdrome’s AI Copilot and the MCP tools — say what you want, and the graph surgery happens server-side. Node types resolve fuzzily, so the catalog label (Respond to Webhook) works as well as the exact type id (output.http-response).

In the Copilot panel (or any connected AI):

add a respond to webhook node after the trigger

As a step in a create_chain_workflow call:

{"type":"Respond to Webhook","config":{}}

Raw MCP call — add this node to a workflow with add_node

curl -s -X POST http://localhost:48170/mcp -H "content-type: application/json" -d '{ "jsonrpc": "2.0", "id": "1", "method": "tools/call", "params": { "name": "add_node", "arguments": { "workflowId": "<id>", "type": "Respond to Webhook" } } }'

Example input & output

Captured from a real test run of the workflow above — this is what you see in the run data panel after pressing Test workflow.

Input — what the node received

{
  "kind": "json",
  "contentType": "application/json",
  "payload": {
    "p": 1
  },
  "body": {
    "p": 1
  }
}

Output — what the node produced

{
  "kind": "json",
  "contentType": "application/json",
  "payload": {
    "p": 1
  },
  "body": {
    "p": 1
  }
}

Property reference

Every setting, with its type and default — the same fields shown configured in the panel above.

Property	Type	Default	Description
Status code `statusCode`	`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.
Headers `headers`	`json`	`{}`	Extra response headers as a JSON object, e.g. { "x-request-id": "abc" }.
Respond with `bodyMode`	`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"`

Related nodes

The rest of the Output group — the same folder you’d scan in the editor’s library.

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. The screenshots and example data are captured from a live Flowdrome by npm run shots:nodes and npm run gen:examples.