abort node immediately stops flow execution and returns an error response to the client. Use it when you encounter critical errors that should halt processing.
Configuration
Config Fields
Response Behavior
The abort node generates a response based on configuration:- If
bodyis provided, it becomes the response body - If only
messageis provided, response is{ "error": "<message>" } - If neither is provided, response is
{ "error": "Request aborted" }
Examples
Simple Error Message
Custom Error Body
Not Found Error
Unauthorized Error
Dynamic Error Message
Common Use Cases
After Failed Validation
Rate Limit Exceeded
Missing Required Resource
vs Response Node
Use
abort for unexpected errors that should stop processing. Use response for normal flow completion, including handled error responses.
Common Status Codes
Related
- Response Node - Normal flow termination
- Condition Node - Branch to abort on errors
- Try Node - Handle errors gracefully