Actions5
- Upload Actions
- Update Asset Actions
- Admin Actions
Overview
This node integrates with a cloud-based media management service to update tags on existing digital assets. It allows users to assign or modify tags for images, videos, or raw files stored in the service. This is useful for organizing and categorizing media assets, enabling easier search, filtering, and management within large media libraries.
Typical use cases include:
- Adding descriptive tags to newly uploaded assets for better organization.
- Updating or correcting tags on existing assets as metadata evolves.
- Automating tag management workflows based on external triggers or data.
For example, a marketing team could automatically tag product images with campaign-specific keywords after upload, or a media library manager could batch-update tags to reflect new classification schemes.
Properties
| Name | Meaning |
|---|---|
| Public ID | The unique identifier of the asset to update. |
| Resource Type | The type of asset to update. Options: Image, Video, Raw. |
| Type | The storage type of the asset. Options: Upload, Private, Authenticated, Fetch. |
| Tags | A comma-separated list of tag names to assign to the asset. |
| Update Fields | Additional options for updating the asset. Currently supports: Invalidate CDN (boolean) — whether to invalidate CDN cache copies of the asset. |
Output
The node outputs JSON data representing the updated asset information returned by the media management service's API. This typically includes confirmation of the updated tags and other asset metadata fields.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the cloud media management service.
- The node makes HTTP requests to the service's REST API endpoints.
- Proper configuration of the API credentials within n8n is necessary for successful operation.
Troubleshooting
- Invalid JSON for structured metadata: Although not directly related to tag updates, if using the metadata update operation, ensure that any JSON input is correctly formatted.
- Authentication errors: Verify that the API key and secret are correctly configured and have sufficient permissions.
- Asset not found: Ensure the provided Public ID matches an existing asset of the specified resource type and storage type.
- Tag format issues: Tags must be provided as a comma-separated string without invalid characters.
- CDN cache not invalidated: If changes do not appear immediately, consider enabling the "Invalidate CDN" option to refresh cached copies.