Overview
The Baserow Trigger node listens for specific events occurring within a Baserow database and triggers an n8n workflow when those events happen. It is designed to monitor changes such as row creation, deletion, or updates, as well as table creation, deletion, or updates in a specified Baserow database.
This node is beneficial in scenarios where you want to automate processes based on data changes in Baserow without manual intervention. For example:
- Automatically sending notifications when a new row is added to a table.
- Syncing updated rows with another system.
- Logging deletions of tables or rows for audit purposes.
Properties
| Name | Meaning |
|---|---|
| Event | The type of event to listen for in Baserow. Options include: Row Created, Row Deleted, Row Updated, Table Created, Table Deleted, Table Updated. |
| Database | The Baserow database to monitor. Can be selected from a list or specified by ID. |
| Table | The Baserow table to monitor. Required only for row-related events (Row Created, Row Updated, Row Deleted). Can be selected from a list or specified by ID. |
| Include Previous Values | When monitoring row updates, whether to include the previous values of the row before the update occurred. |
| Enable Filters | Whether to enable filtering conditions on row created or updated events. |
| Filter | A collection of filter conditions applied when filters are enabled. Each filter includes: - Field Name or ID: The field to watch. - Condition: The condition to apply (e.g., Changed, Contains, Is Empty). - Value Name or ID: The value to compare against (not used for some conditions). |
Output
The node outputs JSON data representing the event details from Baserow. This typically includes information about the affected row or table depending on the event type. For example, for row events, the output contains the row data, and if "Include Previous Values" is enabled for updates, it also includes the prior state of the row.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Baserow API.
- Needs access to the Baserow service endpoint.
- The node uses internal helper methods to fetch databases, tables, fields, and select options dynamically for property selection.
Troubleshooting
Common Issues:
- Incorrect or missing API credentials will prevent the node from connecting to Baserow.
- Specifying a table when the event is a table-level event (e.g., Table Created) may cause confusion; table selection is only required for row events.
- Filters must be correctly configured; invalid field names or unsupported conditions can lead to no triggers firing.
Error Messages:
- Authentication errors usually indicate invalid or expired API keys.
- Resource not found errors may occur if the specified database or table ID does not exist or the user lacks permissions.
- If no events trigger, verify that the event type matches actual changes happening in Baserow and that filters (if enabled) are correctly set.
Links and References
- Baserow Official Documentation
- n8n Expressions Documentation (for using expressions in filter fields)