Appearance
Log
The Log action is a debugging and monitoring tool that outputs messages to the Logs tab
Configuration
Name: You can give your log action a name for better organization in your workflow. This is optional but helpful when managing multiple log actions.
Type
The log type determines how your message appears in the console:
Info— For standard log messagesVerbose— For detailed debugging informationWarning— For potential issues that need attentionError— For critical problems and errorsMessage— Enter the text you want to output to the console. This is required and can be a static message or a dynamic value from your workflow.Data to display— Optionally include additional data alongside your message. This could be variable values, API responses, or any other data you need to monitor. The data can be input as JSON or JavaScript expressions.
Common applications
When building API Endpoints, you might use logs to track incoming request data, verify middleware logic, or monitor database query results. For example, placing a Log action at the start of your API Endpoint can confirm the request was received and show what input parameters were provided.
When debugging complex API Endpoints, logs help verify that actions are executing in the expected order and that variables contain the correct values at each step. They're particularly useful for tracking data transformations and catching potential issues before they cause problems.
In error scenarios, log actions can capture and display detailed error information, making it easier to identify and fix issues in your API Endpoints. Use them inside Try/Catch blocks to log error details before sending a response.
SERVER-SIDE LOGGING
Logs from API Endpoints appear in the server logs and the WeWeb debugger. Unlike interface workflows, API Endpoint logs are not visible to end users, making them ideal for logging sensitive debugging information.

