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 apps, 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, triggering an email notification to the sales team. Another scenario is monitoring updates to inventory records and automatically adjusting stock levels in another system.
This particular operation "Not Equal" allows filtering the trigger so it only fires if a specified field's value does not equal a given value, providing more granular control over when the workflow runs.
Properties
| Name | Meaning |
|---|---|
| Database Name or ID | Select the Baserow database by name or ID where the table resides. You can choose from a list or specify dynamically via expression. |
| Table Name or ID | Select the table within the chosen database by name or ID. Options depend on the selected database. |
| Events | Choose one or more events to listen for: Rows Created, Rows Deleted, Rows Updated. The trigger will activate when any of these events occur. |
| Enable Filter | Boolean toggle to enable or disable filtering of events based on field values. If disabled, the workflow triggers on all matching events without further checks. |
| Field Name or ID | When filtering is enabled, select the specific field in the table to evaluate against the condition. |
| Operation | The comparison operation to apply on the field's value. For this node operation, "Not Equal" means the workflow triggers only if the field's value is different from the specified value. Other operations exist but are not relevant here. |
| Value Name or ID | The value to compare the field's content against. The filter passes if the field's value is not equal to this value. |
Output
- The node outputs JSON data representing the webhook payload received from Baserow.
- The JSON includes details about the event type, affected rows, and their fields.
- If filtering is enabled, only events passing the filter condition (field value not equal to the specified value) cause output.
- If no items meet the condition, the node does not trigger the workflow execution.
- No binary data output is involved.
Example output JSON structure (simplified):
{
"event_type": "rows.updated",
"items": [
{
"field_123": "some value",
"field_456": "another value"
}
],
"other_event_data": "..."
}
Dependencies
- Requires a valid API key credential for Baserow to authenticate API requests.
- Needs n8n to be accessible via a public URL or tunnel since Baserow webhooks cannot target localhost.
- Uses Baserow REST API endpoints to:
- Fetch databases, tables, fields, and field values for dynamic option loading.
- Create, check, and delete webhooks on the specified table.
- No additional external dependencies beyond the Baserow API and n8n environment.
Troubleshooting
- Webhook creation failure: If the webhook cannot be created, ensure the node has a valid API key and that the n8n instance is publicly accessible (not localhost).
- Filter not working as expected: Verify that the correct field, operation ("Not Equal"), and value are selected. Remember that the comparison is case-insensitive and trims whitespace.
- No workflow execution despite events: Check if filtering is enabled and whether the incoming data matches the filter condition. If no items satisfy the "Not Equal" condition, the workflow won't run.
- Error loading options: Dynamic dropdowns for databases, tables, fields, or values may fail if the API key lacks permissions or network issues occur.
- API errors with status 404: Usually indicate that the webhook was deleted externally; the node attempts to clean up its stored webhook ID in this case.