Baserow Trigger icon

Baserow Trigger

Starts the workflow when Baserow events occur
Join our community

Actions6

Overview

This node acts as a trigger for workflows based on events occurring in Baserow, an online database/spreadsheet 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 a particular field's value meets certain conditions (e.g., contains or does not contain a specified text).

Common scenarios where this node is useful include:

  • Automating notifications or actions when new rows are added to a Baserow table.
  • Triggering data synchronization workflows when rows are updated or deleted.
  • Filtering triggers to only run workflows when specific field values meet criteria, e.g., only process rows where a "Status" field does not contain "Completed".

Example: A project management workflow that starts whenever a new task row is created in a Baserow table, but only if the "Priority" field does not contain "Low".

Properties

Name Meaning
Database Name or ID Select the Baserow database to monitor. Can be chosen from a list or specified via expression.
Table Name or ID Select the table within the database to monitor. Depends on the selected database.
Events Choose one or more events to listen for: Rows Created, Rows Deleted, Rows Updated.
Enable Filter Enable or disable filtering of events based on field conditions.
Field Name or ID When filtering is enabled, select the field to check against the condition.
Operation The condition operation to apply on the field value when filtering is enabled. Options include: Contains, Equal, Exists, Not Contains, Not Equal, Not Exists.
Value Name or ID The value to compare the field against for operations that require it (not used with Exists/Not Exists).

Output

The node outputs JSON data representing the webhook payload received from Baserow when an event occurs. This includes detailed information about the event type and the affected rows/items.

  • The output JSON structure corresponds directly to the webhook payload sent by Baserow.
  • If filtering is enabled, only events matching the filter condition will produce output.
  • If no items match the filter condition, the workflow execution is skipped.
  • 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 Baserow webhooks cannot work with localhost URLs.
  • Uses Baserow REST API endpoints to manage webhooks and load options dynamically (databases, tables, fields, field values).

Troubleshooting

  • Webhook creation failure: If the webhook URL is localhost or invalid, the node throws an error. Use a publicly accessible URL or a tunneling service.
  • Missing webhook data: If the webhook response lacks expected data (like webhook ID), the node raises an API error.
  • Filter misconfiguration: If filtering is enabled but no field is selected, the node logs a warning and executes the workflow without filtering.
  • No matching items: When filtering is active and no items satisfy the condition, the workflow does not execute further.
  • API errors: Network issues or invalid credentials will cause API request failures; verify API keys and network connectivity.

Links and References

Discussion