Actions5
- Upload Actions
- Update Asset Actions
- Admin Actions
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 binary file data directly to Cloudinary's cloud storage.
Typical use cases include:
- Uploading user-generated content (images, videos) from a workflow.
- Automating media asset management by programmatically uploading files.
- Integrating with other systems that generate or manipulate files before sending them to Cloudinary.
For example, you could use this node to upload an image captured from a form submission or a video processed in a previous step of your workflow.
Properties
| Name | Meaning |
|---|---|
| File | The binary file data to upload. This is selected from the incoming binary data property. |
| Resource Type | The type of asset being uploaded. Options: Image, Video, Raw. |
| Additional Fields | Optional extra parameters for the upload: |
| - Public ID: Custom identifier for the uploaded resource. | |
| - Folder: Folder path in Cloudinary where the asset will be stored. | |
| - Upload Preset: Predefined upload preset name configured in Cloudinary account. |
Output
The node outputs JSON data representing the response from Cloudinary after the upload request completes. This typically includes details about the uploaded asset such as its public ID, URL, format, size, and other metadata returned by Cloudinary.
If the upload is successful, the output JSON contains all relevant information about the newly created resource in Cloudinary.
The node does not output binary data itself; it only returns metadata about the uploaded file.
Dependencies
- Requires a valid Cloudinary account with API credentials (cloud name, API key, and API secret).
- The node expects these credentials to be configured in n8n as an API key credential.
- Uses Cloudinary's REST API endpoints for uploading files.
- Requires internet access to communicate with Cloudinary's servers.
Troubleshooting
- Invalid Credentials: If the API key, secret, or cloud name are incorrect or missing, the upload will fail with authentication errors. Verify credentials in n8n settings.
- File Not Found or Invalid Binary Data: Ensure the input binary property specified actually contains valid file data.
- Invalid Additional Fields: Providing malformed or unsupported additional fields (e.g., invalid JSON or unsupported folder names) may cause errors.
- Network Issues: Connectivity problems can cause timeouts or failed uploads.
- Error Messages: Errors from Cloudinary are passed through in the JSON output. Common messages include "Invalid signature" (check timestamp and signing), "Resource not found", or "Upload preset not found".
To resolve issues:
- Double-check all input parameters.
- Confirm the binary data exists and is correctly referenced.
- Review Cloudinary account settings for upload presets and permissions.
- Enable "Continue On Fail" in the node to handle errors gracefully in workflows.