Automation · Orders and fulfillment

Store in Cloudinary, sorted by order, the photos a customer sends on WhatsApp

An AI agent stores in Cloudinary the photos a customer sends on WhatsApp, in their order's folder and with tags, and later hands them over as a ZIP.

Show me this with my own operation See every automation

How do I keep the photos my customers send on WhatsApp for their orders organized?

A Met connected to Cloudinary creates a folder for the order, uploads the photos or files the customer sends on WhatsApp into it and tags them with the order number and what they are. When someone in the workshop asks for them, the Met finds them by those tags, checks each file's details and bundles the whole order into a ZIP to download at once. That way the material is not lost between chats and does not depend on someone's phone. Everything stays in your business's Cloudinary library and counts against your plan's storage.

What starts it

When the customer writes

It starts when a customer sends the photos or files for their order on WhatsApp. There is no trigger to configure: the Met assigned to the line runs the procedure inside that conversation.

Nothing to set up. The Met assigned to that channel picks up the conversation and runs the procedure inside it.

Who runs it

Sales Met for personalized products

Sales team

This is not a named, seeded Met. It is the Met that already sells on the WhatsApp of a personalized products store, with Cloudinary connected. Its work ends when the customer's photos are in their order's folder, tagged and ready for the workshop to use.

Run by the sales closing Met

Channels: WhatsApp

What you need connected

Cloudinary Create and promote

6 steps · 6 tools

The procedure, step by step

Each step shows the tool that runs. They belong to the real connector: if one of them stopped existing, this page would not build.

1
Create the order's folder

The Met creates a folder in your library named after the order number or name, as the skill says, so each customer's material stays separate.
- create_folder Cloudinary
2
Upload what the customer sends

Each photo, video or file that arrives on WhatsApp is uploaded to your Cloudinary environment. The Met tells the customer how many files it received so they know if one is missing.
- upload_asset Cloudinary
3
Tag them

The Met updates each file with tags such as the order number and the item type, for example "mug" or "t-shirt", which is what makes them easy to find later.
- asset_update Cloudinary
4
Find the material when someone asks

When someone in the workshop asks the Met for an order's photos, the Met searches by their tags and returns the list of matching files.
- search_assets Cloudinary
5
Check each file

If there is a question about a photo, such as its size or format, the Met pulls that file's details and shares them with the team before anyone uses it.
- get_asset_details Cloudinary
6
Hand everything over as a ZIP

To avoid downloading files one by one, the Met bundles all the order's material into a ZIP archive and shares the download link. That action starts switched off: the admin turns it on if they want it.
- generate_archive Cloudinary

Before you start

What you need ready

The Met solves none of these for you. If one is missing, the automation stops there.

Cloudinary connected in Met

In Met, open Connections → Cloudinary → Connect, sign in and choose the environment where the photos will be stored. The admin leaves upload, update and create folder switched on, and turns on building the ZIP, which starts switched off.
A clear naming and tagging rule

Write in the Met's skill what an order's folder is called and which tags each file gets. Without that rule, every order ends up stored a different way.
A WhatsApp line with the Met assigned

The business connects its WhatsApp Business API line and assigns the Met that answers customers. The photos arrive in that conversation; Cloudinary is where they are stored.

The limits

What this automation does NOT solve

Better said here than discovered halfway through the rollout.

It does not check whether a photo is good enough to print or improve it: it only stores, tags and hands it over. Your team still judges the quality.
It does not ask for confirmation in the chat before uploading or tagging: if the action is on, it does it. The admin decides which writes stay on.
It does not delete what is no longer needed: deleting files and folders starts switched off, and this procedure does not need it.
It does not expand your plan: every file counts against your Cloudinary account's storage, and the Met can only tell you how much you have used.

FAQ

Questions about this automation

The Met uploads them as they arrive, all to the same folder and with the same order tags, and tells the customer how many it has.

Not necessarily: if the admin turned on building the ZIP, they can ask the Met for it and download it with the link. Anyone who wants to can also open the folder in Cloudinary.

Yes, as long as they are still in your library: the Met finds them by the tags it added when uploading. That is why the tagging rule should not change.

Whatever your Cloudinary plan costs: the files count against its storage. Meteor does not resell Cloudinary or charge for storage.

Keep going