Sanaf AI
Start free
Images & Design

Cloudinary, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Cloudinary account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Images & Design
  • Connects with a key
  • 34 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Cloudinary is

Cloudinary is a cloud-based media management platform for uploading, storing, transforming, and delivering images and videos via CDN.

You paste in a key from your own Cloudinary account. It is kept encrypted, and you can withdraw it from inside Cloudinary whenever you like.

How a run works

One message in, the work done in Cloudinary.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Cloudinary. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Cloudinary account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

34 tools it already has

What it can do in Cloudinary

These are the ready-made tools your AI employee already has in Cloudinary. It is not limited to them, but it never has to be taught these.

  • Create FolderTool to create a new asset folder. use when you need to organize assets into nested directories. use after confirming the folder path does not already exist.
  • Create Metadata FieldTool to create a new metadata field definition. use when extending your metadata schema with new fields.
  • Create TriggerTool to create a new webhook trigger for a specified event type. use after configuring your webhook endpoint and choosing the event type. example: "create a trigger for uploads to
  • Create Upload MappingTool to create a new upload mapping folder and url template. use when you need to dynamically map external url prefixes to a cloudinary asset folder before uploading files.
  • Create Upload PresetTool to create a new upload preset. use when defining centralized upload options (tags, formats, transformations, etc.) before asset uploads.
  • Delete Derived ResourcesTool to delete derived assets. use when you need to remove specific derived assets by their ids. example: "delete derived assets with ids [id1, id2]".
  • Delete FolderTool to delete an empty asset folder. use when the folder is confirmed empty and you need to remove it.
  • Delete Metadata FieldTool to delete a metadata field by external id. use when you need to remove a metadata field that is no longer required.
  • Delete Metadata Field Datasource EntriesTool to delete datasource entries for a specified metadata field. use when you need to soft-delete (inactivate) specific entries in a field's datasource. example prompt: "delete en
  • Delete Resources by Asset IDTool to delete resources by asset ids. use when you need to permanently remove specific resources by their immutable asset ids; irreversible.
  • Delete Resources by TagsTool to delete cloudinary assets by tag. use when you need to remove all assets associated with a given tag.
  • Delete TriggerTool to delete a trigger (webhook notification). use when you need to remove a trigger by its id after confirming the correct id.
  • Get Adaptive Streaming ProfilesTool to list adaptive streaming profiles. use when retrieving built-in and custom adaptive streaming profiles for delivering video via hls or dash.
  • Get Metadata Field By IDTool to get a single metadata field definition by external id. use after creating or updating a metadata field to fetch its full definition. example: "get metadata field definition
  • Get product environment config detailsTool to get product environment config details. use when you need to fetch or verify environment configuration such as folder mode.
  • Get Resource by Asset IDGet resource by asset id
  • Get Resource by Public IDTool to get details of a single resource by public id. use when you need full asset, derived, and related info.
  • Get Resource TagsTool to list all tags used for a specified resource type. use when you need to retrieve or page through the tags assigned to your assets.
  • Get Resources by Asset FolderTool to list assets stored directly in a specified folder. use when you need to view assets in a specific folder without including subfolder contents.
  • Get Resources by ContextTool to retrieve assets with a specified contextual metadata key/value. use when filtering resources by context metadata.
  • Get Resources in ModerationTool to retrieve assets in a moderation queue by status. use after moderation to process pending or reviewed assets.
  • Get Root FoldersTool to list all root folders in the product environment. use when you need to retrieve top-level asset folders.
  • Get Streaming Profile DetailsTool to get details of a single streaming profile by name. use when you need to inspect an existing profile's configuration before making changes. example: "get details of streamin
  • Get TransformationsTool to list all transformations (named and unnamed). use when you need to retrieve transformation definitions or paginate through transformation records.
  • Get Upload Mapping DetailsTool to retrieve details of a single upload mapping by folder. use when you need the url prefix template associated with a specific mapping folder.
  • Get Upload MappingsTool to list all upload mappings by folder. use when you need to retrieve and paginate through upload mapping configurations, optionally filtering by folder.
  • Get UsageTool to get product environment usage details. use when you need to monitor your cloudinary account storage, bandwidth, requests, and other usage limits.
  • List Webhook TriggersTool to list all webhook triggers for event types in your environment. use when you need to retrieve or filter existing triggers by type.
  • Order Metadata Field DatasourceTool to update ordering of a metadata field datasource. use when you need to reorder enum or set values for a metadata field datasource before updating assets.
  • Ping Cloudinary ServersTool to ping cloudinary servers. use when testing api reachability and authentication.
  • Restore Metadata Field Datasource EntriesTool to restore previously deleted datasource entries for a metadata field. use after deleting entries to reactivate soft-deleted datasource entries.
  • Search FoldersTool to search asset folders with filtering, sorting, and pagination. use when you need to locate specific folders by name, path, or creation date.
  • Update FolderTool to rename or move an existing asset folder. use when you need to change the folder's name or location.
  • Update Metadata FieldTool to update a metadata field definition by external id. use when modifying an existing schema field (e.g., changing label or validation) without redefining all properties.
Access, and who is in charge of it

You stay the boss of your Cloudinary account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Cloudinary account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Cloudinary is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Cloudinary and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about Cloudinary

Can an AI employee really work inside Cloudinary?
Yes. It signs in to your own Cloudinary account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Cloudinary?
No. Nothing moves and nothing is replaced. Your records stay in Cloudinary, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Cloudinary account?
You paste in a key from your own Cloudinary account. It is kept encrypted, and you can withdraw it from inside Cloudinary whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Cloudinary?
It has 34 ready-made tools in Cloudinary today, among them Create Folder, Create Metadata Field and Create Trigger. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Cloudinary and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Cloudinary and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Cloudinary?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Cloudinary is written down with what it did and when.