Cloud Radial icon

Cloud Radial

Interact with Cloud Radial API

Actions64

Overview

The node interacts with the Cloud Radial API to update an archive item within a specified archive (folder). It allows users to modify the name of an existing archive item by providing the archive ID and item ID. This operation is useful for managing and organizing archived content programmatically, such as renaming files or folders in a cloud-based archive system.

Use Case Examples

  1. Updating the name of a document stored in a specific archive folder by specifying the archive ID and item ID.
  2. Renaming an archived media file to reflect updated content or versioning information.

Properties

Name Meaning
Archive ID The ID of the archive (folder) where the item is located. Required to identify the specific archive containing the item to update.
Item ID The ID of the item within the archive to update. Required to specify which archive item to modify.
Name The new name to assign to the archive item. This is the updated name that will replace the current one.
Request Options Additional settings for the API request such as batching, SSL certificate validation, proxy configuration, and timeout settings to control request behavior and network handling.

Output

JSON

  • id - The unique identifier of the updated archive item.
  • name - The updated name of the archive item.
  • archiveId - The ID of the archive (folder) containing the item.
  • updatedAt - Timestamp indicating when the archive item was last updated.

Dependencies

  • Cloud Radial API

Troubleshooting

  • Ensure that the provided Archive ID and Item ID are correct and correspond to existing resources in the Cloud Radial system to avoid 'item not found' errors.
  • Verify that the API credentials are valid and have sufficient permissions to update archive items.
  • Check network settings such as proxy configuration and SSL certificate validation if requests fail or time out.
  • If batching is enabled, ensure batch size and interval settings are appropriate to avoid rate limiting or request throttling issues.

Links

Discussion