Cubable icon

Cubable

Read, update, write and delete data from Cubable

Actions6

Overview

This node integrates with Cubable, a data platform that allows users to manage bases, tables, and records. Specifically, the Record - Create operation enables users to add new records into a specified table within a Cubable base.

Typical use cases include:

  • Automating data entry by creating new records from workflow data.
  • Integrating external systems to push data into Cubable tables.
  • Building custom forms or applications that feed data directly into Cubable.

For example, you might use this node to create a new customer record in a CRM table whenever a form is submitted on your website.

Properties

Name Meaning
Authentication Method of authenticating with Cubable. Currently supports "Access Token" authentication.
Base The Cubable Base where the record will be created. Can be selected from a list of available bases or specified by its unique ID.
Table The specific table within the chosen base where the new record will be added. Can be selected from a list or specified by its unique ID.
Fields Mapping of fields and their values for the new record. Users can define these fields manually or map them from input data. Supports adding all fields or selecting specific ones.
Require Input by Field Config Boolean flag indicating whether to enforce input for fields marked as required in the Cubable configuration. If true, missing required fields will likely cause errors.
Ignore Fields From Input List of field names to ignore when mapping input data automatically. Useful when using auto-mapping mode to exclude certain fields from being set during record creation.

Output

The node outputs JSON data representing the newly created record in Cubable. This typically includes:

  • The unique identifier of the created record.
  • The values of the fields as stored in Cubable after creation.
  • Metadata related to the record (timestamps, creator info, etc., if provided by Cubable).

If the node supports binary data output (not indicated here), it would represent attachments or files associated with the record.

Dependencies

  • Requires an API key or access token credential for authenticating with Cubable.
  • Needs network access to Cubable's API endpoints.
  • The node depends on Cubable's API availability and correct configuration of bases and tables.
  • 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 correctly copied and valid.
  • Missing Required Fields: When Require Input by Field Config is enabled, omitting required fields will cause errors. Provide all mandatory fields as per Cubable's schema.
  • Authentication Errors: Invalid or expired access tokens will prevent the node from connecting. Verify the API key or token is current and has sufficient permissions.
  • Field Mapping Issues: Incorrect field names or types in the Fields property may cause the API to reject the request. Use the resource mapper to select valid fields.
  • Network or API Downtime: Temporary connectivity issues or Cubable service outages will result in execution failures. Retry later or check Cubable status.

Links and References

Discussion