Output Node 📊
Displays a message, result, or data presentation to the user in a workflow.
Node type: outputNode
Category: Human
Actor: outputNode (2 threads)
Description​
The Output Node renders a visible message or data display to the user interacting with the workflow. It is used in chat-based workflows, public form workflows, and anywhere real-time feedback is needed during execution.
Output Nodes do not pause execution — they render the output and continue immediately to the next node.
Properties​
| Property | Type | Required | Description |
|---|---|---|---|
outputType | select | Yes | Visual style of the output |
prompt | textarea | Yes | Main content to display. Supports {varName} references |
title | text | No | Optional heading above the content |
data | json | No | Structured data to display (for message type) |
dataType | select | No | Format for data: json, table, list |
dismissible | checkbox | No | Whether the user can dismiss the output (default: false) |
duration | number | No | Auto-dismiss after this many seconds (0 = stays until dismissed) |
Output Types​
| Type | Appearance | Use Case |
|---|---|---|
info | Blue information panel | Informational messages, status updates |
success | Green success panel | Confirmation messages, completion notices |
warning | Yellow warning panel | Caution messages, partial results |
error | Red error panel | Error messages, validation failures |
message | Chat message bubble | Conversational responses, AI-generated text |
Inputs​
prompt and title support full {varName} substitution:
outputType: success
title: Order Confirmed!
prompt: Thank you {customerName}! Your order #{orderId} for ${orderTotal} has been confirmed.
Estimated delivery: {estimatedDelivery}
Outputs​
The Output Node does not set any workflow variables. Execution continues immediately after the output is rendered.
Connections​
| Connection | Description |
|---|---|
sequenceFlow (incoming) | Arrives from previous node |
sequenceFlow (outgoing) | Continues immediately after rendering |
Example: Success Confirmation​
{
"nodeId": "confirm-output-1",
"name": "Order Confirmation",
"nodeType": "outputNode",
"properties": {
"outputType": "success",
"title": "✓ Order Placed Successfully",
"prompt": "Hi {customerName}, your order #{orderId} has been placed! You'll receive a confirmation email at {customerEmail} within the next few minutes.",
"dismissible": true
}
}
Example: AI Response Display​
{
"nodeId": "ai-response-display",
"name": "Display AI Answer",
"nodeType": "outputNode",
"properties": {
"outputType": "message",
"prompt": "{aiResponse}",
"data": "{supportLinks}",
"dataType": "list"
}
}
This renders the AI Task's response as a chat message, with a list of related support links below it.
Auto-Dismiss Pattern​
For non-blocking notifications in long workflows:
{
"outputType": "info",
"prompt": "Processing your request, please wait...",
"dismissible": false,
"duration": 3
}
The message auto-dismisses after 3 seconds and the workflow continues.
Best Practices​
- Use
messagetype for conversational AI workflows — it renders inside the chat interface naturally - Use
success,warning,errortypes for form-based workflows where users expect a status response - Always include the user's name (
{customerName}) and relevant reference numbers ({orderId},{ticketId}) in confirmations - For long AI responses, use
messagetype — it handles multi-paragraph text better thaninfo/successpanels - Pair Output Nodes with Input Nodes to create interactive multi-step workflows (display result → collect next input)