Workflow blocks
HTTP Response
Sends a structured HTTP reply (body, status, headers) back to the caller. Use as the final step of an API-triggered workflow.
system/response — Sends a structured HTTP reply (body, status, headers) back to the caller. Use as the final step of an API-triggered workflow.
Where it appears
The HTTP Response block lives in the Logic & control group of the Workflow Builder.
Fields
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
data | code | Yes | — | JSON response body. Use <nodeId:Label.field> to inject values from previous nodes. |
status | text | No | 200 | HTTP status code (default: 200) |
headers | code | No | — | Additional HTTP headers to include in the response |
Inputs and outputs
Inputs are the configurable fields above. The block produces these outputs:
Outputs
Reference an output downstream with <HTTP Response.field>.
| Name | Type | Description |
|---|---|---|
data | json | Response body |
status | number | HTTP status code |
headers | json | Response headers |
success | boolean | Whether the response was formatted successfully |
error | string | Error message if formatting failed |
Example
A minimal configuration for this block:
{
"type": "system/response",
"config": {
"data": "...",
"status": "200"
}
}Limits and failure modes
- Required field (
data) must be set, or the block fails validation before it runs. - On failure the
erroroutput is populated; downstream blocks that reference other outputs may not receive values.