Cloudinary has just a great picture processing platform and the paid tools are cheaper than any other tools.
For example background removal with Cloudinary is the least costly. Many commercial services actually piggy back on Cloudinary and charge high margins for background removal.
Several other tools are free (free tier) with Cloudinary e.g. image improvement command (make pictures pop out, very similar effect as what Etsy and Depop is doing when uploading images to their platform when creating online product listings).
Another favorite is adding overlays to pictures, useful for Pinterest etc. This is also free with Cloudinary (free tier is very generous).
I am struggling with one more issue. I can’t get the array working to process all images. Hope any Make.com Integromat expert here could chip in…
Here is the post at Cloudinary describing a nasty issue I encountered, now resolved.
And here is the Make flow.
The flow only processes 1st image of the attachment field. I want it to do all images.
I have seen @ScottWorld youtube video but that is only few steps there.
Okay I solved the issue… or perhaps I am closer to solving it.
The Iterator Flow Control Array field must only show the attachment field NAME only. It must not contain the usual NAME : URL as initially posted above.
The Iterator steps works now if this is how it’s setup:
Now I am dealing with another issue.
I have 5 attachments images in the attachment field. First 2 images are processed, but the 3rd images stops processing before the 2nd transformation. Hmm. what is the issue now.
I am posting all of this here, hopefully not to be yelled at that it’s not the right place to post here. There is very little documentation online how to deal with the arrays in Airtable and Cloudinary seems such a popular solution, perhaps this is useful for others.
It looks like the flow runs too fast. I need to put a sleep module between the tranformations.
Here is the issue:
Another sleep module needs to be put at the end of the flow, to enable the picture to be uploaded into the field, allow enough time before the flow goes back to iterator to start with the next picture.
Another issue was I had to add one more step to read the attachment field after the picture was added but before the next round is run. This is to allow the flow to see the current number of attachments in the field I am updating:
The last issue I had was to configure correctly what goes into the last Airtable Upload a Record step into the attachment field.
The syntax needs to be specific: The checkbox “Map” must be turned on. Here is how I set it up:
That means: only the exactly as it shows. Do not add the URL part to it…e.g. selecting 117. testpics URL … or 102. Array URL … would not work.
Last cosmetic improvement:
Small modification as the last step - customizing the title of the attached processed images:
Out of pure curiosity, I am still wondering what are these specifications there in “lila” color under “Tools”, what is the use, I can’t read from the images from @ScottWorld post…
