Resources · Make integration

Axelor Make integrationAutomate Axelor with Make.

Records created, edited or deleted in Axelor can start work in your other tools. The Axelor Make integration offers 24 modules, including 3 triggers and 18 actions. This page walks you through the connection, a first scenario and each module in plain words.

Try the Axelor integration on MakeSee the 24 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Axelor Make integration do for you?

The Axelor Make integration links your Axelor account to Make, so records and files move between Axelor and your other apps without retyping. You build a scenario, the automation itself, by chaining modules: a trigger that notices a change, then actions that create, update, read or delete data.

Keep other tools in step with Axelor. Watch New / Updated Records picks up every new or edited record, and Update record or Create / Update record writes the change where it belongs. A price corrected in Axelor no longer waits for someone to copy it into a spreadsheet.

Feed Axelor from the outside. A signed form, a web order or a supplier email can become an Axelor record through Create record, and its PDF can follow with Add attachment or Upload file. Nobody reopens the document to key it in.

Never lose track of a deletion. Instant deleted record reacts as soon as a record disappears, which suits an audit log or a warning sent to the team.

Limits are worth knowing upfront. Five modules carry Deprecated in their name and are kept for older scenarios, and the doc describes most of the newer modules by their name only. When an operation has no ready-made module, Make an API Call reaches the Axelor API with the same connection. If you are still choosing a tool, the n8n vs Make comparison lays out the criteria, the Make training covers scenario basics, and Make troubleshooting helps when a run fails.

Connect

How do you connect Axelor to Make?

  1. 01

    Create an API token in Axelor

    In Axelor, open the Connect application, click Profile at the bottom of the left sidebar, then the API access tab. Click Add token, give it a label, pick organizations:read in the scope list, click Save and copy the token.

  2. 02

    Add an Axelor module in Make

    Place any Axelor module in your scenario and click Create a connection. A connection is your Axelor account linked to Make once, then reused by every Axelor module. Filling the Connection name field is optional, yet handy with several accounts.

  3. 03

    Paste your credentials

    Enter the credentials you copied from Axelor, or follow the instructions Make shows on screen, and confirm. From then on, the module fields offer the Axelor objects Make can read, a quick sign that the link is working.

First scenario

Your first scenario with Axelor

GoalWhen a new record appears in Axelor, Make lists its attachments and downloads each file for the next step.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big +. Search for Axelor and choose Watch a New Record as the first module, then link your account with Create a connection.

  2. 02

    Set up the trigger

    Fill in the trigger fields. Once the connection exists, Make offers the Axelor objects it can read, so you pick the kind of record to watch from a list instead of typing its name.

  3. 03

    Add List attachments

    Click the + on the right of the trigger and add List attachments. Map the record coming from Watch a New Record, so the module looks at the files of that exact record.

  4. 04

    Add File download

    Add File download after it and map each attachment found. Every file becomes a bundle, one item passing from a module to the next, ready for a storage or email module you add later.

  5. 05

    Test with Run once

    Create a test record with a file in Axelor, then click Run once. Read the bundles each module received and check that the file came through.

  6. 06

    Schedule and switch on

    Click the clock on the first module. A new scenario runs every 15 minutes by default, the minimum on the Free plan. Save, then switch the scenario on so it runs without you.

Triggers

What can start an Axelor scenario?

3 modules start a scenario when something happens in Axelor. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Axelor as soon as it happens.

Axelor1Instant deleted record

Instant deleted record

Instant trigger

In Make“Triggers when a record is deleted from Axelor”

Your scenario wakes up the moment someone removes a record in Axelor, so the deletion leaves a trace in another tool instead of vanishing silently. This is the only instant trigger of the app.

How it fires
instant, Axelor calls Make through a webhook as soon as the record is deleted, with no schedule to wait for.
When to use it
an audit sheet or a team channel must hear about every customer, product or order that gets removed.
Watch out
the setup has one more step than the other modules; click Create a webhook first, then Create a connection.
Axelor2Watch a New Record

Watch a New Record

Scheduled trigger

In Make“Watches newly created records.”

New entries in Axelor reach the scenario one by one: each record created since the previous check arrives as its own bundle, ready to be copied, announced or enriched elsewhere.

How it fires
scheduled, Make checks Axelor on the scenario's schedule, every 15 minutes by default and never more often than that on the Free plan.
When to use it
a new customer or a fresh sales order should open a folder, a task or a message in another app.
Watch out
this trigger follows creations only; edits to existing records call for Watch New / Updated Records.
Axelor3Watch New / Updated Records

Watch New / Updated Records

Scheduled trigger

In Make“Watches newly created or updated records.”

Both kinds of change land in the scenario here: a record that did not exist before and a record someone edited. Each one travels as a separate bundle.

How it fires
scheduled, Make checks Axelor on the scenario's schedule, so a change shows up at the next run rather than the second it happens.
When to use it
a status, a price or an address changed in Axelor has to be mirrored in a spreadsheet or a CRM.
Watch out
if a later module of the same scenario writes to the records you watch, that edit comes back at the next run as an update, and the scenario keeps feeding itself.
Modules

What can Make do in Axelor?

Axelor gives you 21 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Axelor1

Create a Record - Deprecated

Action

In Make“This module creates a record in Axelor.”

This older module adds a record to Axelor. Make still lists it, with the Deprecated tag right in its name, next to the newer creation modules.

When to use it
only while reading or adjusting a scenario that someone already built with it.
Watch out
for a new scenario, pick Create record in the same Axelor list, the module without the Deprecated tag.
Axelor2

Delete a Record - Deprecated

Action

In Make“This module deletes record from Axelor.”

Removal of an Axelor record, through the older family of modules that Make now labels Deprecated. You will mostly meet it in scenarios built some time ago.

When to use it
you open an inherited scenario and need to understand what it erases before changing anything.
Watch out
a deletion cannot be undone from Make, and new builds rely on Delete record, the current module for this job.
Axelor3

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

A way out when none of the listed modules fits: any endpoint of the Axelor API becomes reachable from the scenario, with the connection you already set up.

When to use it
an operation you run in Axelor has no ready-made module in Make.
Watch out
you write the request yourself, so keep the Axelor API documentation open and test with Run once before switching the scenario on.
Axelor4

Read a Record - Deprecated

Action

In Make“Reads specified record from Axelor using record ID.”

Given a record ID, this module fetches that Axelor record and hands its data to the next module. Its name carries the Deprecated tag.

When to use it
maintaining an older scenario where it already sits between a trigger and an action.
Watch out
it needs the ID mapped from an earlier module; when you rebuild, Read a record is the current module in the list.
Axelor5

Update a Record - Deprecated

Action

In Make“Updates a record in Axelor.”

Changes to an existing Axelor record, written by the older module that Make keeps in the list with Deprecated in its name.

When to use it
you inherit a scenario built with it and simply want to check which values it overwrites.
Watch out
when you rebuild that step with Update record, swap one module at a time and test each change with Run once.
Axelor6

Search Records - Deprecated

Search

In Make“Searches records from Axelor with appropriate filter.”

Looking for Axelor records that match a filter was once done with this module. As a search, it returns zero, one or several bundles to the scenario.

When to use it
reading an older scenario that relies on it to find a customer before acting.
Watch out
the Deprecated tag means new scenarios are better served by Find records, the current search in the same list.
Axelor7

Add attachment

ActionIn the docs only

With this module a file ends up on an Axelor record, so the document sits next to the customer, the order or the invoice it belongs to.

When to use it
a signed quote or a delivery note arrives in another app and has to reach the right record.
Watch out
on the Free plan Make handles files up to 5 MB, which rules out some large scanned contracts.
Axelor8

Create / Update record

ActionIn the docs only

One module for two cases, as its name says: it writes a record to Axelor, whether that record is new or already there.

When to use it
contacts arrive from a form and you cannot tell in advance whether the person already exists in Axelor.
Watch out
the doc does not explain how it spots an existing record, so run it once on a record you know and read the bundle before going live.
Axelor9

Create custom record

ActionIn the docs only

Custom records are the target here, as the module name says, rather than the standard records handled by Create record.

When to use it
your Axelor holds a model built for your trade, such as equipment or service tickets, and the scenario must feed it.
Watch out
once connected, Make lists the objects it can read; if yours is missing, Make an API Call is the fallback.
Axelor10

Create record

ActionIn the docs only

The everyday module for adding a customer, a product or an order to Axelor from data that another app has just sent.

When to use it
a web order, a signed form or a new lead must become an Axelor record without anyone retyping it.
Watch out
if the source may send the same person twice, Create / Update record deserves a look before you settle on this one.
Axelor11

Delete record

ActionIn the docs only

An Axelor record disappears at the exact point of the scenario where you place this module, without anyone opening the app.

When to use it
a cancelled order or a test entry has to go once another tool confirms it.
Watch out
nothing brings the record back afterwards, so test the scenario on a dummy record with Run once before letting it touch real data.
Axelor12

File download

ActionIn the docs only

A file stored in Axelor comes out as data that the next module can store, send or attach somewhere else.

When to use it
an invoice or a contract kept in Axelor has to land in a shared drive or an email.
Watch out
the Free plan caps files at 5 MB and data transfer at 512 MB, and heavy scans use up that allowance.
Axelor13

File listing

ActionIn the docs only

Before downloading anything, this module shows which files Axelor holds, so the scenario knows what is there to fetch.

When to use it
ahead of File download, when you need to pick the right document instead of guessing its reference.
Watch out
the doc says nothing about which files it covers or how many it returns, so read the output of a test run before building on it.
Axelor14

Find records

SearchIn the docs only

Searching Axelor for the records that match your criteria is the job here, and each result travels down the scenario as a separate bundle.

When to use it
checking whether a supplier or a customer already exists before creating anything.
Watch out
with several results, every module placed after it runs once per result, and each run counts as an operation on your plan.
Axelor15

List attachments

SearchIn the docs only

You get the files attached to an Axelor record, so the scenario can handle them one after the other.

When to use it
right after a trigger on a new order, to collect the documents that came with it.
Watch out
being a search, it may return nothing for a record without files and several bundles for a well-stocked one.
Axelor16

Make a Business Service Call

ActionIn the docs only

Your scenario can call a business service of your Axelor instance, beyond plain reading and writing of records.

When to use it
your Axelor team has set up a service that computes or checks something, and the scenario needs its answer.
Watch out
the doc gives no description of this module; ask whoever runs your Axelor which services exist, then try the call with Run once.
Axelor17

Read a record

ActionIn the docs only

Full details of one Axelor record become available to the next modules, including data the trigger did not carry.

When to use it
a trigger gives you an ID and you need the customer's details to write a message.
Watch out
it reads one record at a time; to gather several, Find records is the better choice.
Axelor18

Run action

ActionIn the docs only

Launching an Axelor action from a scenario is what this module is for, so a step people usually start by hand can follow an event elsewhere.

When to use it
a payment or a signature recorded in another tool should set off the matching step in Axelor.
Watch out
the doc does not describe which actions it accepts; check the list Make offers once connected and try it on a test record.
Axelor19

Update custom record

ActionIn the docs only

Values of an existing custom record in Axelor change here, the natural follow-up of Create custom record once the entry exists.

When to use it
a status on a model specific to your business moves forward in another app and Axelor must follow.
Watch out
a scenario started by Watch New / Updated Records that edits the watched records will see its own changes come back.
Axelor20

Update record

ActionIn the docs only

An Axelor record stays current as this module writes the new values another tool has just produced.

When to use it
a payment confirmed in your billing tool should flip the matching order in Axelor.
Watch out
the module needs to know which record to change, so place Find records or a trigger before it and map the result.
Axelor21

Upload file

ActionIn the docs only

A document from an email, a form or a storage app gets sent into Axelor, with no manual import.

When to use it
a supplier's PDF must be available in Axelor once it reaches your inbox.
Watch out
the doc does not say how it differs from Add attachment; when the file belongs to a specific record, try Add attachment first.
Need help

Need help automating Axelor with Make?

A person reads every message.

FAQ

Axelor and Make: common questions

01Is the Axelor Make integration free?
Yes, on the Make side. Axelor is a standard app, so its modules work from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, lift the cap on active scenarios and count usage in credits each month. The Axelor subscription itself is handled on the Axelor side.
02What do you need to connect Axelor to Make?
An active Axelor account with login access to Axelor Connect, and an API token. You create the token in Axelor from the Connect application: Profile at the bottom of the left sidebar, the API access tab, then Add token, a label, the organizations:read scope and Save. In Make, add an Axelor module, click Create a connection, optionally name it, and paste the token. The connection is then reused by every Axelor module of your scenarios.
03Does the Axelor trigger react in real time?
It depends on the trigger. Instant deleted record is instant: Axelor calls Make through a webhook as soon as a record is deleted. Watch a New Record and Watch New / Updated Records are scheduled: Make checks Axelor on the scenario's schedule, every 15 minutes by default, with 15 minutes as the minimum on the Free plan and 1 minute on paid plans. So a new or edited record appears at the next scheduled run, not immediately.
04What if the Axelor module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Axelor API from your scenario, with the connection you already created, which covers what the 24 listed modules do not. Also check the newer modules before the ones tagged Deprecated: Make a Business Service Call and Run action reach beyond simple records. The doc describes most of these modules by name only, so test each call with Run once and read the bundles before switching the scenario on.
05Is Make or n8n better for Axelor?
It depends on what you check first. On Make, Axelor comes with 24 modules, 3 of them triggers, plus Make an API Call for the rest, and it is available from the Free plan. The same app often has an n8n node too, so look at what that node covers for Axelor before deciding. Compare the triggers you need, especially the instant one on deletions, and whether the listed actions match your records. Pick the tool whose ready-made modules fit your case.
Same platform

Other docs you might need on this stack.

Browse all integrations