Actions13
Table → Create a Table
AI-generatedOverview
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 column constraints like uniqueness or visibility for app workflows.
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 context about the table. |
| Columns | A collection of columns to define the table schema. Each column includes: - Column Name: Identifier for the column (required). - Label: Human-readable name (required). - Description: Details about the column (required). - Data Type: Specifies the type of data stored; options include Text, Number, Integer, Datetime, Boolean, Interval, Image, Color, User, File, Machine, Station, Linked Record. - Hidden: Boolean flag to hide the column. - Unique: Boolean flag to enforce unique values in the column. |
Output
The node outputs JSON data representing the newly created table object as returned by the Tulip API. This typically includes metadata about the table such as its ID, label, description, and detailed column definitions.
If the node supports binary data output, it would relate to file or image columns, but this operation primarily deals with table schema creation and thus does not output binary data.
Dependencies
- Requires an active connection to the Tulip API via an API key credential configured in n8n.
- The node depends on the Tulip platform being accessible and the API credentials having permissions to create tables.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
- Common issues:
- Missing required fields such as Label, Description, or any required column properties will cause validation errors.
- Incorrect data types or unsupported column configurations may result in API errors.
- Insufficient permissions on the API key can lead to authorization failures.
- Error messages:
- Validation errors indicating missing or invalid property values should be resolved by ensuring all required inputs are correctly filled.
- Authorization errors require checking the API key permissions and validity.
- Network or connectivity errors suggest verifying internet access and Tulip API endpoint availability.