Actions5
- Upload Actions
- Update Asset Actions
- Admin Actions
Overview
This node integrates with Cloudinary to update tags on an existing asset. It allows users to modify the tags associated with a specific media asset (image, video, or raw file) stored in Cloudinary. This is useful for organizing and categorizing assets after upload, enabling better searchability and management within the Cloudinary platform.
Typical use cases include:
- Adding or updating descriptive tags on images or videos to improve asset organization.
- Automating tag updates as part of a larger workflow that manages media assets.
- Invalidating CDN caches when tags are updated to ensure changes propagate quickly.
For example, you might use this node to add seasonal tags to product images or to categorize videos by content type dynamically.
Properties
| Name | Meaning |
|---|---|
| Public ID | The unique public 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 the update operation. Currently supports: Invalidate CDN (boolean) to invalidate CDN cache copies of the asset. |
Output
The node outputs JSON data representing the response from the Cloudinary API after updating the asset's tags. This typically includes details about the updated resource such as its public ID, tags, version, and other metadata returned by Cloudinary.
No binary data output is produced by this operation.
Example output structure (simplified):
{
"public_id": "sample_asset",
"tags": ["tag1", "tag2"],
"type": "upload",
"resource_type": "image",
"version": 1234567890,
...
}
Dependencies
- Requires a valid Cloudinary account with API credentials (cloud name, API key, and API secret).
- The node uses these credentials to authenticate API requests to Cloudinary.
- No additional external dependencies beyond the Cloudinary API and n8n's HTTP request helper.
Troubleshooting
- Invalid JSON for structured metadata: Although not directly related to tag updates, if using the metadata update operation, ensure that the structured metadata JSON is valid. Malformed JSON will cause errors.
- Authentication errors: Ensure that the provided API credentials are correct and have sufficient permissions to update assets.
- Asset not found: If the specified Public ID does not exist or is incorrect, the API will return an error. Verify the Public ID and resource type.
- Invalid tags format: Tags must be provided as a comma-separated string. Empty or improperly formatted tags may cause the update to fail.
- CDN invalidation issues: If CDN invalidation is enabled but changes do not appear immediately, allow some time for cache propagation or verify CDN settings in Cloudinary.