Actions13
Overview
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 updating table schemas dynamically based on process changes, hiding tables from UI without deleting them, or refining column properties like labels and data types.
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.
- Add, remove, or modify columns within a table while preserving existing data integrity by hiding old columns instead of changing their data types.
Properties
| Name | Meaning |
|---|---|
| Table Name or ID | Select the target table by name or specify its ID using an expression. This identifies which table will be updated. |
| Deleted | Boolean flag indicating whether the table should be hidden from the Tulip Tables UI. If true, the table is hidden; if false, it remains visible. If not specified, the deleted status remains unchanged. |
| Label | The display name (label) of the table. Used to identify the table in the UI and reports. |
| Description | A textual description of the table, explaining its purpose or contents. |
| Columns | A collection of column specifications defining the table schema. Each column includes: - Column Name or ID: Identifier of the column. - Label: Display name of the column. - Description: Explanation of the column. - Data Type: The type of data stored (e.g., Text, Number, Integer, Datetime, Boolean, 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 primary 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 such as its ID, label, description, deleted status, and full column definitions reflecting the changes made.
No binary data output is produced by this node.
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 loading options) and for updating table metadata.
- Proper permissions on the Tulip account are necessary to perform table updates.
Troubleshooting
- Error: Table not found or invalid ID — Ensure the Table Name or ID is correct and accessible by the authenticated user.
- Error: Cannot change data type of existing column — The Tulip API does not allow changing the data type of existing columns directly. To change a column’s type, mark the old column as hidden and create a new column with the desired type.
- Error: Missing required fields — Make sure all required properties (Table Name or ID, Deleted, Label, Description, and all columns with their required fields) are provided.
- API authentication errors — Verify that the API key credential is valid and has sufficient permissions.
- Columns specification incomplete — The update requires specifying all existing columns including the primary ID column; omitting any may cause errors.