- Home
- Resources
- Integrations
- Odoo ERP Self Hosted
Odoo ERP Self Hosted Zapier integrationAutomate Odoo ERP Self Hosted with Zapier.
The Odoo ERP Self Hosted Zapier integration gives you 10 triggers, 8 actions and 0 searches for your own Odoo server: new leads, tasks, notes or users can start an automation, and every action creates something new in Odoo.
Verified Trustpilot reviews · AI, automation & growth agency
What the Odoo ERP Self Hosted Zapier integration actually does
It links the Odoo instance you host yourself (the product formerly called OpenERP) to Zapier, a tool that runs automations between apps without code. Something new appears in Odoo, Zapier notices it on its next check and passes it to another app. Or the reverse: another app hands Zapier some data, and Zapier creates the matching item in Odoo.
Three results people usually build first. A sales follow-up that writes itself: New Lead/Opportunity picks up each new lead and Create Project Task turns it into a task for the team. A shared agenda that stays in sync: a booking made elsewhere becomes an Odoo appointment through Create Calendar Event. An onboarding trail: New User tells another tool that someone joined your Odoo, so the welcome steps start without a reminder.
Now the limits, because they shape what you can plan. All 8 actions create; none of them edits or deletes an item that already exists. There is no search step either, so a Zap cannot look up an existing Odoo record to reuse it. And all 10 triggers work by checking at intervals, none is instant. If your scenario needs updates or lookups, that is the moment to compare tools: the Make vs Zapier and n8n vs Zapier pages are a good place to start.
One detail specific to this app: most operations depend on an Odoo module being installed on your instance. A calendar trigger expects Calendar, a lead trigger expects CRM, and so on. The notes below say which one each step relies on.
Zapier vocabulary in one minute
Seven words come back on every line of this page. Here is what each one means in plain English.
- Zap
- The automation you build in Zapier: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for that event and nothing else.
- Action
- What the Zap does once it has started: the step that writes, sends or creates something on your behalf.
- Task
- The unit Zapier bills you for: one action your Zap completed successfully. The number on your plan counts those.
- Polling trigger
- A trigger Zapier checks on a timer. It asks the app for its latest items and keeps only the ones it has not seen yet.
- Instant trigger
- A trigger the app reports itself, the moment the event happens, so nothing waits for the next check. Odoo has none here.
- Filter
- A step that lets the Zap continue only when what arrived matches the condition you set, and stops it otherwise.
What it really costs in tasks
Watching Odoo is free. The trigger never costs a task, and neither does each check Zapier makes for new items. You pay only when an action succeeds, and a failed action is not counted.
- Trigger checksFree, never counted
- Each successful action1 task
- Free plan100 tasks per month, two-step Zaps
- Paid plan needed?No for this app, yes for multi-step Zaps
Each successful action is one task, so a Zap with three actions uses three times what a one-action Zap uses. The free plan gives you 100 tasks a month and checks every 15 minutes, but it builds two-step Zaps only: one trigger, one action. Add a second action or a filter and you have a multi-step Zap, which needs a paid plan. Good news: Odoo ERP Self Hosted is not reserved to paid plans, so it works on the free one.
Connect your Odoo instance to Zapier in 3 steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. A connection is your Odoo account linked once, then reused by every Zap step that touches Odoo.
- 02
Pick Odoo ERP Self Hosted
Type the app name in the dialog, select Odoo ERP Self Hosted, then click Add connection. Make sure you pick the self-hosted version: this one talks to the server you run yourself.
- 03
Sign in and grant access
Sign in to Odoo in the tab that opens and let Zapier access the account. Use an Odoo login that can read and write the items your Zaps will touch, including those you did not create yourself.
Your first Zap: from new lead to task and meeting
GoalEach new lead in Odoo creates a follow-up task in a project and a slot in the Odoo calendar.
- 01
Pick the trigger
Create a Zap, choose Odoo ERP Self Hosted as the app that starts it and New Lead/Opportunity as the event. Your instance needs the CRM module for this one.
- 02
Set it up and test it
Select your Database, then run the test. Zapier brings back the three most recent leads from your account, so you map the next steps on a real one rather than an empty example.
- 03
Add the task
Add an action, choose Create Project Task, pick the Database again, and fill the task with what the lead carries. This step relies on the Project module.
- 04
Add the calendar slot
Add a second action with Create Calendar Event, which needs the Calendar module. With two actions this is now a multi-step Zap, so it runs on a paid plan.
- 05
Test, then publish
Run each step once and read what came back in Odoo. When the task and the event look right, click Publish to switch the Zap on.
The 10 Odoo ERP Self Hosted triggers
10 events start a Zap when something happens in Odoo ERP Self Hosted. Zapier checks for them at the interval your plan allows.
New Database
Polling triggerIn Zapier“Triggers when you add a new database.”
Fires when a new database is added to your Odoo server. Handy if you run several databases on one instance and want the people who look after them to hear about a new one without checking the server themselves.
New Calendar Event
Polling triggerIn Zapier“Triggers when you add a new Calendar Event. You will need to have the Calendar module installed.”
Starts your Zap whenever someone adds an appointment to the Odoo calendar. The event lands in the next step with what it carries, ready to be copied into another agenda, a chat or a spreadsheet.
New Lead/Opportunity
Polling triggerIn Zapier“Triggers when you add a new Lead/Opportunity. You will need to have the CRM module installed.”
Picks up each lead or opportunity that appears in your Odoo pipeline. This is usually the first trigger sales teams wire up, because a lead that sits unnoticed in the CRM is the one that goes cold.
New Module
Polling triggerIn Zapier“Triggers when you add a new model.”
Reacts when a new model, meaning a kind of record, appears in your Odoo instance. It is an admin trigger rather than a business one.
New Note
Polling triggerIn Zapier“Triggers when you add a new Note. You will need to have the Note module installed.”
Catches every note added in Odoo and hands it to the next step. Notes are often where meeting minutes or quick reminders live, so this is a simple way to get them out of Odoo and in front of people.
New Product
Polling triggerIn Zapier“Triggers when you add a new Product. You will need to have the ECommerce module installed.”
Notices each product added to your Odoo catalogue. If your catalogue feeds other channels, this keeps them aware of new items without someone exporting a list by hand.
New Record
Polling triggerIn Zapier“Triggers when a new record is added in a model (choose any model you have installed).”
The catch-all trigger: it watches any model installed on your instance, so you can react to records the other triggers do not cover, such as invoices or contacts if those modules are there.
New Project Task
Polling triggerIn Zapier“Triggers when you add a new Project Task. You will need to have the Project module installed.”
Fires on each task created in an Odoo project. Teams that plan in Odoo but talk elsewhere use it so a new task does not wait for someone to open the project view.
New Calendar Todo
Polling triggerIn Zapier“Triggers when you add a new Calendar Todo. You will need to have the Calendar module installed.”
Spots each to-do added through the Odoo calendar. Smaller than an event, a to-do is often a personal reminder, and this trigger is how you get it out of Odoo and into the tool people actually check.
New User
Polling triggerIn Zapier“Triggers when you add a new User. You will need to have the Users module installed.”
Tells your Zap that a new user account exists in Odoo. That is the starting point of most onboarding and access-control automations around an ERP.
The 8 Odoo ERP Self Hosted actions
Odoo ERP Self Hosted gives you 8 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Calendar Event
ActionIn Zapier“Create a new Calendar Event.”
Books an appointment in the Odoo calendar using the date and details the previous steps carry.
Create Lead/Opportunity
ActionIn Zapier“Create a new Lead/Opportunity.”
Drops a new lead or opportunity into your Odoo CRM from whatever started the Zap, a form, a chat or an ad platform.
Create Note
ActionIn Zapier“Create a new Note.”
Saves a note in Odoo, a quick way to keep a written trace of something that happened in another app.
Create Product
ActionIn Zapier“Create a new Product.”
Adds an item to the Odoo product catalogue, filled with what an earlier step provided.
Create Record
ActionIn Zapier“Create a new record in a model of your choice.”
The flexible action: it creates a record in any model you choose, which covers the cases the seven dedicated actions leave out.
Create Project Task
ActionIn Zapier“Create a new Project Task.”
Writes a task into an Odoo project, so work requested elsewhere shows up where the team plans.
Create Calendar Todo
ActionIn Zapier“Create a new Calendar Todo.”
Puts a to-do on the Odoo calendar, lighter than a full event and fine for reminders.
Create User
ActionIn Zapier“Create a new User.”
Opens a new user account in Odoo from data another app passed along, for example an HR tool.
When an Odoo Zap breaks
Zapier attaches no help article of its own to this app, so the problems you will meet are the ones every Zap shares.
They are easy to avoid once you know them, and most of them come from how polling triggers work. If a Zap still behaves oddly, the Zapier troubleshooting page is the next stop.
Old records are never picked up
A Zap only reacts to what happens after you switch it on. Leads or tasks created before that stay where they are, and moving them is a separate job.A Zap that restarts itself
A Zap triggered by New Note that runs Create Note on the same Database sets itself off again and again, and burns through your tasks.A bulk import that seems ignored
After a migration or a mass import into Odoo, the trigger suddenly returns a huge batch, and Zapier's flood protection can hold it back.Why an item never fires twice
Zapier remembers what it has already seen on a polling trigger, so the same Odoo item will not start your Zap a second time.
Need help automating Odoo ERP Self Hosted with Zapier?
A person reads every message.



