Overview
This node acts as a trigger for workflows based on events occurring in Baserow, an online database platform. It listens to specific changes such as row creation, deletion, or updates within a selected table of a Baserow database. The node can optionally filter these events by checking if certain field values meet specified conditions before triggering the workflow.
Common scenarios include:
- Automating notifications or actions when new rows are added to a table.
- Triggering data synchronization processes when rows are updated or deleted.
- Filtering triggers to only respond when specific fields contain or do not contain certain values, or when fields exist or are empty.
For example, you could use this node to start a workflow that sends an email alert whenever a new customer record is created in a sales database, or only when the "Status" field equals "Pending".
Properties
| Name | Meaning |
|---|---|
| Database Name or ID | Select the Baserow database from which to listen for events. You can choose from a list or specify an ID via expression. |
| Table Name or ID | Select the table within the chosen database to monitor for events. Options depend on the selected database. |
| Events | Choose one or more event types to listen for: - Rows Created - Rows Deleted - Rows Updated |
| Enable Filter | Enable or disable filtering of events based on field conditions. When enabled, the node will only trigger if the specified condition is met. |
| Field Name or ID | (Shown if filtering enabled) Select the field to apply the filter condition on. |
| Operation | (Shown if filtering enabled) Choose the operation to apply for filtering: - Contains - Equal - Exists - Not Contains - Not Equal - Not Exists |
| Value Name or ID | (Shown if filtering enabled and operation is not "Exists" or "Not Exists") Select or specify the value to compare the field against in the filter condition. |
Output
The node outputs JSON data representing the webhook payload received from Baserow when the specified event occurs. This includes detailed information about the event type and the affected rows/items.
If filtering is enabled, only events matching the filter criteria will produce output; otherwise, all matching events trigger output.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Baserow API.
- Needs n8n to be accessible via a public URL or tunnel since the webhook cannot work on localhost.
- Uses Baserow REST API endpoints to manage webhooks and load options dynamically.
Troubleshooting
- Webhook on localhost error: The node throws an error if the webhook URL contains "localhost". To fix, run n8n with a tunnel or deploy it on a publicly accessible domain.
- Webhook creation failure: If the webhook creation response lacks expected data, verify API credentials and permissions.
- Filter misconfiguration: If no events trigger despite expected changes, check that the filter field, operation, and value are correctly set and correspond to actual data.
- API errors (404): If the webhook ID is invalid or deleted externally, the node attempts to clean up and recreate the webhook automatically.
- Loading options errors: If loading databases, tables, fields, or values fails, ensure the API credentials are valid and the Baserow instance is reachable.