Cloudinary icon

Cloudinary

Upload to Cloudinary

Actions5

Overview

This node enables uploading assets to a cloud-based media management service from URLs. Specifically, the Upload From URL operation allows users to provide a direct URL of an image, video, or raw file, which the node then uploads to the cloud service. This is useful for automating media ingestion workflows where files are hosted externally and need to be imported without manual download and re-upload.

Common scenarios:

  • Automatically importing images or videos from external sources into your media library.
  • Migrating assets from other platforms by providing their URLs.
  • Integrating with webhooks or APIs that supply media URLs for processing and storage.

Example:
You have a list of image URLs from a marketing campaign and want to upload them all to your cloud media account for further processing or delivery. Using this node, you can input each URL, specify the asset type (image/video/raw), and optionally set metadata like folder or public ID.

Properties

Name Meaning
URL The direct URL of the image, video, or raw file to upload.
Resource Type The type of asset being uploaded. Options: Image, Video, Raw.
Additional Fields Optional extra parameters:
• Public ID: Custom identifier for the uploaded resource.
• Folder: Folder path in the cloud storage.
• Upload Preset: Predefined upload settings configured in your cloud account.

Output

The node outputs JSON data representing the response from the cloud media service after the upload request completes. This typically includes details such as:

  • Asset public ID
  • URL(s) to access the uploaded asset
  • Asset type and format
  • Size and dimensions (for images/videos)
  • Upload timestamp and status

If the upload is successful, the output JSON contains the full metadata of the newly created asset. If there is an error, the output will contain an error message describing the issue.

The node does not output binary data for this operation since it uploads from a URL rather than local files.

Dependencies

  • Requires an API key credential for authenticating with the cloud media service.
  • Needs network access to the provided URLs and the cloud service endpoints.
  • No additional environment variables are required beyond the API credentials.

Troubleshooting

  • Invalid URL or inaccessible resource:
    If the URL is incorrect, private, or blocked, the upload will fail. Ensure the URL is publicly accessible and points directly to a valid media file.

  • Authentication errors:
    Incorrect or missing API credentials will cause authentication failures. Verify that the API key and secret are correctly configured.

  • Unsupported resource type:
    Selecting a resource type that does not match the actual file may cause upload errors. Confirm the resource type matches the file content (e.g., image vs video).

  • Additional fields misconfiguration:
    Providing invalid values for fields like public_id or upload_preset may result in errors. Double-check these values against your cloud account settings.

  • Error messages:
    Errors returned from the cloud service are passed through in the output JSON under an error field if "Continue On Fail" is enabled. Review these messages for specific causes.

Links and References

Discussion