Skip to main content

HTTP Response node

The HTTP Response node allows returning an HTTP response to the client that triggered the workflow (API route trigger type, including incoming webhooks configured on this type): returning data to the client, indicating the success or failure of an operation, returning appropriate HTTP status codes and sending custom headers.

Parameters​

ParameterTypeRequiredDefaultDescription
AppApp❌—Application associated with the node.
Status code200 / 201 / 400 / 401 / 404 / 500 / custom✅—HTTP code returned to the client.
HeadersKey-value❌—HTTP headers of the response. Support Handlebars variables.
BodyJSON❌—Response body returned to the client. Can be empty for certain status codes.

Status code​

Select the HTTP status code to return:

  • 200 OK: Success
  • 201 Created: Resource created
  • 400 Bad Request: Invalid request
  • 401 Unauthorized: Not authorized
  • 404 Not Found: Not found
  • 500 Internal Server Error: Server error
  • Or a custom code

Headers​

Add custom headers:

  • Key-value format
  • Supports Handlebars variables
  • Common headers: Content-Type, Location, X-Custom-Header

Example:

Content-Type: application/json
X-Request-ID: {{requestId}}

Body​

Response body:

  • JSON format (recommended)
  • Supports Handlebars variables
  • Can be empty for certain status codes

Example:

{
  "success": true,
  "data": {
    "orderId": "{{processedOrder.id}}",
    "status": "processed"
  },
  "message": "Order processed successfully"
}

Behavior​

A single HTTP Response node:

A workflow triggered by an API route trigger (API or incoming webhook) must contain only one HTTP Response node:

  • The first HTTP Response node encountered ends the workflow
  • The following nodes are not executed
  • The response is sent immediately

Workflow without response:

If no HTTP Response node is present:

  • The workflow ends without a response
  • The client receives a timeout or an error
  • Always use an HTTP Response node for API route triggers (API or webhook)

Input​

The node receives the workflow context data (API route trigger or previous nodes) and injects it into the response headers and body via Handlebars variables:

{
  "requestId": "req_7f3a",
  "processedOrder": {
    "id": "CMD-4821",
    "status": "processed"
  }
}

The response sent to the client uses these variables, for example X-Request-ID: {{requestId}} and "orderId": "{{processedOrder.id}}".

Output​

The HTTP Response node generates no context variable: it ends the workflow and returns the response to the client. Nothing can be consumed in the following nodes — always place it at the end of a branch.

Errors​

If no HTTP Response node is present in a workflow triggered by an API route, the workflow ends without a response and the client receives a timeout or an error. Always use an HTTP Response node for this trigger type.

Limits​

A workflow triggered by an API route trigger (API or incoming webhook) must contain only one HTTP Response node.

Example​

Answer a REST request:

  1. An API route trigger receives the client request.
  2. Nodes process the data (e.g. an HTTP(S) Request node or a Condition node).
  3. The HTTP Response node returns the status code, headers and body to the client — the first HTTP Response node encountered ends the workflow.

Create complete REST endpoints:

  • GET: retrieve data
  • POST: create resources
  • PUT: update
  • DELETE: delete

Answer a received webhook:

  • Confirm the reception
  • Return a processing status
  • Indicate the errors

See also​