Skip to main content

​
API Response Node

The API Response Node is responsible for sending the final HTTP response back to the client. It marks the end of workflow execution.
Once this node runs, no further nodes are executed. Every workflow that exposes an API must end with exactly one API Response Node.

​
What the API Response Node Does

The API Response Node is responsible for:
  • Defining the HTTP status code
  • Sending the final response to the client
  • Ending workflow execution
It acts like a res.send() or return Response() in traditional backend frameworks.
Response

​
Configuration Fields

​
Status

The Status field defines the HTTP status code returned to the client. You can select from standard HTTP response codes.

​
Common Status Codes

Status CodeMeaning
200 OKRequest successful
201 CreatedResource created
204 No ContentSuccess with no response body
400 Bad RequestClient-side error
401 UnauthorizedAuthentication required
403 ForbiddenAccess denied
404 Not FoundResource not found
500 Internal Server ErrorServer error

​
How Response Data Works

The API Response Node sends the final output of the workflow. The response body is typically constructed using:
  • Data from previous nodes
  • Logic or transformations
  • Database query results
Once this node executes:
  • The response is returned to the client
  • Workflow execution stops immediately

​
Example: Success Response

​
Configuration

Status: 200 OK

​
Response Body

{
  "success": true,
  "message": "User created successfully"
}

​
Example: Error Response

​
Configuration

Status: 400 Bad Request

​
Response Body

{
  "success": false,
  "error": "Invalid input data"
}