Overview
The node is a trigger for Baserow, a no-code database platform. It activates workflows when specific events occur in a Baserow database table, such as rows being created, updated, or deleted. This node is useful for automating processes that depend on changes in your Baserow data, like syncing data to other systems, sending notifications, or updating dashboards.
For example, you can use this node to start a workflow whenever a new row is added to a sales leads table, enabling automatic follow-up emails. Another scenario is triggering a workflow when a row is updated to reflect status changes, allowing real-time updates in connected applications.
The node also supports filtering triggers based on field values and operations (e.g., equal to a value), so workflows only run when certain conditions are met.
Properties
| Name | Meaning |
|---|---|
| Database Name or ID | Select the Baserow database to monitor. You can choose from a list or specify an ID via expression. |
| Table Name or ID | Select the table within the chosen database to watch for events. Options depend on the selected database. |
| Events | Choose one or more events to listen for: "Rows Created", "Rows Deleted", and/or "Rows Updated". The workflow triggers when any of these events occur. |
| Enable Filter | Boolean toggle to enable or disable filtering of events based on field conditions. If disabled, all matching events trigger the workflow. |
| Field Name or ID | When filtering is enabled, select the specific field to apply the condition on. Options depend on the selected table. |
| Operation | The comparison operation to apply on the selected field's value. Available options: Contains, Equal, Exists, Not Contains, Not Equal, Not Exists. Default is Equal. |
| Value Name or ID | The value to compare the field against when filtering is enabled and the operation requires a value (not used with Exists/Not Exists). Options depend on the selected field and table. |
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.
- The main output is a JSON array with one item containing the full event data.
- If filtering is enabled, only events where at least one row matches the filter condition will trigger the workflow.
- If no rows match the filter, the workflow does not execute further.
- The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the Baserow API.
- Needs network access to Baserow's API endpoints.
- The node uses webhooks, so n8n must be accessible via a public URL or tunnel (cannot run on localhost without tunneling).
- The node dynamically loads options for databases, tables, fields, and field values by calling Baserow API endpoints.
Troubleshooting
- Webhook creation failure: If the webhook cannot be created, ensure the node has a valid public URL (not localhost) and the API key has sufficient permissions.
- Filter misconfiguration: If filtering is enabled but no events trigger, verify the field, operation, and value settings match the actual data.
- API errors: Errors from Baserow API calls may indicate invalid credentials or network issues.
- No events firing: Confirm that the selected events are enabled in Baserow and that the webhook exists.
- "Error Loading Values": This message appears if fetching field values fails; check API connectivity and permissions.