---
title: Webhook Response Processor
slug: litmusedge/webhook-response-processor
docTags: 
createdAt: 2026-08-23T04:06:53.185Z
---

The Webhook Response Processor completes a synchronous Webhook flow and defines the HTTP response the hook returns to the caller. Place it at the end of a flow started by a [Webhook](docId\:Xoims-v81dAhH-PqKmBya) processor.

## Why use the Webhook Response Processor

Use this processor when a caller needs a specific status code, header, or response body back, rather than the default empty `200` returned by a Webhook processor.

## How it works

The response is built from the processor's configured `status_code`, `headers`, and `payload` fields. Each of these can be overridden by a matching flat field on the incoming message (`status_code`, `headers`, and `payload`). Message headers merge over the configured headers, with the message's value winning per key.

If nothing is set, the default response is an empty body with `200` status.

## Parameters

| **Parameter** | **Details**                                                                                                                                                  |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Status Code   | The HTTP status code to return to the caller. Overridden by a `status_code` field on the incoming message if present.                                        |
| Headers       | The response headers to return to the caller. Merged with a `headers` field on the incoming message if present. On a key conflict, the message's value wins. |
| Payload       | The response body to return to the caller. Overridden by a `payload` field on the incoming message if present.                                               |

## Related topics

- [Webhook](docId\:Xoims-v81dAhH-PqKmBya)
- [Add Processors and Processor Connections](docId\:v2ByHzigAaETGUWMInzdN)