Overview
The Cubable node allows users to interact with Cubable data tables by reading, updating, writing, and deleting records. Specifically, the Record - Update operation enables updating existing records in a specified table within a Cubable base. This is useful for automating data modifications, synchronizing external data sources, or managing records programmatically.
Typical use cases include:
- Updating customer information in a CRM table.
- Modifying inventory quantities in a stock management table.
- Correcting or enriching data fields based on external triggers or workflows.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating API requests. Currently supports "Access Token" authentication via an API token credential. |
| Base | The Cubable Base where the target table resides. Can be selected from a list of available bases or specified directly by its Base ID (validated against Cubable's ID format). |
| Table | The specific table within the selected Base to update records in. Can be chosen from a list filtered by the selected Base or specified by Table ID (also validated). |
| Fields | Defines which fields of the record to update and their new values. Supports manual mapping or automatic input data mapping. Required for the update operation. |
| Ignore Fields From Input | A list of field names to exclude from the input data when performing automatic mapping during updates. Useful to prevent overwriting certain fields unintentionally. Only applicable when using auto-mapping mode for fields. |
Output
The node outputs JSON data representing the updated record(s) after the operation completes. The structure typically includes the record ID and the updated field values reflecting the changes made.
If binary data were involved (not indicated here), it would represent file attachments or media linked to the record, but this node focuses on JSON record data only.
Dependencies
- Requires an API key credential for authenticating requests to Cubable.
- Needs access to Cubable's REST API endpoints for Bases, Tables, and Records.
- The node depends on internal methods for searching and loading options dynamically based on user selections (e.g., listing available Bases and Tables).
- No additional external libraries beyond those bundled with the node are required.
Troubleshooting
- Invalid Base or Table ID: If the provided Base or Table ID does not match the expected pattern, the node will reject the input. Ensure IDs conform to the regex pattern
[0-7][0-9A-HJKMNP-TV-Z]{25}. - Authentication Errors: Failure to authenticate usually means the API token is missing, expired, or incorrect. Verify the API key credential configuration.
- Field Mapping Issues: When using automatic field mapping, ensure that the input data contains all required fields and that any fields listed in "Ignore Fields From Input" are correctly specified to avoid unintended omissions.
- API Rate Limits or Network Issues: As with any API integration, network failures or rate limiting can cause errors. Retrying or checking API usage limits may resolve these issues.
Links and References
- Cubable Official Documentation (for API details and authentication)
- n8n Resource Locator Documentation (explains resource locator UI components used for Base and Table selection)
- Regex Tester (to validate Base/Table ID patterns)