Photos in a folder, product live in WooCommerce: a Make.com + n8n pipeline for a refurbished-tools shop
A shop that sells refurbished professional power tools has a problem that new-goods shops don't: there are no manufacturer photos. Every unit is different, so every unit has to be photographed, cleaned up and listed by hand. Per product that is a few minutes. Across hundreds of products it is days of work that you can't hand to anyone without the photo quality dropping. I built a pipeline for…
A Slovak shop specializing in refurbished Milwaukee, DeWalt, and Makita power tools struggled with the painstaking task of photographing each individual unit, cleaning them up, and listing them manually. Luko Tools owner sought a solution to automate the process. The result is a Make.com + n8n pipeline that takes photos from a Google Drive folder, upscales and sharpens them, removes backgrounds, creates products in WooCommerce, and posts to social media.
Before implementing the pipeline, Luko Tools followed a similar workflow: photographing, sorting, enhancing product quality, background removal, WooCommerce upload, filling in details, and category assignment. With the new pipeline, photos automatically land in a Google Drive folder triggered by Make.com. The photos are enlarged and sharpened using an image-processing API, and backgrounds are removed as well.
WooCommerce REST API creates the product with a gallery of processed images, making the listing live. An n8n workflow then builds social posts from the product photo and name. By using official APIs, the solution stays separate from the WooCommerce platform, minimizing any potential impact on the shop and allowing for updates without breaking changes.
However, the pipeline does not take photos, so input quality directly affects the output. Pricing and descriptions for refurbished goods still depend on the condition of each unit, which remains a manual decision. Items that don't fit the pattern are better created by hand. The trade-off is that the listing is automatic, which may not be suitable for goods where a bad listing could be costly.
Image-service running costs depend on the number of photos processed, and the system requires an API on the shop side. The author didn't quantify the hours saved but noted that products now reach the shop continuously, rather than in occasional pushes. The client's review is published on an independent portal, not on the author's site. The full case page, including a diagram and limitations, can be found at nexflow.sk/en/case-ecommerce-products.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
