Twake Drive icon

Twake Drive

Basic Twake Drive
Join our community

Actions13

Overview

This node integrates with Twake Drive to perform various file and folder operations. Specifically, the Update File operation allows users to update an existing file's metadata, such as renaming it.

Common scenarios where this node is beneficial include:

  • Renaming files stored in Twake Drive programmatically.
  • Automating file management workflows, e.g., updating file names based on external triggers or data.
  • Integrating Twake Drive file updates into larger automation pipelines.

For example, you might use this node to rename a report file after processing it, ensuring consistent naming conventions without manual intervention.

Properties

Name Meaning
File ID The unique identifier of the file you want to update.
Name of the New File A boolean toggle indicating whether you want to specify a new name for the file.
New Name The new name to assign to the file if "Name of the New File" is enabled.

Output

The node outputs an array of JSON objects corresponding to each input item processed. Each output item contains a json field with details about the updated file, typically including its updated metadata such as the new name and file ID.

If the node supports binary data (not explicitly shown here), it would represent file content or attachments; however, for the Update File operation, the focus is on metadata updates, so binary output is not expected.

Dependencies

  • Requires an API key credential for authenticating with the Twake Drive API.
  • Needs the Twake Drive instance URL and API token configured in the credentials.
  • The node uses internal helper modules for file operations but no external dependencies beyond the Twake Drive API.

Troubleshooting

  • Invalid File ID: If the provided File ID does not exist or is incorrect, the node will throw an error indicating the file could not be found. Verify the File ID is correct.
  • Permission Errors: Insufficient permissions or invalid API tokens can cause authorization failures. Ensure the API key has appropriate access rights.
  • Missing New Name: If "Name of the New File" is enabled but "New Name" is empty, the operation may fail or have no effect. Always provide a valid new name when renaming.
  • API Rate Limits: Frequent calls may hit API rate limits; handle errors gracefully and consider adding delays or retries.

Links and References

Discussion