Send response

Use the Send response action to define what your API Endpoint returns to the caller.

This is where you choose:

• The data to return (for example an object, a list of rows, or an error message).
• The status code (for example 200, 400, 401, 403, 404, 500).
• Optional headers (for example Content-Type).

Configuration

Setting	What it does
Response data	The data to return. You can bind this to results from previous actions.
Status code	The HTTP status code to return.
Headers	Optional headers to include in the response.
Continue workflow after response	If enabled, WeWeb will send the response immediately and keep running the remaining actions.

Example: return data on success

Use Send response after a table action to return the created or updated record.

Example pattern:

• Tables → Insert rows
• Send response With:
  • Status code: 200
  • Response data: The inserted row(s)

Example: return a clear error

If something is wrong (missing data, unauthorized user, etc.), send an error response and stop the workflow early.

Example pattern:

• True/False split (Check a condition)
• If not valid → Send response with:
  • Status code: 400
  • Response data: { "error": "Invalid inputs" }

Common pitfalls

The API Endpoint returns nothing

• Make sure you added a Send response action in your workflow.
• If you have multiple branches, make sure each branch returns a response.

The API Endpoint is slow even after returning a response

• If you do extra work after returning data (logging, notifications, etc.), consider enabling Continue workflow after response so the caller gets the response sooner.

CONTINUE LEARNING

Learn how to handle errors in your API Endpoints.

Error handling with Try/Catch →