This article provides a complete, practical walkthrough of the Odoo Code Import Scheduled n8n agent. It connects HTTP Request, Webhook across approximately 1 node(s). Expect a Intermediate setup in 15-45 minutes. One‑time purchase: €29.

What This Agent Does

This agent orchestrates a reliable automation between HTTP Request, Webhook, handling triggers, data enrichment, and delivery with guardrails for errors and rate limits.

It streamlines multi‑step processes that would otherwise require manual exports, spreadsheet cleanup, and repeated API requests. By centralizing logic in n8n, it reduces context switching, lowers error rates, and ensures consistent results across teams.

Typical outcomes include faster lead handoffs, automated notifications, accurate data synchronization, and better visibility via execution logs and optional Slack/Email alerts.

How It Works

The workflow uses standard n8n building blocks like Webhook or Schedule triggers, HTTP Request for API calls, and control nodes (IF, Merge, Set) to validate inputs, branch on conditions, and format outputs. Retries and timeouts improve resilience, while credentials keep secrets safe.

Third‑Party Integrations

• HTTP Request
• Webhook

Import and Use in n8n

1. Open n8n and create a new workflow or collection.
2. Choose Import from File or Paste JSON.
3. Paste the JSON below, then click Import.
4. Show n8n JSON

   Title:  
   Automating Odoo Product Image Imports from Google Drive with n8n
   
   Meta Description:  
   Discover how to use n8n to automate the import, processing, and updating of Odoo product images stored on Google Drive. This workflow enhances efficiency, reduces manual work, and keeps your Odoo product catalog up to date.
   
   Keywords:  
   n8n, Odoo, Google Drive, image automation, product management automation, workflow automation, product image sync, base64 image processing, Google Chat notifications, ERP automation
   
   Third-Party APIs Used:
   
   1. Google Drive API
   2. Google Chat API
   3. Odoo API
   
   — — —
   
   Article:
   
   Automating Odoo Product Image Imports from Google Drive with n8n
   
   In any eCommerce or ERP-driven business, managing product imagery is a time-consuming yet critical operation. Proper image updates ensure accurate product representation, impact conversion rates, and improve the user experience. For companies using Odoo as their ERP system and Google Drive for media storage, the task of importing and updating product images can easily become a repetitive manual burden.
   
   This is where automation steps in.
   
   In this article, we'll explore a custom n8n workflow titled "Import Odoo Product Images from Google Drive," designed to run every 10 minutes and intelligently process, manage, and update product and template images in Odoo systems. This powerful workflow combines the capabilities of multiple third-party APIs — Google Drive, Google Chat, and Odoo — to automate and optimize image updates across your digital product catalog.
   
   Understanding the Workflow
   
   Here’s how the workflow operates step-by-step:
   
   1. Trigger and File Discovery
   The workflow can start either manually or on a schedule (every 10 minutes). It first scans a designated Google Drive folder ("input") inside a shared drive ("Middleware") for any image files (.jpg or .png). Only supported formats are passed to the next stage using a Filter node.
   
   2. Parsing File Metadata
   Each file name is parsed to extract important metadata. For example, a file named product_SKU12345.jpg will be split into:
   - Model: product
   - SKU: SKU12345
   
   These fields are necessary for locating corresponding records in Odoo.
   
   3. Handling Duplicates
   Before processing each new file, the workflow checks whether an image with the same name already exists in the "done" folder. If a duplicate is detected, it deletes the older image to avoid clutter and data conflicts.
   
   4. Branching by Model Type
   A Switch node evaluates whether the image corresponds to a product template or an individual product based on the "model" field extracted earlier. This determines which branch of the workflow is executed next.
   
   5. Looking Up Records in Odoo
   Depending on the branch, the workflow searches either:
   - The product.template model in Odoo, to match by default_code (SKU)
   - Or the product.product model, also by default_code
   
   If a matching record is found, its internal database ID is retrieved for updating.
   
   6. Downloading and Converting Images
   Next, the workflow downloads the image file from Google Drive and converts it from binary format to base64, which is compatible with Odoo’s image fields.
   
   7. Updating Odoo with New Images
   The converted image is used to update multiple image resolution fields within the respective Odoo record:
   - image_1920
   - image_1024
   - image_512
   - image_256
   - image_128
   
   Using less frequent fields like image_1920 helps support multiple UI display sizes inside Odoo and connected eCommerce platforms.
   
   8. Organizing Processed Files
   Once a file has been successfully processed and its corresponding Odoo record updated, the image is moved from the "input" folder to the "done" folder on Google Drive, effectively marking it as completed.
   
   9. Final Reporting via Google Chat
   A summary is generated showing how many images were processed during the current run. This count is then sent as a notification to a Google Chat space, alerting the team to the successful operation.
   
   Why This Workflow Is Valuable
   
   1. Automated Product Updates  
   Manual management of ERP media assets is error-prone and time-consuming. Automating this process ensures that product data in Odoo is always accurate and up-to-date.
   
   2. Smart Parsing and Routing  
   By extracting metadata from filenames and using branching logic in n8n, the workflow dynamically handles both templates and products without requiring logic duplication.
   
   3. Duplicate Management  
   The system checks for and removes old files automatically, avoiding redundancy and saving storage.
   
   4. File Integrity via Base64 Conversion  
   Using binary-to-base64 conversion ensures compatibility with Odoo’s API schema for image fields, guaranteeing seamless media uploads.
   
   5. Team Visibility  
   Real-time Google Chat notifications enhance operational transparency, keeping stakeholders informed without logging into n8n or Odoo.
   
   Future Enhancements
   
   This workflow is robust and can be further extended by:
   - Adding error handling and retries using IF and Error Trigger nodes
   - Sending alerts only upon failed attempts to minimize unnecessary notifications
   - Generating detailed logs or exporting image stats to Google Sheets or Notion
   - Involving an approval step where images are first validated before being pushed to live systems
   
   Conclusion
   
   The "Import Odoo Product Images from Google Drive" workflow is a shining example of what intelligent automation can achieve. Through modular logic, seamless API integration, and thoughtful design, this workflow reduces human error, increases operational speed, and ensures accurate product representation across your inventories.
   
   With n8n’s low-code flexibility and growing node ecosystem, tasks like this — which once took hours each week — can now run silently and reliably, giving your team the freedom to focus on higher-value work.
   
   — — —
   
   Whether you're running a wholesale catalog or an eCommerce storefront powered by Odoo, automating your media workflow is a key step toward digital efficiency — and with tools like n8n, it’s never been easier.

5. Set credentials for each API node (keys, OAuth) in Credentials.
6. Run a test via Execute Workflow. Inspect Run Data, then adjust parameters.
7. Enable the workflow to run on schedule, webhook, or triggers as configured.

Tips: keep secrets in credentials, add retries and timeouts on HTTP nodes, implement error notifications, and paginate large API fetches.

Validation: use IF/Code nodes to sanitize inputs and guard against empty payloads.

Why Automate This with AI Agents

AI‑assisted automations offload repetitive, error‑prone tasks to a predictable workflow. Instead of manual copy‑paste and ad‑hoc scripts, your team gets a governed pipeline with versioned state, auditability, and observable runs.

n8n’s node graph makes data flow transparent while AI‑powered enrichment (classification, extraction, summarization) boosts throughput and consistency. Teams reclaim time, reduce operational costs, and standardize best practices without sacrificing flexibility.

Compared to one‑off integrations, an AI agent is easier to extend: swap APIs, add filters, or bolt on notifications without rewriting everything. You get reliability, control, and a faster path from idea to production.

Best Practices

• Credentials: restrict scopes and rotate tokens regularly.
• Resilience: configure retries, timeouts, and backoff for API nodes.
• Data Quality: validate inputs; normalize fields early to reduce downstream branching.
• Performance: batch records and paginate for large datasets.
• Observability: add failure alerts (Email/Slack) and persistent logs for auditing.
• Security: avoid sensitive data in logs; use environment variables and n8n credentials.

FAQs

Can I swap integrations later? Yes. Replace or add nodes and re‑map fields without rebuilding the whole flow.

How do I monitor failures? Use Execution logs and add notifications on the Error Trigger path.

Does it scale? Use queues, batching, and sub‑workflows to split responsibilities and control load.

Is my data safe? Keep secrets in Credentials, restrict token scopes, and review access logs.