Sign In

Webhook Response

Send a custom HTTP response back to the caller of a Webhook Listener trigger.

The Webhook Response node sends a custom HTTP response back to the caller that triggered the workflow. It is designed to work with a Webhook Listener set to "Wait for Completion" response mode. You control the status code, content type, headers, and body of the response.

Configuration

FieldTypeRequiredDescription
Status CodeNumberYesHTTP status code to return (100-599). Defaults to 200.
Content TypeSelectNoResponse content type: JSON, HTML, Plain Text, or XML. Defaults to JSON (application/json).
Response HeadersKey/Value listNoAdditional response headers. Values support template variables.
Response BodyText (variable)NoThe response body content. Supports template variables. For JSON responses, ensure the body is valid JSON.

Content Type Options

LabelValue
JSONapplication/json
HTMLtext/html
Plain Texttext/plain
XMLapplication/xml

Output

FieldTypeDescription
statusCodenumberThe status code that was sent in the response.
contentTypestringThe content type that was sent in the response.

Example

A workflow that validates an incoming webhook payload and returns a structured JSON response:

  1. Webhook Listener -- Path: validate-order, Method: POST, Response Mode: Wait for Completion.
  2. If/Else -- Check that webhookTrigger_1.body.orderId is not empty.
  3. HTTP Request (true branch) -- Fetch order details from a backend API.
  4. Webhook Response (after HTTP Request) -- Status: 200, Body:
{"status": "ok", "order": "{{httpRequest_1.body}}"}
  1. Webhook Response (false branch) -- Status: 400, Body:
{"status": "error", "message": "Missing orderId"}

Response headers are sanitized to prevent CRLF injection. All header values have carriage return and newline characters stripped automatically.

On this page

Webhook Response | Buildorado