Why connect n8n to Odoo?
Odoo is where your business runs — sales orders, invoices, inventory movements, CRM updates. n8n is where your automation logic lives — routing data between systems, triggering notifications, synchronising records across tools. Connecting the two unlocks fully event-driven automation: no polling, no scheduled batch jobs, no stale data.
The challenge is that Odoo does not emit webhooks out of the box. The KSROlabs Webhooks & REST API module adds this capability — every record creation, update, or deletion in Odoo can instantly fire an HTTP payload to any n8n workflow.
For teams also using AI agents or LLM-powered n8n nodes, the KSROlabs MCP Server provides a complementary connection method suited to conversational, query-driven access to Odoo data.
Two ways to connect n8n to Odoo
KSROlabs offers two modules for connecting external tools to Odoo. Here is how they compare for n8n specifically:
Webhooks & REST API module
Best for event-driven automation. Fires an HTTP POST to n8n the instant a record is created, updated, or deleted in Odoo. No polling. Supports domain filters, field selection, and retry logic. The right choice for order processing, invoice sync, and operational workflows.
MCP Server module
Best for AI-driven workflows. If your n8n workflow includes an LLM node (e.g. OpenAI, Claude) that needs to query or reason about Odoo data, the MCP Server gives those AI nodes structured access to Odoo records and schema. Ideal for AI-assisted triage, report generation, and intelligent routing.
The steps below cover the Webhooks & REST API approach — the most common choice for n8n operational automation. If you want the MCP approach, see the MCP Server product page.
Step-by-step setup guide
Follow these 6 steps to connect n8n to Odoo with real-time event triggers.
Install the Webhooks & REST API module from the Odoo App Store
Purchase the KSROlabs Webhooks & REST API module from the Odoo App Store. Install it in your Odoo instance via Apps → Upload Module, or directly through the App Store. The module adds a Webhooks menu under Settings → Technical.
Create a webhook endpoint in Odoo Settings → Webhooks
Navigate to Settings → Technical → Webhooks and click "New". Give your webhook a name (e.g. "n8n Sale Order Created") and set the target URL to the Webhook trigger URL from your n8n workflow. Select the authentication method — Bearer token is recommended.
Configure the trigger: model = sale.order, event = record_created
In the webhook configuration, set the Model to "sale.order" and the Event to "record_created". Optionally add domain filters to restrict which records fire the webhook — for example, only confirmed orders over a certain value. Save the webhook record.
In n8n, create a Webhook trigger node pointing at your endpoint
In n8n, add a "Webhook" trigger node to your workflow. Copy the n8n webhook URL and paste it into the Target URL field in your Odoo webhook configuration. Set the HTTP method to POST. Activate the n8n workflow so it is listening for incoming requests.
Add an Odoo action node using the REST API key for write-back
To write data back to Odoo from n8n, use the n8n HTTP Request node with your Odoo REST API endpoint. Create a dedicated API key in Odoo Settings → MCP Server (the same module exposes a REST API). Use this key in the Authorization header of your n8n HTTP Request nodes.
Test: confirm a sale order in Odoo and watch n8n fire
Create a new sale order in Odoo and confirm it. Switch to n8n and check the execution log — you should see the webhook payload arrive within seconds. Verify the payload contains the expected fields, then connect downstream n8n nodes to process the data (e.g. send a Slack message, create a row in Google Sheets, update a CRM record).
Frequently asked questions
Does n8n have a native Odoo connector?
n8n includes a built-in Odoo node that uses the Odoo XML-RPC API. It works for basic CRUD operations but does not support real-time event triggers — it relies on polling. The KSROlabs Webhooks & REST API module adds true event-driven webhooks that fire instantly when records change in Odoo, which is significantly more efficient for automation workflows.
Should I use MCP or Webhooks for n8n automation?
It depends on your workflow type. Use the Webhooks & REST API module if you need event-driven automation — e.g. trigger an n8n workflow the moment a sale order is confirmed or an invoice is paid. Use the MCP Server if your n8n workflow includes AI/LLM nodes that need to query or reason over Odoo data conversationally. For most operational automation (order processing, notification routing, sync workflows), Webhooks is the right choice.
Can n8n write back to Odoo?
Yes. Use n8n's HTTP Request node to call the KSROlabs REST API endpoints. Create a scoped API key in Odoo with the write permissions your workflow needs, then use it as a Bearer token in the Authorization header. The REST API supports create, update, and delete operations on any Odoo model that the key's scope allows.
What Odoo events can trigger n8n?
The KSROlabs Webhooks module supports record_created, record_updated, and record_deleted events on any installed Odoo model. You can set up separate webhooks for different models and events — for example, one webhook for new sale orders, another for invoice state changes, and another for new CRM leads. Domain filters let you restrict triggers to records matching specific conditions.
Is this better than Zapier for Odoo?
For most Odoo automation use cases, yes. n8n with the KSROlabs Webhooks module gives you real-time event triggers (not polling), self-hosted deployment options, unlimited workflow executions, and full programmatic control over data transformation. Zapier's Odoo integration relies on polling and has significant per-task pricing at scale. n8n Cloud or self-hosted n8n with KSROlabs modules is typically both faster and more cost-effective.