Automated Odoo Product Image Synchronization from Google Drive - n8n Workflow

• E-commerce Managers needing centralized image management.


• ERP Administrators utilizing Odoo for product catalog maintenance.


• Automation Specialists looking for a robust n8n templates for integration between cloud storage and business systems.


• Developers requiring repeatable file processing logic within an n8n workflow.

Managing product images across different systems can be time-consuming. This specialized n8n workflow solves the common challenge of ensuring that product and product template images stored in Google Drive are automatically synchronized and updated within Odoo ERP. By defining a clear naming convention (e.g., model_sku.jpg), the n8n automation can identify the target Odoo record, download the image, convert it to the necessary Base64 format, and update the corresponding Odoo fields.

The value proposition of this n8n solution is hands-free data consistency. It runs on a schedule (using the n8n trigger), ensuring that new or updated image files are processed, uploaded to Odoo, and then archived in a 'done' folder, providing a complete, auditable integration using powerful n8n node configurations.

This n8n workflow starts with a scheduled n8n trigger, running every 10 minutes, or can be initiated manually.

1. File Discovery: The Find Files Google Drive n8n node scans a designated 'input' folder for new files.


2. Filtering: The Filter Images n8n node ensures only files ending in .png or .jpg are processed.


3. Data Decoration: The Decorate Images Code n8n node is crucial. It parses the filename to extract two key variables: model (identifying if the target is a product or template) and sku (which maps to the Odoo defaultcode). For example, a file named templateSKU123.jpg is transformed into structured data items.


4. Routing: The Switch n8n node evaluates the model variable and routes the execution flow into two parallel branches: one for product templates and one for product variants.


5. Odoo Synchronization (Parallel):

1. Cleanup & Archiving: Concurrently, the original item is processed for cleanup. The n8n workflow searches for and deletes any old versions of the file in the 'done' folder (Search Old Images, Drop Old Images), and then moves the newly processed image to the 'done' folder (Move Images).


2. Notification: A Summarize n8n node counts the processed items, and the Announce Google Chat n8n node sends a confirmation message detailing the total number of images successfully updated.

To utilize this highly functional n8n workflow, follow these steps:

1. Import the n8n template: Copy the provided JSON data and paste it directly into your n8n instance via the 'New' menu and selecting 'Import workflow from JSON'.


2. Google Drive Credentials: You need an OAuth2 credential set up for Google Drive. Replace the existing credential references in the Find Files, Move Images, Download Images Templates, and Download Images Products Google Drive n8n node configurations.


3. Odoo Credentials: Set up an Odoo API credential connection. Ensure the connection in the Find Templates, Update Images Templates, Find Products, and Update Images Products Odoo n8n node is correctly configured to your ERP instance.


4. Google Chat Credentials (Optional): If you require notifications, update the OAuth2 credentials for the Announce Google Chat n8n node.


5. Configure Paths: Adjust the specific Drive ID and Folder IDs within the Find Files and Move Images Google Drive n8n node parameters to point to your actual 'input' and 'done' folders.


6. Activate: Once credentials and paths are set, activate the n8n workflow.

Schedule Trigger / Manual Trigger n8n trigger: Initiates the workflow either on a fixed schedule (every 10 minutes) or on demand.
Find Files (Google Drive n8n node): Retrieves a list of all files from the configured input folder, setting the stage for the rest of the n8n workflow.
Decorate Images (Code n8n node): Executes custom JavaScript logic to dynamically extract image type (model) and Odoo SKU from the filename, creating necessary metadata for routing and database lookup.
Switch (n8n node): Acts as a router, sending items to either the 'product template' branch or the 'product variant' branch based on the derived model field.
Odoo (n8n node): Used multiple times for finding (using default_code) and updating records (product.template and product.product). It handles the core business logic connection in this n8n automation.
Download Images (Google Drive n8n node): Downloads the actual image file content as binary data.
Convert Base64 Images (ExtractFromFile n8n node): Converts the downloaded binary data into a Base64 string property, a requirement for updating image fields within Odoo via the API.
Move Images (Google Drive n8n node): Manages file lifecycle by moving successfully processed files from the input folder to an archive folder, providing completion assurance for this specific n8n workflow.