Resources · Zapier integration

Axelor Zapier integrationAutomate Axelor with Zapier.

The Axelor Zapier integration offers 1 trigger and 2 actions. Zapier can spot new records in Axelor, create fresh ones, and change existing ones. Below: what each step does, how much of your plan it eats, and where things usually go wrong.

See the 3 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Axelor Zapier integration does for your records

It lets Axelor, the business suite where you keep your CRM, sales and accounting records, talk to your other tools without code. Zapier watches Axelor for new records and can also write into it: add a record or change one. Three operations, all built around the same idea of a record.

Three setups come up again and again. A new record in Axelor reaches the people who need it: New Record spots it and the next step posts a message or sends an email. Leads gathered elsewhere end up in your CRM: a form entry or a sheet row runs Create Record, so nobody retypes it. And a status changed in another tool is carried back: Update Record rewrites the matching Axelor record.

What Zapier does not do here matters just as much. There is no search step, so a Zap cannot look up an existing record by name or email before updating it; the record has to be identified some other way. There is no delete either, and only one trigger, which reacts to new records, not to edited ones.

Also worth knowing: the trigger is polling, so on the free plan expect a delay between the record appearing and the Zap starting. If you are weighing editors, the Axelor Make integration page covers the same app on Make, and our n8n vs Zapier comparison puts two of the options side by side.

Vocabulary

Zapier words, explained once

A handful of terms carry the whole page. Plain definitions first.

Zap
One automation on Zapier. Here it opens on a new record in an Axelor model, and the steps you stack after it run for each one.
Trigger
The event that opens the Zap. Axelor has a single one, New Record, tied to the model you pick in the editor.
Action
The work done once the Zap is running: writing a record into Axelor, changing one, or sending its details to another tool.
Task
What Zapier bills you for: one action that your Zap completes without failing. Plans are measured in tasks.
Polling trigger
A trigger Zapier visits on a schedule, asking Axelor what is new and skipping records it has already seen. New Record works this way.
Instant trigger
A trigger the app reports by itself, calling Zapier the moment something happens. Axelor's trigger is not one.
Filter
A step that lets the rest of the Zap run only when the incoming data meets your condition, and halts it otherwise.
Connection
Your Axelor account linked to Zapier one time, then picked again by every Axelor step you add later.
Cost

What an Axelor Zap costs

Axelor is not a premium app, so the free plan is enough to start. What you pay for is actions that work.

  • New Record checksfree
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps
  • Premium appno

Checking Axelor for new records never costs a task, however often Zapier looks. Each successful Create Record or Update Record counts one task, and a failed one is not billed. The free plan includes 100 tasks a month, but only two-step Zaps: one trigger, one action. A filter or a second action turns the Zap multi-step, and that needs a paid plan. Since New Record is a polling trigger, the interval below applies to it directly.

Connect

Link your Axelor account

  1. 01

    Start from Apps

    Open Apps in your Zapier account and click + Add connection. Make sure you have an Axelor account, plus rights on any records you do not own but want the Zap to touch.

  2. 02

    Pick Axelor

    Search for Axelor in the dialog that appears, select it, then click Add connection. Zapier opens a new tab so you can sign in on the Axelor side right away.

  3. 03

    Sign in and allow access

    Log in to Axelor in that tab and grant Zapier access to the account. The connection is stored, and every Axelor step you add afterwards offers it in a dropdown.

First Zap

Your first Zap: each new Axelor record emailed and posted in Slack

GoalEvery new record in the model you pick is emailed to the person in charge and announced in a team Slack channel.

  1. 01

    Choose the trigger

    Create a Zap, select Axelor and the New Record event, then set the Model you want watched. That choice decides which records start the Zap.

  2. 02

    Test it on real data

    Run the trigger test. Zapier pulls the three most recent records of that model, so you map the next steps on a real record rather than on a blank one.

  3. 03

    Add the email (paid plan)

    Click the plus icon, choose Gmail and Send Email, and map fields from the Axelor record into the subject and body. Two actions follow the trigger, so this Zap needs a paid plan.

  4. 04

    Add the Slack message

    Add a second action with Slack and Send Channel Message, pick the team channel and reuse a few record fields. Test both steps and read what arrived before going further.

  5. 05

    Publish

    Hit Publish. The Zap is now on and checks Axelor on your plan's interval; each new record it finds costs two tasks, one email and one message.

Triggers

The Axelor trigger

1 event starts a Zap when something happens in Axelor. Zapier checks for them at the interval your plan allows.

1

New Record

Polling trigger

In Zapier“Triggers when a new record is created.”

Starts the Zap whenever a record appears in the Axelor model you selected, and passes its fields along to the following steps. It is the only way in from Axelor, so every Zap that reacts to your CRM or sales data begins here.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a new customer or order in Axelor should alert a team, land in a sheet or open a task elsewhere.
Watch out
it watches a single Model and only brand new records; edits to existing ones never start it, so a second model means a second Zap.
Actions

Axelor actions

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

1

Create Record

Action

In Zapier“Creates a new record.”

Adds a fresh record to Axelor in the model you choose, filled with data from earlier steps. This is how leads or orders captured elsewhere get into your suite without retyping.

When to use it
a form, a shop or a sheet collects entries that belong in Axelor.
Watch out
the Model is required, and if this Zap writes into the model that New Record watches, it loops.
2

Update Record

Action

In Zapier“Updates a record.”

Changes a record that already exists in Axelor, rewriting the fields you map. Useful when the truth moves in another tool and Axelor needs to follow.

When to use it
a deal status or a customer detail changes outside Axelor.
Watch out
there is no search step to find the record first, so the Zap must already carry what identifies it.
When it breaks

When it breaks

Zapier links no help article to Axelor, so the cases below are the general ones that apply here too.

Often the Zap is doing exactly what it was set to do, and the surprise comes from the setup. For deeper checks, our Zapier troubleshooting page lists what to look at next.

  • Existing records are ignored

    A Zap only reacts to records created after you switch it on. Everything already in Axelor stays out; moving that backlog is a separate job.

  • A Zap that feeds itself

    Create Record writing into the very model New Record watches makes each run start the next one, and the task count drains fast.

  • A big import gets held

    After a bulk import or a migration in Axelor, the trigger may return a huge batch at once, and Zapier's flood protection can hold it back.

  • No duplicates from polling

    Zapier remembers which records it has already seen on New Record, so the same record does not start the Zap twice, even across many checks.
Need help

Need help automating Axelor with Zapier?

A person reads every message.

FAQ

Axelor Zapier integration: common questions

01Is the Axelor Zapier integration free?
Yes, Axelor is not a premium app, so it works on Zapier's free plan. That plan gives 100 tasks a month and as many Zaps as you like, each limited to two steps: one trigger and one action. A Zap that turns each new Axelor record into an email fits. Add a filter or a second action and it becomes a multi-step Zap that needs a paid plan. Your Axelor subscription is separate and is not covered here.
02How many tasks does an Axelor Zap use?
One task for every action that succeeds, and nothing for the trigger. Zapier checking Axelor for new records is free, however often it checks. So a Zap with New Record and one action costs one task per new record; with three actions it costs three. A failed action is not counted. The total depends on how many records appear in the model you watch, multiplied by the actions that follow.
03Is Axelor on Zapier real time?
No. New Record is a polling trigger: Zapier goes and looks at regular intervals, and how often depends on your plan. On the free plan that is every 15 minutes, on Professional every 2, on Team and Enterprise every minute. The type comes from the app itself and cannot be switched in the editor. On paid plans you can also run a check by hand from the editor when you need a record to go through right away.
04What does it take to connect an Axelor account?
An Axelor account, plus access to the records you want the Zap to read or write. In Zapier, open Apps, click + Add connection, search Axelor, click Add connection, then sign in and grant access in the tab that opens. Every operation then asks for a Model, the type of record involved, so the connected user has to see that model in Axelor or the list stays empty. Check that first if a dropdown looks blank.
05Why does Update Record not find the right record?
Because the integration has no search step, so the Zap cannot look the record up by name or email first. Update Record changes a record that already exists, and the Zap has to carry whatever identifies it from an earlier step. The cleanest setups start from New Record in Axelor itself, so the identifying data is already in the Zap. Test the step once and check in Axelor that the right record changed.
06What if the operation you need does not exist?
Then the Zap cannot do it and the work stays in Axelor. The integration has one trigger, for new records, and two actions, to create and update; there is no search, no delete and no trigger for edited records. A common approach is to split the job: let Zapier handle what goes in and out, and keep the rest inside Axelor. If the missing step is central, compare the other automation tools before building.
07Zapier, Make or n8n for Axelor?
It depends on what matters to you, not on a single winner. On Zapier, the Axelor trigger is polling, so the delay follows your plan, each successful action is billed, and a filter or a second action needs a paid plan. Make has its own Axelor page, so the first check is which operations each tool offers for this app. n8n is the third option if your team is at ease with a more technical tool. Then compare how many records you move and how many steps each needs with the price of each option.
Same platform

Other docs you might need on this stack.

Browse all integrations