How to Sync Google Drive to Odoo Catalog Images?
Description
Keep your Odoo catalog images fresh with files from Google Drive. Every ten minutes or on demand, new product and template images are picked up, applied to the correct records, and the team gets a clear message in Google Chat. It suits ecommerce and catalog teams that manage many SKUs.
The flow starts on a schedule or manual click, searches a Drive folder for files, and filters to valid images. It reads the file name to pull a model and SKU, then routes items with a Switch to either product templates or product variants. For each item, it finds the matching record in Odoo by SKU, downloads the image, converts it to base64, and updates multiple image sizes. It also removes older images from Drive, moves processed files to a done folder, and posts a count of processed items in Google Chat.
You will need Google Drive access, Odoo credentials with rights to read and update catalog records, and a Google Chat space. File names should follow a simple rule like model_sku.jpg so the parser can match the correct SKU. Expect image updates to go from hours of manual uploads to minutes, fewer mistakes on the catalog, and faster product launches for new drops and seasonal refreshes.
Tools Required
What this workflow does?
- Runs on a schedule every ten minutes or by a manual click
- Finds all files in a Google Drive folder and filters to valid images
- Parses file names to extract model and SKU with a simple code step
- Routes items with a Switch to update templates or products
- Searches Odoo by SKU to locate the exact record to update
- Downloads images from Drive and converts them to base64
- Updates multiple Odoo image fields such as 1920, 1024, 512, and 256
- Deletes older images in Drive and moves processed files to a done folder
- Sends a Google Chat message with the total count processed
What are the benefits?
- Reduce manual work from 3 hours to 10 minutes per batch
- Automate about 90 percent of repetitive uploads and moves
- Improve image match accuracy by 95 percent using SKU parsing
- Handle 10 times more images without adding staff
- Connect Google Drive, Odoo, and Google Chat in one flow
How to set this up?
- Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
- You'll need accounts with Google Drive, Odoo and Google Chat. See the Tools Required section above for links to create accounts with these services.
- Open the Find Files node and connect a Google Drive credential. If unsure, double click the node, then on the Credential to connect with dropdown click Create new credential and follow the on screen instructions.
- Open the Announce node and connect a Google Chat OAuth2 credential. If unsure, create a new credential from the dropdown and follow the on screen steps to approve access to your Chat space.
- Open any Odoo node and create an Odoo credential. Enter your Odoo URL, database, username, and password or API key. Name the credential clearly so your team can identify it later.
- In the Find Files node, select the correct Drive and source folder that will receive new images from your team or vendors.
- Review the Filter Images node and adjust conditions to include only the file types you want to process, such as jpg or png.
- Open the Decorate Images code node and confirm your file naming rule matches model_sku.ext. If your format is different, update the parsing logic to set model and sku correctly.
- Open the Switch node and set rules that direct template images to the template path and product images to the product path based on the model value you parse.
- Check the Update Images Templates and Update Images Products nodes. Confirm the record IDs come from the Find Templates or Find Products nodes and that image fields are mapped to the base64 data output.
- Open the Schedule Trigger and choose your preferred interval. Keep ten minutes while testing, then adjust as needed for your volume.
- Run a manual test. Upload a few sample images to the source folder, click the manual trigger, and watch the run. Verify images update in Odoo, files move to the done folder, old files are removed, and a Chat message shows the total.
- Troubleshooting tips: if no record updates, confirm the SKU in the file name matches the default code in Odoo. If images do not save, check the Convert Base64 output field name and the mapping in the update nodes. If Drive actions fail, confirm folder permissions. If Chat does not post, verify the space ID and the OAuth2 connection.
Need help or want to customize this?
Ask in the Free Futurise Community.
Similar Templates
These templates were sourced from publicly available materials across the web, including n8n’s official website, YouTube and public GitHub repositories. We have consolidated and categorized them for easy search and filtering, and supplemented them with links to integrations, step-by-step setup instructions, and personalized support in the Futurise community. Content in this library is provided for education, evaluation and internal use. Users are responsible for checking and complying with the license terms with the author of the templates before commercial use or redistribution.Where an original author was identified, attribution has been provided. Some templates did not include author information. If you know who created this template, please let us know so we can add the appropriate credit and reference link. If you are the author and would like this template removed from the library, email us at info@futurise.com and we will remove it promptly.
