Overview
This node is designed to delete a record from a multi-dimensional table system, identified uniquely by an application token. It is useful in scenarios where you need to programmatically remove specific entries from a data table, such as cleaning up outdated information, managing records dynamically based on workflow conditions, or automating data maintenance tasks.
For example, if you have a table storing user feedback and want to delete entries that are no longer relevant or were submitted erroneously, this node can be configured to perform those deletions automatically using the unique identifier of the table.
Properties
| Name | Meaning |
|---|---|
| app_token | The unique identifier of the multi-dimensional table from which a record will be deleted |
Output
The node outputs JSON data representing the result of the deletion operation. This typically includes confirmation of success or failure, and may contain metadata about the deleted record or error details if the operation did not succeed.
No binary data output is indicated in the source code.
Dependencies
- Requires access to the multi-dimensional table service via an API.
- Needs an API authentication token or key (referred generically as "an API key credential") to authorize requests.
- The node depends on internal routing and transport modules to handle the request execution and data retrieval.
Troubleshooting
- Common issues:
- Invalid or missing
app_tokenleading to failure in identifying the target table. - Authentication errors due to incorrect or expired API credentials.
- Network connectivity problems preventing communication with the external service.
- Invalid or missing
- Error messages:
- Errors indicating "record not found" suggest the specified record does not exist or has already been deleted.
- Authorization errors imply issues with the provided API key or permissions.
- Resolutions:
- Verify the correctness of the
app_token. - Ensure valid and active API credentials are configured.
- Check network settings and service availability.
- Verify the correctness of the
Links and References
- Refer to the official documentation of the multi-dimensional table service for details on API usage and authentication.
- n8n documentation on creating and configuring custom nodes for handling API operations.