Skip to main content
Version: V11

Output Node

The Output node defines the return value for HTTP-triggered workflow execution. It captures a value from the workflow and returns it as the HTTP response payload. Use this node as the terminal node in workflows initiated by the HTTP Trigger node.

How It Works​

The Output node receives data from upstream nodes and stores it as the workflow execution result. When the workflow completes, this value is returned to the calling HTTP client as the response body.

Unlike the Chat Output node which streams content to the chatbot interface, the Output node returns data programmatically to external systems. This enables API-style integrations where external applications invoke workflows and receive structured responses.

Configuration​

Value​

The value to return as the workflow execution output. Supports variable interpolation using ${variable} syntax to reference workflow variables.

PropertyValue
TypeAny
Input modesFixed, Expression
RequiredYes

Examples:

${processedResult}
{"status": "success", "data": ${analysisOutput}}

Output​

This node produces no downstream output. It stores the configured value as the final workflow result returned to the HTTP caller.

Execution Lifecycle​

PhaseBehavior
Pre-executionAwaits incoming data from upstream nodes
ExecutionResolves variable interpolation, stores value as workflow result
Post-executionCompletes workflow; value returned to HTTP caller

Usage Example​

HTTP API workflow:

HTTP Trigger → Data Processing → Large Language Model → Output

Webhook processing workflow:

HTTP Trigger → Validation → Vector Search → Output

The workflow receives an HTTP request, processes it through intermediate nodes, and returns the final value via the Output node.

Limitations​

  • Terminal node: Does not emit data to downstream nodes
  • HTTP workflows only: Designed for use with HTTP Trigger; use Chat Output for chatbot workflows
  • Single output: Returns one value per workflow execution

Best Practices​

  • Place the Output node at the end of HTTP-triggered workflows
  • Return structured data (JSON) for API integrations
  • Use meaningful variable references for clarity
  • Pair with HTTP Trigger node for complete request-response workflows
  • HTTP Trigger - Entry point for HTTP-triggered workflows
  • Chat Output - Stream content to chatbot interface instead of HTTP response
  • Data Transformation - Process data before returning via Output
  • Large Language Model - Generate AI responses to return via Output
Did you find this article helpful?