Enhance product photos with Google Gemini AI for e-commerce catalog
Ready for 3.0What this workflow does
This AI workflow has 14 nodes and runs on Google Drive events (file created) (plus 1 other trigger). Along the way it connects Google Drive, Google Gemini and Google Sheets. It also calls generativelanguage.googleapis.com over HTTP.
How it runs
Trigger: On Google Drive events (file created) (plus 1 other trigger).
- Set File ID (Edit Fields (Set)): sets 5 fields: input_file_id, input_file_name, input_file_name_no_ext…
- Workflow Configuration (Edit Fields (Set)): sets 3 fields: google_sheet_id, dest_folder_id, text_prompt
- Create Entry (Google Sheets): append or update
- Download Image (Google Drive): download
- Edit Image (Google Gemini): edit (image)
- Save image (Google Drive): uses Google Drive
- Update Entry to Error (Google Sheets): append or update
- Update Entry to Done (Google Sheets): append or update
- Extract from File: extracts data from a file (binary to propery)
- Gemini Image (HTTP Request): calls generativelanguage.googleapis.com (POST)
…plus 2 more steps. See the full node list below.
Services it uses
HTTP calls to: generativelanguage.googleapis.com
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (8)
- Google Drive Trigger
n8n-nodes-base.googleDriveTrigger - Edit Fields (Set)
n8n-nodes-base.set - Extract from File
n8n-nodes-base.extractFromFile - Convert to File
n8n-nodes-base.convertToFile - Google Drive
n8n-nodes-base.googleDrive - HTTP Request
n8n-nodes-base.httpRequest - Google Gemini
@n8n/n8n-nodes-langchain.googleGemini - Google Sheets
n8n-nodes-base.googleSheets
From the author
Automated image processing for e-commerce product catalog Use cases Monitor a Google Drive folder, process each image based on the prompt defined in Workflow Configuration and save the new image to the specified output Google Drive folder. Maintain a…