Cubable

Read, update, write and delete data from Cubable

Actions6

Record Actions

Overview

The Cubable node allows users to interact with Cubable, a data platform for managing and manipulating structured data. Specifically, the Record - Search operation enables searching for records within a specified base, table, and optionally a view in Cubable. This operation is useful when you want to retrieve filtered or specific sets of records from your Cubable database.

Common scenarios include:

Fetching all records or a limited number of records from a particular table.
Searching records based on views that apply filters or sorting.
Extracting custom fields data from records for further processing or integration.

Practical example:

A user wants to pull all customer records from a "Customers" table in a specific Cubable base to sync with another CRM system.
Another use case is retrieving only records visible in a certain view that filters active projects.

Properties

Name	Meaning
Authentication	Method of authenticating with Cubable API. Currently supports "Access Token".
Base	The Cubable Base to search records in. Can be selected from a list or provided by ID.
Table	The Table within the selected Base where records will be searched. Can be selected from a list or provided by ID.
View	(Optional) The View within the Table to filter/search records. Can be selected from a list or provided by ID.
Return All	Boolean flag indicating whether to return all matching records or limit the results.
Limit	Maximum number of records to return if "Return All" is false. Minimum value is 1.
Options	Additional options affecting output:
- Output Custom Fields	Select which custom fields to include in the output.
- Expand Custom Fields	Whether to flatten nested custom fields into a flat structure in the output. Defaults to true.
- Return by Custom Field ID	Whether to return custom fields keyed by their field IDs instead of names. Defaults to true.

Output

The node outputs JSON data representing the records retrieved from Cubable. Each record includes standard fields and optionally custom fields as configured by the options.

The json output contains an array of record objects.
Custom fields can be included and either expanded into a flat structure or kept nested.
Custom fields can be keyed by their field IDs or by their names depending on configuration.
No binary data output is indicated for this operation.

Dependencies

Requires an API authentication token (access token) for Cubable.
Needs proper configuration of the Cubable credentials in n8n.
Depends on Cubable API availability and correct Base/Table/View IDs.

Troubleshooting

Invalid Base/Table/View ID error: Ensure the IDs match the required regex pattern and exist in your Cubable account.
Authentication failures: Verify that the access token is valid and has sufficient permissions.
Empty results: Check if the selected view or table actually contains records; also verify filtering options.
Limit ignored when Return All is true: This is expected behavior; set Return All to false to enforce limits.
Custom fields not appearing: Confirm that the fields are selected in "Output Custom Fields" and that the base/table selections are correct.