Overview
This node is designed to interact with a multi-dimensional table service, specifically to add new records ("新增记录") to the table. It is useful in scenarios where users want to programmatically insert data entries into a structured table format, such as logging events, adding user information, or updating datasets dynamically within an automation workflow.
For example, you might use this node to add a new row of customer data into a shared spreadsheet-like database whenever a form is submitted, enabling seamless data collection and integration.
Properties
| Name | Meaning |
|---|---|
| app_token | The unique identifier of the multi-dimensional table. This token specifies which table the new record will be added to. |
Output
The node outputs JSON data representing the result of the "add record" operation. This typically includes confirmation details such as the ID of the newly created record, status messages, or any metadata returned by the table service after insertion.
If the node supports binary data output (not evident from the provided code), it would represent attachments or files related to the record, but no such indication is present here.
Dependencies
- The node relies on external modules for routing actions (
./actions/router), version description (./actions/versionDescription), and transport logic for listing and filtering (./transport/getList). - It requires an API token or key (referred to as
app_token) that uniquely identifies the target multi-dimensional table. - Proper configuration of this token within the node's input properties is necessary for successful execution.
Troubleshooting
- Common Issues:
- Missing or invalid
app_token: The node will fail to identify the target table, resulting in errors. - Network or API access issues: If the external service is unreachable or credentials are incorrect, the node cannot add records.
- Missing or invalid
- Error Messages:
- Errors related to authentication usually indicate problems with the provided token; verify its correctness.
- Timeout or connection errors suggest network problems or service downtime.
- To resolve these, ensure the
app_tokenis valid and that the service endpoint is accessible from your environment.
Links and References
- Since the node interacts with a multi-dimensional table service, consult the official documentation of that service for details on token generation and API usage.
- Review n8n documentation on how to configure nodes with API tokens and handle authentication securely.