Re-render product images and auto-tag VNTANA 3D assets with Gemini
UnknownWhat this workflow does
This workflow has 11 nodes and runs manually, when you click “Execute workflow” (plus 1 other trigger). Along the way it connects Vntana (community). It also calls generativelanguage.googleapis.com over HTTP.
How it runs
Trigger: Manually, when you click “Execute workflow” (plus 1 other trigger).
- Download renders (Vntana): work with render
- Skip Images Already Processed (Code): runs custom JavaScript code
- Prep Image for Gemini (Code): runs custom JavaScript code
- Limit: keeps the first few items
- Gemini Studio Re-render (HTTP Request): calls generativelanguage.googleapis.com (POST)
- Gemini Tagging (HTTP Request): calls generativelanguage.googleapis.com (POST)
- Extract Gemini Image (Code): runs custom JavaScript code
- Resolve Tags & Update Asset (Code): runs custom JavaScript code
- Upload a render (Vntana): upload (render)
Services it uses
HTTP calls to: generativelanguage.googleapis.com
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that n8n-nodes-vntana is verified or supports 3.0 (used in Download renders, Upload a render).
Nodes used (6)
- Manual Trigger
n8n-nodes-base.manualTrigger - Webhook
n8n-nodes-base.webhook - HTTP Request
n8n-nodes-base.httpRequest - Code
n8n-nodes-base.code - Limit
n8n-nodes-base.limit - Vntana
n8n-nodes-vntana.vntana
From the author
Quick Overview This workflow receives a VNTANA product publish webhook, downloads the product’s renders, uses Google Gemini to create a studio-style re-render and generate catalog tags, then uploads the new render back to VNTANA and updates the product’s tags…