Skip to main content

Response Node

What it does​

Builds and sends the final HTTP response to the caller, ending request processing for that execution path.

Inputs/config​

  • HTTP status code (static or expression).
  • Response headers map.
  • Response body payload (raw or expression-resolved object).

Outputs/branches​

  • Terminal behavior for HTTP flows.
  • No matched_output.
  • Downstream edges are typically unnecessary.

Example usage snippet​

{
  "id": "n3",
  "type": "response_node",
  "config": {
    "status": 200,
    "body": {
      "ok": true
    }
  }
}

Common pitfalls​

  • Leaving status unset and unintentionally returning default values.
  • Returning large debug payloads in production.
  • Continuing workflow edges after response and expecting client-visible effects.