Overview
The "Record - Get" operation in this Cubable node retrieves a single record from a specified table within a Cubable base. This is useful when you need to fetch detailed information about one specific entry, for example, to display it, process it further, or use it as input for subsequent workflow steps.
Common scenarios include:
- Fetching a customer record by its unique ID to update or analyze.
- Retrieving a product's details before performing inventory checks.
- Accessing a specific data entry for reporting or validation purposes.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Cubable API; currently supports "Access Token". |
| Base | The Cubable base (database) where the target table resides. Can be selected from a list or specified by its Base ID. |
| Table | The table within the selected base containing the record. Selectable from a list or by Table ID. |
| Record ID | Unique identifier of the record to retrieve. Required to specify exactly which record to get. |
| Options | Additional options affecting output: |
| - Output Custom Fields | Select which custom fields to include in the output. |
| - Expand Custom Fields | Whether nested custom fields should be flattened in the output (default: true). |
| - Return by Custom Field ID | Whether to return custom fields keyed by their field IDs instead of names (default: true). |
Output
The node outputs JSON data representing the requested record. The structure includes standard fields and optionally custom fields based on the selected options. If enabled, nested custom fields are flattened for easier access. Custom fields can be returned keyed either by their field IDs or by their names.
No binary data output is indicated for this operation.
Dependencies
- Requires an API authentication token (access token) to connect to Cubable.
- Needs proper configuration of the Cubable base and table identifiers.
- The node depends on Cubable’s REST API endpoints to fetch record data.
Troubleshooting
- Invalid Base or Table ID: Errors may occur if the provided Base or Table ID does not match the expected format or does not exist. Ensure IDs conform to the regex pattern and are correct.
- Record Not Found: If the Record ID does not exist in the specified table, the node will likely throw an error or return no data. Verify the Record ID is accurate.
- Authentication Failures: Missing or invalid access tokens will prevent successful API calls. Confirm that the API key credential is correctly set up.
- Custom Fields Loading Issues: If custom fields are selected but do not appear, check that the base and table support those fields and that the options are configured properly.
Links and References
- Cubable API Documentation (for API details and authentication)
- n8n Documentation on Resource Locators (explains how resource locators work in nodes)