Actions13
Table → Update a Table
AI-generatedOverview
This node allows you to update an existing Table in the Tulip platform. It is useful for managing and modifying table metadata such as the table's label, description, visibility (deleted status), and its columns' definitions. Typical use cases include synchronizing table schemas with external systems, updating column properties, or hiding tables from the UI without deleting them.
For example, you might use this node to:
- Rename a table or update its description to reflect new business requirements.
- Hide a table temporarily from the Tulip Tables UI by marking it as deleted.
- Modify the columns of a table by adding new columns, changing labels or descriptions, or setting columns as hidden or unique.
Properties
| Name | Meaning |
|---|---|
| Table Name or ID | Select the target table to update from a list or specify its ID using an expression. |
| Deleted | Boolean flag indicating whether the table should be hidden from the Tulip Tables UI. If not set, the table's current deleted status remains unchanged. |
| Label | The display name (label) of the table. |
| Description | A textual description of the table. |
| Columns | A collection of columns defining the table schema. Each column includes: - Column Name or ID: select or specify the column identifier. - Label: the display name of the column. - Description: details about the column. - Data Type: the type of data stored in the column. Options include Text, Number, Integer, Datetime, Boolean, Interval, Image, Color, User, File, Machine, Station, Linked Record. - Hidden: whether the column is hidden. - Unique: whether the column values must be unique. The spec must include all existing columns including the ID column. Existing columns' data types cannot be changed; to change a type, hide the old column and add a new one with the desired type. |
Output
The node outputs JSON data representing the updated Table object as returned by the Tulip API. This typically includes the updated table metadata and column definitions reflecting the changes made.
No binary data output is indicated.
Dependencies
- Requires connection to the Tulip API via an API key credential configured in n8n.
- The node depends on the Tulip API endpoints for fetching tables and columns (for dropdown options) and for updating table specifications.
- Proper permissions on the Tulip account are necessary to modify tables.
Troubleshooting
- Missing or invalid Table ID: Ensure the Table Name or ID property is correctly set and corresponds to an existing table accessible by your API credentials.
- Column specification errors: The update requires all existing columns to be included in the spec. Omitting any existing column or attempting to change a column’s data type directly will cause errors. To change a column type, mark the old column as hidden and add a new column with the desired type.
- API authentication failures: Verify that the API key credential is valid and has sufficient permissions.
- Network or connectivity issues: Confirm that n8n can reach the Tulip API endpoint.