Baserow Extended icon

Baserow Extended

Consume the Baserow API

Actions5

Row → Get

AI-generated

Overview

This node retrieves a single row from a specified table in a Baserow database using the "Get" operation. It is useful when you need to fetch detailed information about a specific record by its unique Row ID. Common scenarios include looking up user profiles, fetching configuration values, or retrieving any data entity stored in Baserow for use in subsequent workflow steps.

Example Use Cases:

  • Fetching a customer record by ID to send a personalized email.
  • Retrieving a product's details for inventory management.
  • Looking up a configuration row to drive conditional logic in your workflow.

Properties

Name Type Meaning
Database Name or ID options The Baserow database to operate on. You can select from a list or specify an ID directly (supports expressions).
Table Name or ID options The table within the selected database. You can select from a list or specify an ID directly (supports expressions).
Row ID string The unique identifier of the row to retrieve. This is required for the "Get" operation and determines which record will be fetched.

Output

The output is a JSON object representing the retrieved row. Each field in the row is included as a key-value pair, where keys are the human-readable field names (not internal IDs).

Example Output:

{
  "id": 123,
  "Name": "John Doe",
  "Email": "john@example.com",
  "Status": "Active"
}
  • All fields present in the Baserow row will appear as properties in the output JSON.
  • The structure dynamically matches the schema of the selected table.

Dependencies

  • External Service: Requires access to a Baserow instance.
  • API Key: Needs valid Baserow API credentials configured in n8n under the name baserowApi.
  • n8n Configuration: No special environment variables beyond standard credential setup.

Troubleshooting

Common Issues:

  • Invalid Database/Table/Row ID: If the provided IDs do not exist or are incorrect, the node will throw an error indicating that the resource was not found.
  • Authentication Errors: If the API credentials are missing or invalid, you may see errors related to authentication failure.
  • Permissions: The API user must have permission to read the specified database/table/row.

Error Messages & Resolutions:

  • "Row not found": Check that the Row ID exists in the specified table.
  • "Invalid credentials": Ensure the correct API key/token is set up in n8n credentials.
  • "Table not found" or "Database not found": Double-check the selected or entered IDs/names.

Links and References

Discussion