Skip to content

Cloudinary, without opening Cloudinary.

Find the asset, not the folder it might be in.

  • Free to start
  • No card
  • Nothing irreversible without your yes
  • One key for the workspace
Try asking Ray

Ask in your own words.

Nothing to configure and no builder to open. Copy one of these into a thread, swap in your own Cloudinary details, and Ray takes it from there.

  • @Ray find the product shots we tagged for the spring launch.

  • @Ray how much storage are we using this month?

  • @Ray rename that hero image so it matches the campaign.

  • @Ray zip up the spring launch shots and send me the archive.

What Ray can and cannot do in Cloudinary

Reading is free, because reading changes nothing. Everyday changes Ray just makes, and anything that can't be taken back waits for your yes. The rest is not on Ray’s list.

32 reads wired, 5 actions Ray does at once, and 15 actions that wait for your yes.

Runs on its own

What Ray reads in Cloudinary

  • Search every asset by query expression, by tag, by folder or by what an image looks like
  • Images, videos and raw files with their tags, context and metadata
  • Named transformations, upload presets, folders and moderation queues
  • Storage and bandwidth usage, and how often a video was watched

Reading changes nothing, so Ray never stops to ask whether it may look something up.

Just does it

Ray does these at once

  • Link related assets
  • Set tags and context on an asset
  • Create a folder or a named transformation

Anything Ray can put back comes with an Undo button on its reply. In a schedule, a watch or a chase that has read outside content with nobody present, these wait for a yes too.

Asks first, every time

Always waits for your yes

  • Upload a file from a link
  • Rename an asset, or rename or move a folder
  • Set tags, context, and metadata values on assets
  • Build derived media: slideshows, archives, text images, page splits, combined files, and an asset's derived versions
  • Change a named transformation
  • Make private assets publicly deliverable, and restore deleted ones

Ray posts a card showing exactly what it is about to do. Nothing happens until someone approves, and no setting turns that off.

Not on the list

Things Ray is never handed

These are left out during curation, so they are not something Ray could do and decides against. They are not in front of it at all.

  • Destroy an asset, empty a folder, or delete assets by tag
  • Strip every tag or context value off a set of assets in one call
  • Configure the account: upload presets, upload mappings, webhook triggers or live streams
Before it acts

Exactly what Ray will ask you to approve.

Not a category of permission. These are the Cloudinary actions that stop in the thread with the real content before they happen.

  • Generate a text image in Cloudinary
  • Combine Cloudinary images into one animation, video or PDF
  • Build a Cloudinary slideshow video
  • Update a Cloudinary asset and build its derived versions
  • Split a multi-page Cloudinary file into separate images
  • Build a Cloudinary archive of assets
  • Make Cloudinary assets publicly available
  • Rename a Cloudinary asset
  • Restore deleted Cloudinary assets
  • Restore deleted Cloudinary assets

Ray does these at once

  • Link Cloudinary assets together
  • Link Cloudinary assets together
  • Create a Cloudinary folder
  • Create a named Cloudinary transformation
  • Change a Cloudinary asset

Everyday work. Anything Ray can put back comes with an Undo button on its reply.

The card Ray posts

Generate a text image in Cloudinary

Showing Public id, Text, Font family, Font size, Font color and Background, each carrying the exact content that will land.

ApproveDecline

How Ray works with Cloudinary

No workflow to build, and nothing to maintain when the work changes.

  1. 01

    Connect Cloudinary

    Cloudinary has no per-person login, so it takes one workspace key. Ray posts a connect card, you paste the key on Ray's own page rather than in Slack, and it covers the whole team from then on.

  2. 02

    Ask in plain words

    In the conversation you were already having. Nothing to build, no trigger to map, no tab to open.

  3. 03

    It lands, with an Undo

    Reading runs on its own. Everyday changes land at once with an Undo, and anything that sends, spends or can't be taken back waits for your yes with the exact content in front of you.

and the rest

Megan

@Ray the checkout bug is back. Take a look in Cloudinary, and tell Dana it is being looked at.

Link Cloudinary assets together

Done
just now
Undo
Works with your stack

Ray uses Cloudinary together with the rest of your tools.

One ask can read Cloudinary, cross-reference what is in these, and land the finished result back in the thread. Not four connectors taking turns, one teammate with one memory.

What does connecting Cloudinary to Ray actually do?

Ray is an AI teammate that works in your team chat, on Slack today. Connect Cloudinary and it can do the Cloudinary part of a request without anyone leaving the conversation: read what it needs and make the change, asking first before anything that can’t be taken back.

It is not a workflow builder. There is no trigger to configure and no automation to repair when your process shifts. You describe the outcome in the thread and Ray picks the actions, including actions in your other connected tools when the request spans more than one.

Cloudinary has no per-person login, so it connects once with a single workspace key and covers the whole team. Ray reaches whatever that key reaches, which is worth scoping the way you want everyone to see Cloudinary. Anything irreversible still waits for a yes.

Security and permissions

  • You paste the Cloudinary key on Ray’s own page, never in Slack. It goes straight to the connection and never reaches the model.
  • What waits for a yes is decided in the execution path, not by a prompt. No setting lets an irreversible action through without one.
  • Each workspace is isolated at the database level, and that isolation is tested by trying to break it.
  • An admin, or whoever connected it, can disconnect Cloudinary in a message. Uninstall Ray and every connection it held is revoked.

How Ray handles your data

Cloudinary and Ray, answered

The questions teams ask before they connect Cloudinary. Every answer is how this integration is built rather than a promise about it.

More storage & files integrations

Ray uses them together in a single run when a request spans more than one.

Browse every integration

Put Ray to work in Cloudinary.

Free to start, no credit card, and nothing irreversible happens without your yes.

Add to Slack for free

By adding Ray, you accept the Terms and Privacy Policy.