Actions13
Overview
This node allows users to create a new table within the Tulip platform by defining its label, description, and columns. It is useful for automating the setup of structured data storage in Tulip apps, enabling dynamic creation of tables that can store various types of data such as text, numbers, timestamps, images, and linked records.
Practical examples include:
- Automatically creating a custom data table to log production metrics.
- Defining a table schema on-the-fly based on user input or external data sources.
- Setting up tables with specific columns for inventory management or quality control processes.
Properties
| Name | Meaning |
|---|---|
| Label | The name of the table to be created. This is a required string that identifies the table. |
| Description | A textual description of the table's purpose or contents. This is a required string providing additional context about the table. |
| Columns | A collection of column definitions specifying the structure of the table. Each column includes: - Column Name: The internal name of the column (string, required). - Label: User-friendly label for the column (string, required). - Description: Explanation of the column's content (string, required). - Data Type: The type of data stored in the column. Options include Text, Number, Integer, Datetime, Boolean, Interval, Image, Color, User, File (File/Video), Machine, Station, Linked Record. - Hidden: Boolean flag indicating if the column should be hidden. - Unique: Boolean flag indicating if the column values must be unique. |
Output
The node outputs JSON data representing the newly created table object. This typically includes metadata about the table such as its ID, label, description, and the defined columns with their properties. The output does not include binary data.
Dependencies
- Requires an API key credential for authenticating with the Tulip API.
- The node depends on the Tulip platform's API being accessible and properly configured.
- No additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
- Missing Required Fields: Errors may occur if the Label, Description, or any required column fields are missing. Ensure all required inputs are provided.
- Invalid Data Types: Selecting unsupported or incorrect data types for columns could cause failures. Use only the supported data types listed.
- API Authentication Failures: If the API key credential is invalid or expired, the node will fail to connect. Verify the API key and permissions.
- Duplicate Column Names: Defining multiple columns with the same name might cause errors. Ensure each column name is unique.
- Network Issues: Connectivity problems with the Tulip API endpoint can result in timeouts or errors. Check network access and API availability.