BaserowAdvanced icon

BaserowAdvanced

Consume the Baserow API
Join our community

Actions5

Overview

The BaserowAdvanced node for n8n allows you to interact with the Baserow API, specifically to retrieve a single row from a specified table within a database. This is useful when you need to fetch detailed information about a specific record in your Baserow workspace and use that data in subsequent workflow steps.

Common scenarios:

  • Fetching a user's details by their unique ID for further processing.
  • Retrieving a product or order record to enrich or validate data in an automation.
  • Looking up configuration or reference data stored in Baserow for use in other systems.

Example:
You have a table of customers in Baserow and want to get all information about a customer with a known Row ID to send them a personalized email.

Properties

Name Meaning
Database Name or ID Database to operate on. Choose from the list, or specify an ID using an expression.
Table Name or ID Table to operate on. Choose from the list, or specify an ID using an expression. The available tables depend on the selected database.
Row ID ID of the row to return. This uniquely identifies the record you wish to retrieve from the selected table.

Output

  • The output will be a JSON object representing the requested row.
  • All fields from the row are included, with field names mapped to their human-readable names (not internal IDs).
  • Example output structure:
{
  "id": 123,
  "Name": "John Doe",
  "Email": "john@example.com",
  "Status": "Active"
}
  • If the operation is successful, only the row's data is returned.
  • No binary data is produced by this operation.

Dependencies

  • External Service: Requires access to a Baserow instance.
  • API Key: You must provide valid Baserow API credentials via n8n's credential system (baserowApi).
  • n8n Configuration: No special environment variables required beyond standard credential setup.

Troubleshooting

Common issues:

  • Invalid Database/Table/Row ID: If any of these IDs are incorrect or do not exist, the node will throw an error indicating the resource was not found.
  • Authentication errors: If the provided API credentials are invalid or expired, you may receive authentication or authorization errors.
  • Permission denied: If the user associated with the API key does not have access to the specified database/table/row, the request will fail.

Error messages and resolutions:

  • "Not found" or 404: Check that the Database, Table, and Row IDs are correct and exist in your Baserow instance.
  • "Invalid credentials" or 401: Ensure your Baserow API credentials are correctly configured in n8n.
  • "Permission denied" or 403: Verify that your API user has sufficient permissions for the target database/table/row.

Links and References

Discussion