Actions13
Overview
The "Budibase DB" node allows interaction with the Budibase Database Public API. Specifically, the "Get Row" operation retrieves a single row from a specified table within a Budibase app database. This is useful when you need to fetch detailed data for a particular record by its unique identifier.
Common scenarios include:
- Fetching user details or configuration settings stored in a Budibase table.
- Retrieving a specific item or entity's data for further processing or conditional logic in an automation workflow.
- Integrating Budibase data retrieval into larger workflows that require dynamic access to database rows.
Example: You have a Budibase app managing customer orders and want to retrieve the details of a specific order by its row ID to send a notification or update another system.
Properties
Name | Meaning |
---|---|
Table ID | The unique identifier of the table from which to get the row. |
Row ID | The unique identifier of the row to retrieve from the specified table. |
Output
The node outputs JSON data representing the retrieved row from the Budibase table. The structure corresponds directly to the columns and values of the row identified by the given Row ID in the specified Table ID.
If the row exists, the output json
field contains the full data object of that row. If no row is found or an error occurs, the output may be empty or contain error information depending on the API response.
This node does not output binary data.
Dependencies
- Requires connection to the Budibase Public API.
- Needs an API authentication token credential configured in n8n to authorize requests.
- The base URL for API requests is taken from the domain specified in the credentials.
Troubleshooting
- Missing or incorrect Table ID or Row ID: The node will fail to retrieve data if these IDs are invalid or missing. Ensure they are correctly set.
- Authentication errors: If the API key or domain is misconfigured, the node will return authorization errors. Verify credentials are correct and have necessary permissions.
- Row not found: If the specified Row ID does not exist in the table, the output will be empty or indicate no data found.
- API connectivity issues: Network problems or incorrect base URL can cause request failures. Check network access and credential domain setting.
Links and References
- Budibase Documentation
- Budibase Public API Reference (for detailed API endpoints and payloads)