Twake DriveInstall

Overview

The node integrates with Twake Drive to manage files and folders within a Twake instance. Specifically, the List Files operation under the File/Folder resource allows users to either list the contents of a folder or fetch details of a single file by specifying its ID.

This node is useful for automating workflows that require accessing and managing files stored in Twake Drive, such as:

• Retrieving all files inside a specific folder to process or analyze them.
• Fetching metadata or content of a particular file by its ID.
• Building integrations where file listings are needed dynamically based on user input or other triggers.

Example use cases include syncing files from Twake Drive to another system, generating reports on folder contents, or triggering actions based on file presence.

Properties

Name	Meaning
Target	Choose whether to list a folder's contents (Folder) or fetch a single file (File).
Target ID	The ID of the targeted file or directory. If listing a folder and left empty, the root directory is used.

Output

The node outputs JSON data representing the result of the listing or file fetch operation:

• When listing a folder, the output contains an array of files and folders inside the specified directory, including their metadata.
• When fetching a single file, the output contains the file's metadata and details.

If the node supports binary data (not explicitly shown here), it would represent file contents or attachments accordingly, but this operation primarily returns JSON metadata about files/folders.

Dependencies

• Requires an API key credential for authenticating with the Twake Drive API.
• Needs the Twake instance URL and API token configured in the credentials.
• Uses internal helper modules for file and directory operations bundled within the node.

Troubleshooting

• Empty or invalid Target ID: If the Target ID is incorrect or missing when fetching a file, the node may return an error or no results. Ensure the correct ID is provided or leave empty only when listing the root folder.
• Authentication errors: Invalid or expired API tokens will cause authentication failures. Verify the API key credential is valid and has necessary permissions.
• Permission issues: Accessing files or folders without sufficient rights may lead to errors. Confirm the authenticated user has access to the target resources.
• API rate limits or network issues: Temporary failures might occur due to API limits or connectivity problems. Retrying or checking network status can help.

Common error messages typically include HTTP error codes and descriptive messages from the Twake API, which should be reviewed to adjust inputs or credentials accordingly.

Links and References

• Twake Drive API Documentation (for detailed API capabilities)
• n8n Documentation - Creating Custom Nodes
• n8n Expressions Guide (useful for dynamic property values)