Baserow Trigger

Starts the workflow when Baserow events occur

Overview

The Baserow Trigger node for n8n starts workflows in response to specific events occurring in a Baserow database table. It listens for row-level changes—such as creation, deletion, or updates—in a specified table within a selected database. This node is particularly useful for automating processes that need to react instantly to data changes in Baserow, such as synchronizing records with other systems, sending notifications, or triggering downstream processing.

Example scenarios:

Automatically send an email when a new row is added to a Baserow table.
Sync deleted rows from Baserow to another application.
Update external dashboards when a record is updated in Baserow.

Properties

Name	Type	Meaning
Database Name or ID	options	The Baserow database to operate on. You can select from a list or specify the database ID directly using an expression.
Table Name or ID	options	The table within the selected database to monitor. You can select from a list (which depends on the chosen database) or specify the table ID directly using an expression.
Events	multiOptions	The types of row events to listen for. Options include "Rows Created", "Rows Deleted", and "Rows Updated". You can select one or more event types to trigger the workflow.

Output

The node outputs a JSON object containing the payload received from Baserow's webhook. The structure of this output will depend on the event type and the data sent by Baserow, but typically includes details about the affected row(s) and the action performed.

Example output structure:

{
  "hook_id": "string",
  "action": "rows.created" | "rows.deleted" | "rows.updated",
  "table_id": number,
  "row_ids": [number],
  "event_data": { ... }
}

hook_id: Identifier for the webhook.
action: The event type that triggered the webhook (e.g., "rows.created").
table_id: The ID of the table where the event occurred.
row_ids: Array of affected row IDs.
event_data: Additional event-specific data provided by Baserow.

If the incoming request only contains a hook_id and no action, the node responds with "OK" and does not trigger the workflow.

Dependencies

External Service: Requires access to a Baserow instance with API support.
API Key: Needs valid Baserow API credentials configured in n8n under the name baserowApi.
n8n Configuration: The webhook URL must be publicly accessible; it cannot work with localhost. Use a custom domain or start n8n with the --tunnel option for testing.

Troubleshooting

Webhook Not Working on Localhost:
Error: The Webhook can not work on "localhost". Please, either setup n8n on a custom domain or start with "--tunnel"!
Solution: Ensure your n8n instance is accessible from the internet. Use a tunnel (--tunnel) or deploy to a server with a public domain.
Webhook Creation Fails:
Error: Baserow webhook creation response did not contain the expected data.
Solution: Check your Baserow API credentials and ensure the table and database IDs are correct. Verify that your Baserow instance allows webhook creation.
404 Errors During Webhook Checks/Deletion:
These are handled gracefully, but if you see repeated failures, verify that the referenced webhook still exists in Baserow.