The END node is the exit point of every flow. It defines what data the flow returns to callers.Documentation Index
Fetch the complete documentation index at: https://hypha-docs.plinqx.app/llms.txt
Use this file to discover all available pages before exploring further.
Overview
The END node:- Defines Output Schema: JSON Schema specifying return structure
- Returns Data: What the flow returns to callers
- Validates Output: Ensures return data matches the schema
- Completes Flow: Signals successful flow completion
Output Schema
The output schema defines what data your flow returns:- JSON Schema Format: Standard JSON Schema specification
- Type Validation: Validates return types
- Structure: Defines the shape of returned data
Example Output Schema
Return Value
The END node returns data from flow execution:- Expression-Based: Use expressions to construct return value
- Variable References: Reference data from any previous node
- Transformations: Apply transformations before returning
Example Return Value
Response Modes
Sync Mode
For sync flows (webhook triggers with sync mode):- Immediate Return: Returns data directly to caller
- Timeout: Must complete within timeout window
- Use Case: When caller needs immediate result
Async Mode
For async flows:- Acknowledgment: Returns acknowledgment immediately
- Result Available: Result available via flow run API
- Use Case: Long-running flows, fire-and-forget
Error Handling
If flow execution fails before reaching END:- Error Response: Error details returned to caller
- No Output: END node output not returned
- Error Logging: Errors logged in flow execution history
Best Practices
Consistent Structure
Use consistent output structure across flows
Include Status
Always include success/status indicators
Error Details
Include error details when applicable
Document Schema
Document output schema clearly
Next Steps
START Node
Learn about flow input
Transform Node
Transform data before returning