Cloudinary

undefined

Detail	Value
Category	Media
Base URL	https://api.cloudinary.com/v1_1/{cloud_name}
Authentication	API Key
Endpoints	6
Connector key	cloudinary

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

Endpoint	Summary
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

Detail	Value
Operation ID	upload_image_0
Method	GET
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

Detail	Value
Operation ID	upload_video_1
Method	GET
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

Detail	Value
Operation ID	list_resources_2
Method	GET
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

Detail	Value
Operation ID	folders_3
Method	GET
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

Detail	Value
Operation ID	transformations_4
Method	GET
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

Detail	Value
Operation ID	usage_5
Method	GET
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.