Overview
This node integrates with Cubable, a platform for managing structured data bases (called "Bases") and tables within them. The "Record" resource with the "Create or Update" operation allows users to either create new records or update existing ones in a specified table of a Cubable Base.
Typical use cases include:
- Synchronizing external data sources into Cubable by upserting records.
- Automating data entry workflows where records need to be created if they don't exist or updated if they do.
- Maintaining up-to-date datasets in Cubable from other systems without manual intervention.
For example, you might use this node to automatically add or update customer information in a Cubable table whenever a new order is received in your e-commerce system.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Cubable API. Currently supports using an Access Token. |
| Base | The Cubable Base where the target table resides. Can be selected from a list of available Bases or specified by its unique Base ID. |
| Table | The specific table within the selected Base where the record will be created or updated. Can be selected from a list or specified by its Table ID. |
| Fields | Mapping of input data fields to the Cubable table fields. Supports defining which fields to set or update on the record. This mapping can be defined manually or auto-mapped based on input data. |
| Ignore Fields From Input | List of field names to ignore when updating records. Useful to prevent overwriting certain fields during an update operation. |
Output
The node outputs JSON data representing the result of the create or update operation on the Cubable record. This typically includes the full record data as stored in Cubable after the operation, including any generated IDs or timestamps.
If binary data were involved (not indicated here), it would represent file attachments or similar content related to the record, but this node focuses on structured JSON record data.
Dependencies
- Requires an API access token credential for authenticating requests to the Cubable API.
- Needs network connectivity to Cubable's service endpoints.
- The node depends on Cubable's API being available and responsive.
- No additional environment variables are explicitly required beyond the authentication token.
Troubleshooting
- Invalid Base or Table ID: If the provided Base or Table ID does not match the expected pattern or does not exist, the node will fail. Ensure IDs are correct and accessible with the given credentials.
- Authentication Errors: Using an invalid or expired access token will cause authentication failures. Verify that the token is valid and has sufficient permissions.
- Field Mapping Issues: Incorrect or missing field mappings may cause errors or incomplete updates. Double-check that all required fields are mapped correctly.
- Ignoring Fields: If some fields are unexpectedly not updated, verify whether they are included in the "Ignore Fields From Input" property.
- API Rate Limits or Downtime: Temporary failures may occur due to API rate limits or service outages. Retrying after some time or checking Cubable's status page can help.
Links and References
- Cubable Official Website — For general product information.
- Cubable API Documentation — Detailed API reference for developers.
- n8n Documentation on Creating Custom Nodes — For understanding how nodes like this are implemented.