ODOO n8n INTEGRATION: AUTOMATE ODOO WITH N8N

Keeping opportunity data current reflects your actual sales progress and enables accurate forecasting. This action allows you to modify existing opportunity records based on data from any source in your workflow.

Key parameters: The action requires your Odoo credentials, the Opportunity resource selection, and Update operation. You must provide the Opportunity ID of the record you wish to modify. The Update Fields section lets you specify which properties to change and their new values—modify just one field or dozens, depending on your needs.

Practical use cases: Update opportunity stage when meetings are completed or contracts signed, adjust expected revenue based on negotiation outcomes, or reassign opportunities when sales territories change. This action integrates naturally with calendar tools, contract platforms, or any system that tracks deal progress.

When you need to retrieve multiple opportunities at once—for batch processing, reporting, or synchronization—this action delivers exactly that capability. It's designed for bulk retrieval of opportunity records based on your criteria.

Key parameters: Connect with your Odoo account credentials, set Resource to "Opportunity", and Operation to "Get Many". The Return All toggle, when enabled, fetches all matching records regardless of limit. When disabled, the Limit field (default 50) controls maximum records retrieved. The Options section allows filtering, sorting, and field selection.

Practical use cases: Generate weekly pipeline reports sent to Slack or Discord, sync all opportunities to your business intelligence tool, or identify stale deals that need attention. Building scheduled workflows with this action creates powerful automated reporting without manual effort.

When to use it: Use this action for reporting workflows, data synchronization tasks, or when you need to process multiple opportunities based on shared criteria rather than targeting a single record.

Retrieving individual opportunity details enables workflow decisions based on deal status, value, or other properties stored in Odoo. This action fetches a specific opportunity record for use in subsequent workflow steps.

Key parameters: Requires Odoo credentials, Resource set to "Opportunity", and Operation set to "Get". The optional Opportunity ID field specifies which opportunity to retrieve by its unique identifier. The Options section provides additional parameters for filtering or field selection.

Practical use cases: Check opportunity stage before triggering follow-up sequences, pull deal value for revenue reporting workflows, or verify opportunity exists before updating external systems. This action is particularly useful in conditional workflows where next steps depend on opportunity status.

Removing opportunities cleans your pipeline of cancelled deals or test data, maintaining accurate sales metrics. This action permanently deletes an opportunity record from your Odoo instance.

Key parameters: The action requires Odoo account credentials, Resource set to "Opportunity", Operation set to "Delete", and the mandatory Opportunity ID field containing the unique identifier of the opportunity you wish to remove.

Practical use cases: Remove opportunities marked as "Lost - No longer interested", clean up demo data after sales training sessions, or process bulk deletions for data maintenance. Consider marking opportunities as "Lost" instead of deleting them to preserve historical data for analysis.

Sales opportunities represent potential revenue, and automating their creation ensures your pipeline stays current without manual intervention. This action creates new opportunity records directly from your n8n workflows.

Key parameters: Requires Odoo credentials, Resource set to "Opportunity", and Operation set to "Create". The optional Name field provides the opportunity title. The Additional Fields section lets you add properties like expected revenue, probability, stage, salesperson, and linked contact.

Practical use cases: Create opportunities from inbound demo requests, generate pipeline entries when leads reach a qualification threshold, or sync deals from external sales tools into Odoo. Combining this with the Create Contact action lets you build complete lead-to-opportunity workflows that keep your CRM populated automatically.

Modifying existing notes keeps information current as situations evolve. This action allows you to update the content of notes previously created in Odoo.

Key parameters: Requires Odoo credentials, Resource set to "Note", and Operation set to "Update". The mandatory Note ID field identifies which note to modify. The optional Memo field contains the updated note content.

Practical use cases: Append new information to existing notes, update status indicators within note content, or correct and enhance previously recorded details. This is particularly useful for maintaining living documentation that evolves with your processes.

Bulk note retrieval supports workflows that need to process or analyze multiple notes simultaneously. This action fetches multiple note records based on your specified criteria.

Key parameters: Connect with Odoo credentials, set Resource to "Note" and Operation to "Get Many". The Return All toggle fetches all records when enabled. The Limit field (default 50) controls maximum records when Return All is disabled. The Options section provides advanced filtering and property selection.

Practical use cases: Export notes for backup or migration, search notes for specific keywords across your instance, or generate digests of recent notes for team updates. This action is ideal for reporting and data synchronization workflows.

Retrieving existing notes allows you to access stored information for use in other workflow steps. This action fetches a specific note record by its unique identifier.

Key parameters: Requires Odoo authentication, Resource set to "Note", and Operation set to "Get". The Note ID field specifies which note to retrieve. The Options section offers additional retrieval parameters for field selection and filtering.

Practical use cases: Access note content for forwarding to other systems, verify note existence before updating or deletion, or pull historical notes for reporting purposes. Perfect for workflows that need to reference previously captured information.

Removing notes maintains data hygiene and clears outdated information. This action permanently deletes a note record from Odoo.

Key parameters: Requires Odoo credentials, Resource set to "Note", Operation set to "Delete", and the mandatory Note ID field containing the unique identifier of the note to remove.

Practical use cases: Remove resolved action items, clean up temporary notes after processing, or delete outdated information no longer relevant. This keeps your Odoo instance organized and focused on current information.

Notes in Odoo provide a simple way to capture information, and automating their creation ensures important details are recorded without manual effort. This action creates new note records directly from your workflows.

Key parameters: Requires Odoo credentials, Resource set to "Note", and Operation set to "Create". The optional Memo field contains the note content, supporting both fixed text and dynamic expressions from previous workflow steps.

Practical use cases: Log important events from external systems, create meeting summaries from calendar integrations, or record workflow execution details for audit purposes. Notes are lightweight and perfect for capturing information that doesn't fit structured record types.

Modify records in custom modules to keep your proprietary data current. This action updates existing records in any custom Odoo module you've defined, providing flexibility beyond standard resources.

Key parameters: Requires Odoo credentials, Resource set to "Custom Resource", and the Custom Resource Name or ID identifying your custom model. Operation is set to "Update". The Custom Resource ID field specifies which record to modify, and the Update Fields section defines which properties to change.

Practical use cases: Update custom module records from external system changes, sync data bidirectionally with proprietary applications, or batch update custom fields across multiple records. This action unlocks automation for industry-specific or company-specific Odoo modules.

Bulk retrieval from custom resources enables comprehensive data processing workflows. This action fetches multiple records from any custom Odoo module based on your criteria.

Key parameters: Connect with Odoo credentials, set Resource to "Custom Resource", and provide the Custom Resource Name or ID. Operation is "Get Many". The Return All toggle and Limit field control record count. The Options section allows field selection, while the Filters section defines criteria to narrow down returned records.

Practical use cases: Export custom module data for analytics, sync proprietary records to external databases, or generate reports from industry-specific modules. Perfect for scheduled data synchronization with external systems.

Retrieve individual records from any custom Odoo module for use in your workflows. This action fetches a specific record from custom modules you've created in Odoo.

Key parameters: Requires Odoo credentials, Resource set to "Custom Resource", and Custom Resource Name or ID specifying your custom model. Operation is set to "Get". The optional Custom Resource ID targets a specific record. The Options section provides additional configuration for field selection and filtering.

Practical use cases: Fetch custom module data for external reporting, verify record existence before updates, or pull data from proprietary modules for cross-system sync. Essential for workflows that need to reference custom Odoo data.

Remove records from custom modules when they're no longer needed. This action permanently deletes records from any custom Odoo module you've created.

Key parameters: Requires Odoo credentials, Resource set to "Custom Resource", Custom Resource Name or ID identifying your module, Operation set to "Delete", and the mandatory Custom Resource ID field with the record ID to remove.

Practical use cases: Clean up obsolete records from custom modules, process deletion requests for proprietary data, or maintain data hygiene in industry-specific modules. Useful for automated cleanup workflows and data retention policies.

Custom resources extend Odoo's native capabilities, and this action lets you create records for any custom module you've defined. This unlocks automation for any Odoo module, not just standard ones.

Key parameters: Requires Odoo credentials, Resource set to "Custom Resource", and Custom Resource Name or ID specifying your custom model's technical name (e.g., "x_custom_model"). Operation is set to "Create". The Fields section allows you to add field names and values for the new record.

Practical use cases: Create records in custom modules from external data sources, populate industry-specific modules with automated data, or extend standard workflows to proprietary Odoo customizations. This action makes it invaluable for customized Odoo instances.

Keeping contact information current is crucial for effective customer relationship management. This action modifies existing contact records based on data from any source in your workflow.

Key parameters: Requires Odoo credentials, Resource set to "Contact", and Operation set to "Update". The mandatory Contact ID identifies which contact to modify. The Update Fields section allows you to add specific fields and their new values—modify just one property or dozens.

Practical use cases: Update contact status when they become a customer, sync profile changes from your user portal back to Odoo, or enrich contacts with data from third-party services like Dropcontact. The flexibility means you can change only what you need.

When you need to retrieve multiple contacts at once—for batch processing, reporting, or synchronization—this action delivers exactly that capability. Perfect for working with contact segments or entire databases.

Key parameters: Requires Odoo credentials, Resource set to "Contact", and Operation set to "Get Many". The Return All toggle fetches all matching records when enabled. The Limit field (default 50) controls maximum records when disabled. The Options section provides filtering, sorting, and field selection capabilities.

Practical use cases: Export contacts matching specific criteria for marketing campaigns, sync all Odoo contacts to an external email platform daily, or generate reports based on contact segments.

💡 TIP: Start with a reasonable limit during testing to avoid processing thousands of records accidentally. Once your workflow is validated, adjust the limit or enable Return All for production use.

Retrieving contact information from Odoo enables you to use that data in subsequent workflow steps—whether for personalization, validation, or enrichment purposes.

Key parameters: Requires Odoo credentials, Resource set to "Contact", and Operation set to "Get". The optional Contact ID field specifies which contact to retrieve by unique identifier. The Options section provides additional retrieval parameters for filtering and field selection.

Practical use cases: Fetch contact details before sending a personalized email via Gmail, validate if a contact exists before creating a duplicate, or pull contact data to sync with external systems. When combined with conditional logic, this action enables smart workflows that behave differently based on existing contact data.

Removing contacts programmatically is essential for data hygiene workflows, GDPR compliance, or cleaning up test data. This action permanently deletes contact records from Odoo.

Key parameters: Requires Odoo credentials, Resource set to "Contact", Operation set to "Delete", and the mandatory Contact ID field containing the unique identifier of the contact to remove.

Practical use cases: Remove unsubscribed contacts to maintain clean data, process deletion requests for GDPR compliance, or clean up test contacts after workflow validation. Deletion is permanent in Odoo—consider implementing a two-step process where contacts are first archived (via Update) before eventual deletion.

Creating contacts automatically is one of the most impactful automations you can implement. This action allows you to add new contact records to Odoo directly from your n8n workflows, eliminating manual data entry and ensuring every lead or customer gets captured instantly.

Key parameters: Requires Odoo credentials, Resource set to "Contact", and Operation set to "Create". The optional Name field provides the contact's display name. The Additional Fields section allows you to add properties like email, phone, company, address, and any custom fields defined in your Odoo instance.

Practical use cases: Create a contact when someone subscribes to your newsletter, add leads automatically from LinkedIn or other prospecting tools, or sync customers from your e-commerce platform like WooCommerce to Odoo. This action works perfectly as a first step in customer onboarding workflows, ensuring no lead falls through the cracks.