Overview
This node integrates with a multi-dimensional table service (多维表格) to add new records into a specified database table. It is useful for automating data entry tasks where structured records need to be created programmatically based on dynamic inputs. For example, you can use this node to insert customer information, inventory items, or any structured dataset into your multi-dimensional table without manual input.
Typical scenarios include:
- Automatically logging form submissions as new records.
- Syncing data from other apps into the multi-dimensional table.
- Creating records triggered by events in workflows.
Properties
| Name | Meaning |
|---|---|
| app_token | The unique identifier token of the multi-dimensional table instance. This authenticates and scopes the operation to a specific workspace or application. |
| 记录表 (databaseId) | The target database table within the multi-dimensional table where the new record will be added. Must be selected after specifying the app_token. |
| 属性 (propertiesUi) | A collection of key-value pairs representing the fields and their values to set in the new record. Each property includes: |
| 键名或ID (key) | The field name or ID in the target table to set. Can be selected from a list or specified via expression. |
| 类型 (type) | The type of the field, automatically derived from the selected key. Types include Text, Formula, Barcode, Phone, MultiSelect, SingleSelect, Email, Url, User, CreatedUser, ModifiedUser, DuplexLink, Checkbox, Number, Currency, Progress, Rating, DateTime, CreatedTime, ModifiedTime. |
| TextValue | Text string value for Text type fields. |
| FormulaValue | Formula string for Formula type fields. |
| BarcodeValue | String value for Barcode type fields. |
| PhoneValue | Phone number string for Phone type fields. No strict format required. |
| MultiSelectValue | Array of option names or IDs for MultiSelect fields. Multiple options can be specified. |
| SingleSelectValue | Option name or ID for SingleSelect fields. |
| EmailValue | Email address string for Email type fields. |
| name, url | For Url type fields, the link name and URL address respectively. |
| UserValue | User name(s) or ID(s) for User, CreatedUser, or ModifiedUser fields. Multiple users can be comma-separated. |
| relation | Comma-separated related record IDs for DuplexLink fields. |
| CheckboxValue | Boolean indicating if a Checkbox field is checked (true) or not (false). |
| NumberValue | Numeric value for Number type fields. |
| CurrencyValue | Numeric value for Currency type fields. |
| ProgressValue | Numeric value for Progress or Rating fields, constrained by min/max values (e.g., 0-100 for Progress, 0-5 for Rating). |
| date | ISO 8601 formatted date/time string for DateTime, CreatedTime, or ModifiedTime fields. |
Output
The node outputs JSON data representing the newly created record in the multi-dimensional table. This typically includes the record's unique ID and all its properties as stored in the table after creation.
If the node supports binary data output (not indicated here), it would represent attachments or files associated with the record, but this node primarily deals with structured JSON data.
Dependencies
- Requires an API token or authentication credential that uniquely identifies and authorizes access to the multi-dimensional table service.
- The node dynamically loads available tables and field options based on the provided app_token, so network connectivity to the service API is necessary.
- No additional external dependencies are indicated beyond the API access.
Troubleshooting
- Invalid app_token or insufficient permissions: The node may fail to load tables or create records if the token is incorrect or lacks write permissions. Verify the token and user rights.
- Missing or incorrect databaseId: Ensure the target table is selected after entering the app_token. The node depends on this to know where to add the record.
- Field value type mismatches: Providing values incompatible with the expected field type (e.g., text in a number field) may cause errors. Double-check field types and corresponding input values.
- Network or API errors: Temporary connectivity issues or API rate limits may cause failures. Retry or check service status.
- Empty required fields: Some fields might be mandatory in the target table schema. Make sure to provide all required properties.
Links and References
- n8n Expressions Documentation
- Official documentation of the multi-dimensional table service (if publicly available) for details on field types and API usage.