Resources · Make integration

Odoo Make integrationAutomate Odoo with Make.

The Odoo Make integration gives you 20 modules to work with, and none of them needs code. 16 of them act on your data, 4 look things up. This page shows what each one does, how to plug your account in, and how to get a first scenario running on its own.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Odoo Make integration actually do?

It hooks your Odoo account up to Make so that a scenario, the automation you build in Make, can read and write your Odoo records without you. Make gives you 20 Odoo modules: create, fetch, update, delete and list inventory types, inventories, batches tracking and leads. Each module is one brick of that chain, an action that writes or a search that looks something up.

Leads that land without retyping. A form on your site, an ad campaign, a list a partner sends over: the scenario picks the row up and Create a Lead writes it into Odoo, so sales sees the contact the day it arrives.

Stock counts opened before anyone walks the floor. Create an Inventory sets the count up in Odoo from what another tool announced, and List Inventories reports on the ones already running.

Batch records that keep up. A delivery arrives with its batch reference and Create a Batch Tracking logs it; a lab result comes back and Update a Batch Tracking carries it onto the right batch.

Two things Make will not do here. No Odoo module is a trigger, the kind of module that starts a scenario on its own, so nothing on the Odoo side wakes anything up: the scenario runs on a schedule or starts from another app. And the Leads modules only work once the CRM app is installed in Odoo, which is the documentation's own warning. Each module run counts as one operation on your plan, so a search that hands back a long list is worth sizing before you switch anything on.

Odoo lives on the other side of the fence too. The Odoo n8n integration covers the equivalent node, n8n vs Make lays out the criteria, and Make troubleshooting is where the usual connection headaches end up.

Connect

How do you connect Odoo to Make?

  1. 01

    Create an API key in Odoo

    In Odoo, open the My Profile menu, go to the Account Security tab and click New API Key. Copy the value it shows and keep it somewhere safe. That key is what lets Make speak to your account without a human typing a password each time.

  2. 02

    Add an Odoo module and open the connection

    In your scenario, add any Odoo module, then click Create a connection. A connection is your Odoo account linked to Make once and reused by every Odoo module after that. The Connection name field is optional, though naming it helps if you juggle several accounts.

  3. 03

    Fill in the four fields and save

    Host takes your Odoo hostname, Login your account credentials, API-Key/Password the key you just copied or your usual password, and Database the name of the database you want Make to work in. Then click Save.

First scenario

Your first scenario, step by step

GoalAt the interval you set, Make lists the leads in your Odoo database and writes the same update on each one.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario, then click the + in the middle of the canvas to drop in the very first module.

  2. 02

    Add List Leads

    Search for Odoo by name, pick List Leads from the list of modules and, the first time around, click Create a connection to link your account.

  3. 03

    Set the module up

    Fill in the fields the module shows. With the connection in place, Make reads what your database actually holds instead of asking you to type it from memory.

  4. 04

    Add Update a Lead

    Click the + on the right of the first module, add Update a Lead, then map its fields to the lead that List Leads just handed over.

  5. 05

    Test it with Run once

    Hit Run once. The scenario fires a single time and each module shows you the bundles it received, the items travelling down the chain. It writes for real, so start on a database you can afford to disturb.

  6. 06

    Schedule it and switch it on

    Open the scheduling on the first module, the little clock that decides how often the scenario looks. A new scenario runs every 15 minutes by default, so pick the rhythm your Odoo deserves, then switch the scenario on.

Modules

The 20 Odoo modules, one by one

Odoo gives you 20 modules in 5 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Inventory Types

4 modules
Odoo1

Create an Inventory Type

Action

In MakeCreates a new inventory type.

Adds a brand new inventory type to Odoo from data the scenario is already carrying, so nobody has to open the interface to declare it.

When to use it
a new product family starts moving through the warehouse and you want it on the books the same day.
Watch out
it creates on every run, so a search placed in front of it saves you from two types wearing the same name.
Odoo2

Get an Inventory Type

Action

In MakeRetrieves an existing inventory type.

Fetches one inventory type that already exists and hands it to the rest of the scenario, read only.

When to use it
a spreadsheet row mentions a type and you need Odoo's own version of it before the scenario decides anything.
Watch out
it never writes. Point it at something that left Odoo and the modules behind it get nothing to chew on.
Odoo3

Update an Inventory Type

Action

In MakeUpdates an inventory type.

Rewrites an inventory type that is already in Odoo with the values your scenario carries.

When to use it
your naming convention changed and you would rather fix every type from a sheet than click through Odoo one by one.
Watch out
it needs a type that exists. When all you have is a label, run List Inventory Types first and feed it the result.
Odoo4

List Inventory Types

Search

In MakeSearches for inventory types or lists them all.

Searches your inventory types, or hands over the whole set, one bundle per type.

When to use it
right before creating anything, to check whether the type is already sitting in Odoo.
Watch out
a search gives back zero, one or several items. Every module placed after it runs once per item, and each of those runs is one operation.

Inventories

5 modules
Odoo5

Create an Inventory

Action

In MakeCreates a new inventory.

Opens a new inventory in your Odoo database straight from the scenario, with nobody logging in.

When to use it
a stock count is planned in the warehouse tool and you want Odoo ready before the team walks the aisles.
Watch out
nothing checks for a twin. If the scenario can fire twice on the same input, look the inventory up first.
Odoo6

Get an Inventory

Action

In MakeRetrieves an existing inventory.

Pulls back one inventory you already have so the following modules work from what Odoo actually holds, not from a copy that drifted.

When to use it
a support agent pastes a reference into a chat and the scenario needs the matching record before answering.
Watch out
reading is all it does. Any change has to go through Update an Inventory further down the chain.
Odoo7

Update an Inventory

Action

In MakeUpdates an inventory.

Applies a change to an inventory that is already in Odoo, using whatever the previous module handed over.

When to use it
counted quantities come back from a barcode app and you want Odoo to match the shelf before the shift ends.
Watch out
what you map is what gets written. Leave a value out of the mapping and the scenario simply has nothing to say about it.
Odoo8

List Inventories

Search

In MakeSearches for inventories or lists them all.

Searches inventories, or returns all of them, then sends each one down the chain as its own item.

When to use it
a dashboard needs the current state of every inventory before it gets written anywhere else.
Watch out
the wider the answer, the more operations the rest of the scenario burns. Narrow the search before you widen it.
Odoo9

Delete an Inventory

Action

In MakeDeletes an inventory.

Removes an inventory from Odoo. Neither the module nor the scenario has an undo button.

When to use it
a draft count was created by mistake and you want it gone before anyone starts filling it in.
Watch out
Run once deletes for real, exactly like a live run. Test it against a record you can afford to lose.

Batches Tracking

5 modules
Odoo10

Create a Batch Tracking

Action

In MakeCreates a new batch tracking.

Records a new batch tracking entry in Odoo from the scenario, so a batch that exists on the production sheet also exists in the system.

When to use it
a supplier delivery shows up with its own batch reference and you want that reference in Odoo the moment it is scanned.
Watch out
each run adds an entry, so a scenario that passes twice over the same delivery leaves you with two.
Odoo11

Get a Batch Tracking

Action

In MakeRetrieves an existing batch tracking.

Brings one existing batch tracking entry into the scenario so what follows can read whatever Odoo knows about that batch.

When to use it
a customer asks where a batch came from and the answer has to be built without opening Odoo.
Watch out
it handles one entry at a time. To sweep several, put List Batches Tracking in front of it.
Odoo12

Update a Batch Tracking

Action

In MakeUpdates a batch tracking.

Writes a change onto a batch tracking entry that Odoo already holds.

When to use it
a quality check comes back from the lab and the batch has to carry that result before the goods ship.
Watch out
the entry has to exist. Chain it behind a search or a Get rather than guessing at a reference.
Odoo13

List Batches Tracking

Search

In MakeSearches for batches tracking or lists them all.

Searches your batch tracking entries, or lists every one of them, one item per entry.

When to use it
an audit asks for everything logged on a product line and exporting by hand is not how you want to spend the afternoon.
Watch out
the series it returns can be long. Each entry restarts the modules behind it, so count what that costs before you switch on.
Odoo14

Delete a Batch Tracking

Action

In MakeDeletes a batch tracking.

Deletes a batch tracking entry from Odoo, for good.

When to use it
a test batch slipped through during a dry run and it is polluting what your team reads.
Watch out
put a search in front and look at what comes back before you wire the delete, because the module will not ask twice.

Leads

5 modules

You need to install the CRM app in Odoo to ensure the necessary table is created and fields are available. For more information, refer to Apps and modules in Odoo documentation.

Odoo15

Create a Lead

Action

In MakeCreates a new lead.

Creates a lead in Odoo from whatever the scenario is holding, a form reply, a row, a message, so sales sees it without retyping anything.

When to use it
a webinar sign-up or a quote request has to land in Odoo while the prospect is still warm.
Watch out
the Leads modules only find their table once the CRM app is installed in Odoo. Install it first or the fields will not be there.
Odoo16

Get a Lead

Action

In MakeGets a single lead by ID.

Gets one lead by its ID and drops it into the scenario, so what follows works from the record itself rather than from a stale copy.

When to use it
a notification carries nothing but an identifier and the scenario needs the whole lead before it posts anything.
Watch out
the ID is the way in. Without one, go through List Leads and pick from what comes back.
Odoo17

Update a Lead

Action

In MakeUpdates a lead.

Changes a lead that is already in Odoo with data the scenario picked up somewhere else.

When to use it
an enrichment tool returns a company size or a phone number and you want it on the lead, not in a separate sheet.
Watch out
it overwrites the values you map and stays quiet about the rest, which is handy as long as you know what you mapped.
Odoo18

List Leads

Search

In MakeLists all leads.

Lists the leads in your Odoo database and passes them on, one bundle per lead.

When to use it
it is the usual opening module when the scenario starts on a schedule rather than on something happening inside Odoo.
Watch out
it lists them all, so everything behind it runs once per lead. Look at the schedule and the follow-up modules before you turn it on.
Odoo19

Delete a Lead

Action

In MakeDeletes a Lead.

Takes a lead out of Odoo. Once the scenario has run, the record is not coming back.

When to use it
a duplicate slipped in through two forms and you want the copy gone before two people call the same contact.
Watch out
sending List Leads straight into this module deletes everything it found. Check the bundles with Run once first.

Other

1 module
Odoo20

Make an API Call

Action

In MakePerforms an arbitary authorized API call.

Reaches an endpoint of the Odoo API that none of the other modules covers, reusing the connection you already set up.

When to use it
what you need sits outside inventory types, inventories, batches tracking and leads, and you would rather stay inside the same scenario.
Watch out
the Odoo API documentation is the list of what you can call. Make will not suggest it for you.
Need help

Need help automating Odoo with Make?

A person reads every message.

FAQ

Questions that come up next

01Is the Odoo Make integration free?
Yes. Odoo is a standard app in Make, so it is available from the Free plan and the modules cost nothing on top. What the Free plan limits is the scale: 2 active scenarios, a floor of 15 minutes between two scheduled runs, and 5 minutes of execution per run. Paid plans bring the interval down to 1 minute and lift the cap on active scenarios. Your Odoo subscription is a separate bill, and Make has no say in it.
02What do you need to connect Odoo to Make?
An Odoo account, and four things that come from it: the hostname, your login, an API key or your password, and the name of the database you want to work in. The key is generated inside Odoo, from your profile menu, in the Account Security tab, with the New API Key button. Copy it and store it somewhere safe. The documentation asks for no other prerequisite. Everything after that happens in Make, the first time you drop an Odoo module into a scenario.
03Does Odoo trigger a scenario in real time?
No, because Odoo has no trigger module in Make. Nothing on the Odoo side wakes a scenario up. You start it another way: put the clock on a search module such as List Leads and let Make look at the interval you choose, or start the scenario from another tool with a Make webhook, an address that tool calls the second something happens on its side. A new scenario runs every 15 minutes by default, and the Free plan keeps that as its floor.
04What if a module is missing or a limit gets in the way?
Make an API Call covers most gaps. It calls any endpoint of the Odoo API with the same connection, so you are not boxed in by the 20 modules on the list. One limit is worth knowing before you start: the Leads modules need the CRM app installed in Odoo, otherwise the table and the fields they expect are simply not there. And when a large slice of the process lives outside Odoo, handing that slice to another app in the same scenario is usually cleaner.
05Make or n8n for Odoo?
It depends on who will keep the thing alive. Make runs in a browser, you pick modules from a catalogue, and a first scenario gets built in an afternoon. n8n is worth a look when the team wants to host and version the automation itself. Both cover Odoo, so the app is rarely what decides. Ask the real question instead: does anyone on your side want to own a server? If the answer is no, Make is the short road.
Hack'celeration Lab

Get our weekly automation tips.

No spam. Unsubscribe anytime.