Overview
The Baserow Trigger node starts an n8n workflow when specific events occur in a Baserow database. It listens for changes such as rows being created, updated, or deleted in a specified table within a database. This trigger is useful for automating workflows that depend on real-time data changes in Baserow, such as syncing data to other systems, sending notifications, or updating dashboards.
A practical example: You want to send an email notification whenever a new row is added to a particular table in your Baserow database. By configuring this trigger to listen for "Rows Created" events on that table, the workflow will start automatically upon each new entry.
Additionally, the node supports filtering events based on field values and conditions, allowing workflows to trigger only when certain criteria are met (e.g., only when a status field contains "urgent").
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 table within the chosen database by name or ID to monitor for events. |
| 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 specific field conditions. When enabled, the workflow triggers only if the condition matches. |
| Field Name or ID | The field within the table to apply the filter condition on. Only shown if filtering is enabled. |
| Operation | The type of comparison operation to apply on the selected field's value. Options include: - Contains - Equal - Exists (field has any value) - Not Contains - Not Equal - Not Exists (empty) |
| Value Name or ID | The value to compare the field against, depending on the operation. Not applicable for "Exists" or "Not Exists" operations. |
Output
The node outputs JSON data representing the webhook payload received from Baserow when an event occurs. The structure includes details about the event type and the affected rows/items.
- The main output (
json) contains the full event data as received. - If filtering is enabled, only events matching the filter condition produce output; otherwise, the node returns an HTTP 200 OK response without triggering the workflow.
- No binary data output is produced by this node.
Example output snippet:
{
"event_type": "rows.created",
"items": [
{
"field_1": "value1",
"field_2": "value2"
}
]
}
Dependencies
- Requires an API key credential for authenticating with the Baserow API.
- Needs network access to the Baserow instance.
- The node creates and manages webhooks on Baserow tables to receive event notifications.
- The webhook URL must be publicly accessible (cannot be localhost); using a tunnel or custom domain is necessary.
Troubleshooting
- Webhook creation failure: If the webhook cannot be created, ensure the API credentials are valid and have permissions to manage webhooks on the target Baserow instance.
- Webhook URL issues: The webhook URL cannot be localhost. Use a public URL or tunneling service.
- Filter misconfiguration: If filtering is enabled but no events trigger the workflow, verify the field, operation, and value parameters match the actual data.
- Missing or invalid IDs: Selecting database, table, or field IDs incorrectly can cause errors or empty option lists.
- API rate limits or connectivity problems: Network issues or API limits may prevent webhook registration or event delivery.
Common error messages:
- "The webhook cannot work on 'localhost'. Please setup n8n on a custom domain or start with '--tunnel'!" — Fix by providing a public webhook URL.
- "Baserow webhook creation response did not contain the expected data." — Check API credentials and permissions.
- Errors loading options for databases, tables, fields, or values — Verify API connectivity and correct parameter dependencies.