Skip to content
← Back to documentation
Technical Reference

Cloudinary

Cloudinary is a cloud-based image and video management platform that allows you to upload, store, manage, and deliver your media assets. It provides a range of features for image and video optimization, transformation, and delivery.

CategoryContent And Files
Authenticationcustom
Version0.1.7
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Cloudinary with Flows360

Cloudinary is a cloud-based image and video management platform that allows you to upload, store, manage, and deliver your media assets. It provides a range of features for image and video optimization, transformation, and delivery.

Use the Cloudinary connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 5 actions and 2 triggers.

Available actions

  • Upload Resource
  • Delete Resource
  • Create Usage Report
  • Find Resource by Public ID
  • Transform Resource

Available triggers

  • New Resource
  • New Tag Added to Asset

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Cloudinary
  • Package: @activepieces/piece-cloudinary@0.1.7
  • Exact artifact digest: sha256:6334ba2a6fccdd8590d49299b298b2e94e7bf7cbdc35d8bfb7576f7fb4a8295d
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Upload Resource (uploadResource), Upload a new image, video, or file to Cloudinary. Classification: read.
  • Delete Resource (deleteResource), Permanently delete images, videos, or files from Cloudinary. Classification: read.
  • Create Usage Report (createUsageReport), Generate a comprehensive report of account usage and quotas including storage, bandwidth, transformations, requests, and add-on usage. Classification: read.
  • Find Resource by Public ID (findResourceByPublicId), Retrieve details of an asset using its unique public ID. Classification: read.
  • Transform Resource (transformResource), Apply transformations (resize, crop, watermark, etc.) to an asset and generate a new URL. Classification: read.

Trigger contracts

  • New Resource, polling.
  • New Tag Added to Asset, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects7
Supported actionsNot published
Triggers2

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential
  • API Secret Required · protected credential
  • Cloud Name Required

Supported objects

ObjectReadWriteNotes
Upload Resource Yes No Upload a new image, video, or file to Cloudinary.
Delete Resource Yes No Permanently delete images, videos, or files from Cloudinary.
Create Usage Report Yes No Generate a comprehensive report of account usage and quotas including storage, bandwidth, transformations, requests, and add-on usage.
Find Resource by Public ID Yes No Retrieve details of an asset using its unique public ID.
Transform Resource Yes No Apply transformations (resize, crop, watermark, etc.) to an asset and generate a new URL.
New Resource Yes No polling trigger declared by the pinned package.
New Tag Added to Asset Yes No polling trigger declared by the pinned package.

Triggers

New Resource · Poll

Triggers when a new image, video, or file is uploaded to a specific folder or account in Cloudinary.

Inputs

  • asset_folder · string
New Tag Added to Asset · Poll

Triggers when a tag is added to an asset in Cloudinary.

Inputs

  • resource_type · string
  • asset_folder · string

Setup

Setup

  1. Add the Cloudinary connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • API Key (api_key), required; stored as a sensitive connection value.
  • API Secret (api_secret), required; stored as a sensitive connection value.
  • Cloud Name (cloud_name), required.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-cloudinary@0.1.7; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 5 actions and 2 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Cloudinary connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-cloudinary@0.1.7 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.