Skip to content
For LLMsView as Markdown·

Cloudinary ​

undefined

DetailValue
CategoryMedia
Base URLhttps://api.cloudinary.com/v1_1/{cloud_name}
AuthenticationAPI Key
Endpoints6
Connector keycloudinary

Using Cloudinary in a workflow ​

  1. Go to Connections and click New Connection.
  2. Pick Cloudinary from the marketplace.
  3. Enter your credentials (see Authentication above for what's expected).
  4. In a workflow, drop an API Call node and select this connection.
  5. Pick the operation you need from the Operation dropdown. The full list is below.

Available endpoints ​

EndpointSummary
GET Upload Image
GET Upload Video
GET List Resources
GET Folders
GET Transformations
GET Usage

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET ​

Upload Image

DetailValue
Operation IDupload_image_0
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Cloudinary connection from the Connection dropdown.
  3. In the Operation dropdown, select upload_image_0.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Cloudinary API reference.

GET ​

Upload Video

DetailValue
Operation IDupload_video_1
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Cloudinary connection from the Connection dropdown.
  3. In the Operation dropdown, select upload_video_1.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Cloudinary API reference.

GET ​

List Resources

DetailValue
Operation IDlist_resources_2
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Cloudinary connection from the Connection dropdown.
  3. In the Operation dropdown, select list_resources_2.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Cloudinary API reference.

GET ​

Folders

DetailValue
Operation IDfolders_3
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Cloudinary connection from the Connection dropdown.
  3. In the Operation dropdown, select folders_3.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Cloudinary API reference.

GET ​

Transformations

DetailValue
Operation IDtransformations_4
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Cloudinary connection from the Connection dropdown.
  3. In the Operation dropdown, select transformations_4.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Cloudinary API reference.

GET ​

Usage

DetailValue
Operation IDusage_5
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Cloudinary connection from the Connection dropdown.
  3. In the Operation dropdown, select usage_5.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Cloudinary API reference.