# Webhook response - Workflow node | Docs - nodulz

Source: https://nodulz.com/docs/nodes/webhook_response

Language: en

Builds the JSON body returned to the webhook HTTP caller.

## Usage and specifics

Select this node in the Webhook trigger response settings. The template builds the JSON body and statusCode sets the HTTP status.

Technical type : `webhook_response`. Runtime : `nodulz`.

## Credentials and prerequisites

This node defines no dedicated external credential. Remote sources or execution targets may still need their own access credentials.

See the [credentials guide](/docs/credentials) if a remote source or execution target requires access.

## Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

| Parameter | Type | Default | Values / limits |
| --- | --- | --- | --- |
| `responseTemplate` | `string` | `"{\n  \"data\": \"{{ nodes.http1.body.data }}\",\n  \"request\": \"{{ input.body }}\"\n}"` | - |
| `statusCode` | `string` | `"200"` | - |

## Configuration help

| Setting | Purpose and guidance |
| --- | --- |
| `statusCode`<br>HTTP status code | Status sent to the caller (200, 201, 400, 404, 422, 500…). Fixed number or JavaScript expression in double curly braces. |
| `responseTemplate`<br>Response JSON template | JSON returned to the HTTP caller. Use JavaScript expressions inside strings with double curly braces. Each {{ … }} value is resolved from input, nodes.http1, nodes.set1, or vars. |

## Examples

- Response: JSON template combining input.body and nodes.http1.body.data
- Each {{ … }} value is resolved from input, nodes.http1, nodes.set1, or vars.

## Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

```json
{
  "responseTemplate": "{\n  \"data\": \"{{ nodes.http1.body.data }}\",\n  \"request\": \"{{ input.body }}\"\n}",
  "statusCode": "200"
}
```

## Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.

See also : [Expressions and data](/docs/expressions), [Executions](/docs/executions), [Node catalog](/docs/nodes).

## Explore further

- [Features - nodulz](https://nodulz.com/product/overview)
- [Node catalog - nodulz](https://nodulz.com/product/catalog)
- [MCP server - nodulz](https://nodulz.com/product/mcp)
- [Pricing - nodulz](https://nodulz.com/pricing)
- [Use cases and workflow automation - nodulz](https://nodulz.com/use-cases)
- [Choose what your workflows can do. - nodulz](https://nodulz.com/compare)
- [Documentation - nodulz](https://nodulz.com/docs)