Overview
The Return Node allows you to control exactly what data gets sent back to your frontend or calling system when the workflow completes. Use it when you need to format, transform, or customize the response from your workflow.
One per flow: Each connected flow can only have one Return node to avoid conflicts.
Required Configuration
- Label - Display name for the node
- Response Type - How to format the return data:
- All Items - Return complete data from previous node (most common)
- Text - Return specific data or transformed results
- Redirect - Redirect to a URL
- No Data - Return empty response for side-effect operations
Optional Configuration
- Requires Auth - Whether this node needs user authentication (default: false)
Response Type Details
All Items (Most Common)
- Returns the complete result from the previous node
- Perfect for queries, mutations, and API responses
- No additional configuration needed
- Use this when you want to pass through all the data
Text
- Return custom or transformed data
- Requires Response Value and Value Mode:
- Fixed - Static text, numbers, or JSON objects
- Args - Reference specific fields from previous nodes
- Expression - JavaScript expressions for data transformation
Redirect
- Navigate to a different URL after workflow completion
- Requires Redirect URL
- Perfect for post-form submissions or payment flows
No Data
- Empty response for operations that don’t need to return data
- Used for background tasks or simple confirmations
Connections
Return nodes are workflow endpoints:
Input from: Any node type
Output to: None - Return nodes end the workflow
Common Use Cases
Data Retrieval - Return query results or fetched information using “All Items”
Operation Results - Return mutation outcomes (created, updated, deleted records) using “All Items”
Custom Responses - Return formatted messages, status updates, or transformed data using “Text”
Post-Action Navigation - Redirect users after successful operations using “Redirect”
Background Tasks - Signal completion without data using “No Data”
Example Workflows
- User List: Frontend → Query Users → Return (All Items)
- Create User: Frontend → Mutation → Return (All Items)
- Custom Message: Frontend → Process → Return (Text: “Operation successful”)
- After Payment: Frontend → Payment → Return (Redirect: “/success”)
Expression Examples
When using Text response type with Expression mode:
// Return just the names from a list
${__full_result__}.map(item => item.name)
// Count active items
${__full_result__}.filter(x => x.active).length
// Create summary object
({
total: ${__full_result__}.length,
items: ${__full_result__}.map(x => x.title)
})
// Get first item's specific field
${__full_result__}[0].email
