Media asset uploads

Cloudinary stores the images, video, and other media files a team uses across a site or product, organized into folders with metadata attached to each asset. A Beam agent uploads a new file when a workflow produces one, such as a generated thumbnail or a submitted photo, and attaches the tags or metadata the team's rule specifies. It reads the resulting asset record to confirm the upload succeeded. If a file exceeds a size or format limit the account allows, or a required tag can't be determined from the source, the agent routes the asset to a person before it's used anywhere.

Resize and format preset application

Cloudinary can resize, crop, or reformat an asset on request using a preset the account defines, rather than storing a separate file for every size a page needs. A Beam agent applies an approved preset to a newly uploaded asset, such as generating a thumbnail or a smaller, web-ready version, and reads back the resulting URL to pass along to the next step or write into a connected system. When a preset produces an unexpected result, such as a badly cropped image, or the source file doesn't support the requested preset, the agent flags it for a person to review.

Asset metadata and tag updates

Every Cloudinary asset carries metadata such as tags, alt text, or custom fields that other systems rely on to find and use the file correctly. A Beam agent reads an asset's current metadata when a workflow step needs it, and writes an update, such as adding a tag or correcting a field, when the change matches an approved pattern, for example tagging assets from a specific campaign. It confirms the update is saved. If the required metadata can't be determined with confidence or conflicts with an existing tag, the agent routes the asset to a person instead of guessing.