🇬🇧 EN

↩️ Webhook Response

Returns a custom HTTP response to the caller that initiated the workflow via a Webhook Trigger. Use this node when you want to send a meaningful response back to the webhook sender instead of the default empty 202 response. The workflow continues executing after the response is sent.

Category: Notifications & Messaging · Type identifier: webhook_response

Overview

When a workflow is triggered by a Webhook Trigger, Flusso normally returns a default 202 Accepted response immediately as the run is queued. The Webhook Response node lets you override this: it sends a custom response body, status code, and headers back to the caller at the point in the workflow where you place the node.

This is useful when the webhook sender expects a meaningful reply — for example, a payment provider expecting a 200 OK to acknowledge receipt, or an external system expecting a JSON object containing a processed result. Because the workflow continues executing after the response is dispatched, you can acknowledge the caller quickly and then carry on with slower asynchronous processing steps.

One response per workflow. Only one Webhook Response node should be placed per workflow. If you place it inside a branch, only the branch that executes will return a response.

Configuration

Field	Status	Description
Status Code	Required	HTTP status code to return, e.g. `200`, `201`, `400`. Default: `200`.
Body	Optional	The response body. Can be a JSON object, plain text, or `{{ variable }}` reference. Defaults to empty.
Content Type	Optional	The Content-Type header. Default: `application/json`.
Headers	Optional	Additional response headers as key-value pairs.

Output Data

After the response is dispatched, the following fields are available on the step output:

Field	Type	Description
`sent`	boolean	True once the response has been dispatched.
`status`	number	The status code that was sent.

Example Usage

Add a Webhook Trigger node as the workflow trigger. A payment provider will POST event data to this URL.
Add a Logic Gate node (step key: validate) that verifies the request signature from {{ trigger.output.headers.x-signature }}.
On the true branch, add a Webhook Response node. Set Status Code to 200 and Body to:
{ "received": true }
The payment provider receives an immediate acknowledgement.
Add further steps after the Webhook Response node to process the payment asynchronously — update the database, send a confirmation email, trigger downstream workflows — without keeping the payment provider waiting.

Tips & Notes

Place it early for acknowledgement patterns. If the caller only needs confirmation of receipt, place the Webhook Response node right after your validation step so the caller is not kept waiting while processing runs.
The workflow continues after response. Subsequent steps run normally after the response is sent. You can use this to run slow or resource-intensive steps without affecting the caller's experience.
Branched responses. If you use a Logic Gate before the Webhook Response node, you can return different status codes on different branches — for example 200 on success and 400 on validation failure.
Only works with Webhook Trigger. This node has no effect in workflows triggered by schedules, manual runs, event triggers, or other non-webhook triggers.

Related Nodes

Webhook Trigger — the trigger this node pairs with.
Logic Gate — validate the incoming request before sending a response.
Emit Event — hand off work to other workflows after acknowledging the caller.