Overview
The node is a trigger for Baserow, a no-code database platform. It starts an n8n workflow when specific events occur in a Baserow table, such as rows being created, updated, or deleted. This node is useful for automating processes that depend on changes in a Baserow database, like syncing data to other systems, sending notifications, or updating dashboards.
For example:
- Trigger a workflow when new rows are added to a sales leads table to notify the sales team.
- Start a process when rows are updated to reflect changes in inventory levels.
- React to row deletions to clean up related records in another system.
It supports optional filtering so the workflow only triggers if certain field conditions are met, allowing more precise control over when automation runs.
Properties
| Name | Meaning |
|---|---|
| Database Name or ID | Select the Baserow database by name or ID where the table resides. |
| Table Name or ID | Select the specific table within the chosen database by name or ID to monitor for events. |
| Events | Choose one or more types of row events to listen for: - Rows Created - Rows Deleted - Rows Updated |
| Enable Filter | Enable or disable filtering to trigger the workflow only when specific field conditions are met. |
| Field Name or ID | When filtering is enabled, select the field to apply the condition on. |
| Operation | The condition operation to apply on the selected field (shown only if filtering is enabled): - Contains - Equal - Exists - Not Contains - Not Equal - Not Exists |
| Value Name or ID | The value to compare the field against for the condition (hidden if operation is "Exists" or "Not Exists"). |
Output
The node outputs JSON data representing the webhook payload received from Baserow when the specified event occurs. The output contains detailed information about the event, including the changed rows and their fields.
If filtering is enabled, the node only outputs data when the filter condition matches; otherwise, it skips execution.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Baserow API.
- Needs network access to Baserow's API endpoints.
- The node registers a webhook URL with Baserow to receive event notifications.
- The webhook URL must be publicly accessible (cannot be localhost) for Baserow to send events.
Troubleshooting
- Webhook creation failure: If the webhook cannot be created, ensure the node has a valid API key and the webhook URL is publicly reachable (not localhost).
- Filter not working as expected: Verify the correct field, operation, and value are selected. Check the field values in Baserow match the expected format and casing since comparisons are case-insensitive but exact.
- No workflow trigger despite events: Confirm the selected events match those occurring in Baserow. Also, check if filtering is enabled and conditions are too restrictive.
- Error "Baserow webhook creation response did not contain the expected data.": This indicates an unexpected API response; verify API credentials and permissions.
- Webhook deletion errors: Usually safe to ignore 404 errors indicating the webhook was already removed.