Cloudinary

Overview

This node integrates with Cloudinary to upload and manage media assets such as images, videos, and raw files. Specifically, the Upload File operation under the Upload resource allows users to upload a file from binary data directly into their Cloudinary account.

Common scenarios where this node is beneficial include:

• Automating media uploads from workflows that generate or receive files (e.g., image processing pipelines).
• Centralizing asset management by uploading files to Cloudinary for CDN delivery and transformation.
• Integrating file uploads into content management systems or marketing automation tools.

Practical example:

• A workflow receives an image file from a form submission, then uses this node to upload the image to Cloudinary as an "image" resource type, optionally specifying a folder or public ID for organization.

Properties

Output

The node outputs JSON data representing the response from Cloudinary after the upload request. This typically includes details about the uploaded asset such as:

• public_id: The unique identifier assigned to the uploaded asset.
• version: Version number of the asset.
• signature: Signature confirming the upload.
• width, height: Dimensions for images/videos.
• format: File format (e.g., jpg, mp4).
• resource_type: The type of resource uploaded (image, video, or raw).
• created_at: Timestamp of upload.
• Other metadata returned by Cloudinary.

If the upload is successful, the output contains all relevant metadata for further use in the workflow.

Binary data is not outputted by this node; it only sends binary input and returns JSON metadata.

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.
• No additional external dependencies beyond standard HTTP requests.
• The user must configure the Cloudinary API credentials in n8n before using this node.

Troubleshooting

• Invalid Credentials Error: If authentication fails, verify that the Cloudinary API key, secret, and cloud name are correctly set in the credentials.
• File Not Found or Invalid Binary Data: Ensure the input binary property specified in the "File" field exists and contains valid file data.
• Invalid Additional Fields: Incorrectly formatted fields like upload_preset or public_id may cause upload failures. Double-check values against Cloudinary's requirements.
• Network or API Errors: Check network connectivity and Cloudinary service status if requests time out or fail.
• JSON Parsing Error (for other operations): When updating structured metadata (not applicable here), invalid JSON will cause errors.

To resolve most issues, confirm all required parameters are provided, credentials are valid, and the input binary data is correctly passed.

Links and References

• Cloudinary Upload API Documentation
• Cloudinary Upload Presets
• n8n Documentation on Binary Data Handling