Resources · Make integration

Axonaut Make integrationAutomate Axonaut with Make.

Can your CRM and invoicing data in Axonaut move on its own? The Axonaut Make integration gives you 83 modules, including 31 instant triggers, to link Axonaut to your other tools. This guide connects your account, builds a first scenario and explains each module.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Axonaut Make integration automate?

The Axonaut Make integration links your Axonaut account to Make, a visual tool where you build a scenario: an automation made of modules, each module being one brick such as a trigger, an action or a search. Axonaut can start a scenario when a record changes, and Make can create, read, update or delete companies, invoices, opportunities and more.

Leads that file themselves. A contact form in another app hands over a new lead; Create a Company then Create an Opportunity put it straight into your pipeline, with nobody retyping names.

Invoices that reach the right people. Watch Created Invoices fires as soon as an invoice exists in Axonaut, so the accountant or a team channel hears about it without opening the CRM.

Support that stays in one place. A request arriving by email or form becomes a ticket through Create a Ticket, and Watch Updated Tickets can tell the customer when its status moves.

Signed contracts can also close the loop: an e-signature app reports the signature and Register an Opportunity as Won updates the deal for you.

The Axonaut documentation gives no numeric limit for these modules. What the 83 listed modules do not cover, Make an API Call can reach with the same connection. To go further, see our Make training, check plans on Make pricing, or weigh both tools in n8n vs Make.

Connect

How do you connect Axonaut to Make?

  1. 01

    Copy your API key in Axonaut

    Log in to Axonaut, click the wrench icon, then API. Click Show your API key, confirm with ok, and copy the key somewhere safe: Make will ask for it in a moment.

  2. 02

    Add an Axonaut module in Make

    Open a scenario in Make, add any Axonaut module, then click Add next to the Connection field. A connection is your Axonaut account linked to Make once, then reused by every Axonaut module.

  3. 03

    Name the connection and paste the key

    Give the connection a clear name in Connection name, for example the company account it belongs to. Paste the key into API Key and click Save. Make can now list your Axonaut records.

First scenario

Your first scenario: web leads into Axonaut

GoalWhen a lead comes in from your web form, Make creates the company and its opportunity in Axonaut.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Search for the form tool your site uses and pick its module that receives a new submission.

  2. 02

    Add Create a Company

    Click the + on the right of the form module, search Axonaut and choose Create a Company. Select your connection, then map the name and details coming from the form.

  3. 03

    Chain Create an Opportunity

    Add Create an Opportunity after it. Map data from the two previous modules so the deal lands on the company Make just created, not on a random record.

  4. 04

    Test with Run once

    Click Run once, then send a test submission through your form. Open each module's bubble to read the bundle it received: one bundle is one item, here one lead.

  5. 05

    Schedule and switch it on

    Check the scheduling clock on the first module (every 15 minutes by default for a new scenario) and switch the scenario on. Each module run on a lead counts as one operation on your plan.

Triggers

Axonaut triggers: what starts a scenario

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

Axonaut1Watch Created Companies

Watch Created Companies

Instant trigger

In MakeTriggers when a new company is created.

Every company added in Axonaut can launch a scenario the moment it exists, so a fresh customer or prospect reaches your other tools without anyone copying it by hand.

How it fires
instant, Axonaut calls Make through a webhook as soon as the company is saved.
When to use it
a sales rep adds a prospect and you want it in your mailing list or shared customer sheet too.
Watch out
it reacts to creation only; pair it with Watch Updated Companies if later edits must follow.
Axonaut2Watch Created Employees

Watch Created Employees

Instant trigger

In MakeTriggers when a new employee is created.

A colleague newly entered in Axonaut becomes the starting point of an onboarding flow, with their record handed as one bundle to whatever module comes next.

How it fires
instant, Axonaut pings Make by webhook right after the employee record is created.
When to use it
HR creates the profile and you want a welcome email, a checklist card or an account request to follow on its own.
Watch out
each module that runs for that newcomer uses one operation on your Make plan.
Axonaut3Watch Created Events

Watch Created Events

Instant trigger

In MakeTriggers when a new event is created.

Calls, meetings and other events logged in Axonaut can travel beyond the CRM, giving your calendar or team channel the same trace your reps record.

How it fires
instant, the new event reaches Make through a webhook as soon as Axonaut stores it.
When to use it
a rep logs a client meeting and the account manager should get a short note in chat without checking the CRM.
Watch out
busy teams log many events, and every one of them starts a run, so filter early in the scenario.
Axonaut4Watch Created Expenses

Watch Created Expenses

Instant trigger

In MakeTriggers when a new expense is created.

Spending recorded in Axonaut can land in your bookkeeping or approval process straight away, so finance sees costs while they are still fresh.

How it fires
instant, Axonaut sends each new expense to Make by webhook once it is entered.
When to use it
someone logs a supplier bill or travel cost and the finance lead wants a copy in a spreadsheet or an approval message.
Watch out
the module name says Expenses while its internal key says Expanses; both point to the same thing.
Axonaut5Watch Created Invoices

Watch Created Invoices

Instant trigger

In MakeTriggers when a new invoice is created.

A newly issued invoice can notify the people who care about cash, or be copied into another tool, without anyone exporting it from Axonaut.

How it fires
instant, Make hears about the invoice through Axonaut's webhook the moment it is created.
When to use it
you want your accountant, a finance channel or a revenue sheet updated each time billing goes out.
Watch out
a draft still counts as a created invoice if Axonaut saves it as one; test with Run once to see what arrives.
Axonaut6Watch Created Opportunities

Watch Created Opportunities

Instant trigger

In MakeTriggers when a new opportunity is created.

Each new deal in your Axonaut pipeline can start the follow-up work around it, from a reminder for the rep to a card on a sales board.

How it fires
instant, the opportunity is pushed to Make by webhook as soon as it is opened.
When to use it
a manager wants every fresh deal announced in the sales channel, or a project prepared before the kickoff call.
Watch out
if your own scenario also runs Create an Opportunity, that record will fire this trigger too, so keep the two flows apart.
Axonaut7Watch Created Orders

Watch Created Orders

Instant trigger

In MakeTriggers when a new order is created.

An order entered in Axonaut can move on to preparation, shipping or production tools at once, so nothing waits on a copy and paste.

How it fires
instant, Axonaut alerts Make through a webhook when the order is created.
When to use it
a signed order must reach the warehouse sheet or the delivery team the same day it is booked.
Watch out
the internal key mentions contracts, yet Make shows this module as Watch Created Orders; trust the displayed name.
Axonaut8Watch Created Products

Watch Created Products

Instant trigger

In MakeTriggers when a new product is created.

When a product joins your Axonaut catalog, the same item can appear in your shop, price list or sales documents without a second entry.

How it fires
instant, Make receives the product from Axonaut's webhook right after it is added.
When to use it
the catalog lives in Axonaut and an online store or a quoting sheet must stay aligned with it.
Watch out
changes made later go through Watch Updated Products, not this module, so plan both if prices move.
Axonaut9Watch Created Projects

Watch Created Projects

Instant trigger

In MakeTriggers when a new project is created.

Opening a project in Axonaut can set up the working space around it: a folder, a board, a channel, whatever your team uses to deliver.

How it fires
instant, Axonaut notifies Make by webhook when the project is created.
When to use it
a consultancy wants a shared folder and a task list ready as soon as a project is registered for a client.
Watch out
the bundle carries what Axonaut sends for the project; check it with Run once before mapping names into other tools.
Axonaut10Watch Created Quotations

Watch Created Quotations

Instant trigger

In MakeTriggers when a new qouotation is created.

A quotation sent from Axonaut can kick off the chase that follows it, so no proposal sits forgotten in someone's outbox.

How it fires
instant, the new quotation reaches Make through Axonaut's webhook as soon as it is saved.
When to use it
a sales lead wants a reminder task or a note in the CRM channel each time a quote is issued.
Watch out
the trigger tells you a quote exists; to check its current state later, pair it with Get a Quotation.
Axonaut11Watch Created Tasks

Watch Created Tasks

Instant trigger

In MakeTriggers when a new task is created.

Tasks assigned in Axonaut can echo in the tool where people actually work, so an action item does not stay hidden inside the CRM.

How it fires
instant, Axonaut posts each new task to Make by webhook once it exists.
When to use it
reps create follow-up tasks in Axonaut but the team plans its week in a separate to-do app or chat.
Watch out
mirroring tasks both ways can create loops; send them in one direction only.
Axonaut12Watch Created Tickets

Watch Created Tickets

Instant trigger

In MakeTriggers when a new ticket is created.

Support requests logged as tickets in Axonaut can alert the right person immediately, cutting the time a customer waits for a first answer.

How it fires
instant, Make gets the ticket through a webhook the moment Axonaut records it.
When to use it
the support desk wants a message in its channel, or an acknowledgment email to the client, for every new ticket.
Watch out
if another scenario creates tickets with Create a Ticket, those will also start this one.
Axonaut13Watch Deleted Companies

Watch Deleted Companies

Instant trigger

In MakeTriggers when an existing company is deleted.

Removing a company from Axonaut can trigger the cleanup elsewhere, so old records do not linger in a mailing list or a shared file.

How it fires
instant, Axonaut tells Make by webhook as soon as the company is deleted.
When to use it
you keep a copy of your customer base in another tool and want both lists to lose the same entries.
Watch out
the record no longer exists in Axonaut, so a Get a Company step after this trigger has nothing left to read.
Axonaut14Watch Deleted Employees

Watch Deleted Employees

Instant trigger

In MakeTriggers when an existing employee is deleted.

When someone leaves and their Axonaut profile goes, a scenario can start the offboarding steps you would otherwise track by memory.

How it fires
instant, the deletion is sent to Make through a webhook right away.
When to use it
an office manager wants a checklist card or a message to IT each time an employee record is removed.
Watch out
use the bundle as a signal to act elsewhere; the employee is already gone from Axonaut itself.
Axonaut15Watch Deleted Events

Watch Deleted Events

Instant trigger

In MakeTriggers when an existing event is deleted.

A cancelled meeting removed from Axonaut can disappear from the calendars and channels that received it, keeping everyone's agenda honest.

How it fires
instant, Axonaut reports the deleted event to Make by webhook.
When to use it
events are copied to a shared calendar and a deletion in the CRM should take the slot off there too.
Watch out
to find the copy to remove, you need something that links both sides, so store it when you first copy the event.
Axonaut16Watch Deleted Expenses

Watch Deleted Expenses

Instant trigger

In MakeTriggers when an existing expense is deleted.

An expense withdrawn from Axonaut can be struck from your spending report as well, so totals outside the CRM match the ones inside.

How it fires
instant, Make is warned through Axonaut's webhook once the expense is deleted.
When to use it
expenses feed a budget sheet and a correction in Axonaut must flow into it without manual edits.
Watch out
deletions and creations run in separate scenarios, so name them clearly to tell them apart later.
Axonaut17Watch Deleted Opportunities

Watch Deleted Opportunities

Instant trigger

In MakeTriggers when an existing opportunity is deleted.

Deals dropped from your Axonaut pipeline can vanish from the forecasts and boards built on them, keeping reports tied to real opportunities.

How it fires
instant, Axonaut calls Make by webhook when the opportunity is deleted.
When to use it
a sales director tracks the pipeline in a spreadsheet and wants deleted deals out of it.
Watch out
a lost deal is not a deleted one; if the rep marks it lost instead, this trigger stays silent.
Axonaut18Watch Deleted Orders

Watch Deleted Orders

Instant trigger

In MakeTriggers when an existing orders is deleted.

A cancelled order that disappears from Axonaut can stop the work downstream, before someone prepares or ships something nobody wants.

How it fires
instant, Axonaut sends the deletion to Make through a webhook as soon as it happens.
When to use it
orders are forwarded to logistics and a cancellation must reach the same team fast.
Watch out
the internal key speaks of contacts while Make displays Watch Deleted Orders; the module is about orders.
Axonaut19Watch Deleted Products

Watch Deleted Products

Instant trigger

In MakeTriggers when an existing product is deleted.

A product retired from the Axonaut catalog can be pulled from your store or price list too, so customers do not order an item you no longer sell.

How it fires
instant, Make learns about the deletion through Axonaut's webhook.
When to use it
your web shop mirrors the catalog kept in Axonaut and must drop the same references.
Watch out
remove the item in the other tool through its own module; nothing in Axonaut can be read back once deleted.
Axonaut20Watch Deleted Projects

Watch Deleted Projects

Instant trigger

In MakeTriggers when an existing project is deleted.

Closing the door on a project deleted in Axonaut can archive its folder or board, so abandoned work stops cluttering the team's space.

How it fires
instant, Axonaut informs Make by webhook when the project is removed.
When to use it
each project has a matching folder or board and you want those archived the day the project goes.
Watch out
archive rather than delete on the other side, so a mistake in Axonaut stays recoverable.
Axonaut21Watch Deleted Tasks

Watch Deleted Tasks

Instant trigger

In MakeTriggers when an existing task is deleted.

Tasks removed in Axonaut can be cleared from the to-do app that mirrors them, so nobody works on something already cancelled.

How it fires
instant, the deletion reaches Make through a webhook from Axonaut.
When to use it
you already copy new tasks to another tool with Watch Created Tasks and want the lists to stay equal.
Watch out
keep the link between both copies from the start, otherwise Make cannot tell which task to clear.
Axonaut22Watch Deleted Tickets

Watch Deleted Tickets

Instant trigger

In MakeTriggers when an existing ticket is deleted.

A ticket deleted in Axonaut can close its trace elsewhere, whether that is a support channel thread or a line in a service log.

How it fires
instant, Axonaut sends a webhook to Make as soon as the ticket is deleted.
When to use it
duplicate tickets are cleaned up in Axonaut and the support team's tracking sheet should follow.
Watch out
a solved ticket is usually updated, not deleted; for status changes use Watch Updated Tickets.
Axonaut23Watch Updated Companies

Watch Updated Companies

Instant trigger

In MakeTriggers when an existing company is updated.

Edits to a company in Axonaut, such as a new address or a changed contact detail, can reach every tool holding a copy of that customer.

How it fires
instant, Axonaut calls Make by webhook whenever the company is updated.
When to use it
the CRM is your reference and a billing or mailing tool must stay aligned with it.
Watch out
if your scenario ends with Update a Company on the same record, it can wake itself again; avoid writing back.
Axonaut24Watch Updated Employees

Watch Updated Employees

Instant trigger

In MakeTriggers when an existing employee is updated.

Changes to an employee profile in Axonaut can refresh the directory, org chart or payroll sheet that relies on it.

How it fires
instant, Make receives the updated employee through a webhook from Axonaut.
When to use it
a new job title or phone number entered in Axonaut should show up in the team directory too.
Watch out
every small edit fires the scenario, so a filter on the fields you care about saves operations.
Axonaut25Watch Updated Expenses

Watch Updated Expenses

Instant trigger

In MakeTriggers when an existing expense is updated.

A corrected amount or category on an Axonaut expense can flow into your reporting, so budget lines never keep the old figure.

How it fires
instant, Axonaut pushes the change to Make by webhook as it is saved.
When to use it
the finance team fixes expenses in Axonaut and a spending dashboard reads from another sheet.
Watch out
update the matching row rather than adding one, or the corrected expense will appear twice.
Axonaut26Watch Updated Opportunities

Watch Updated Opportunities

Instant trigger

In MakeTriggers when an existing opportunity is updated.

When a deal moves in Axonaut, the people and tools following it can move with it, from a sales chat to a forecast sheet.

How it fires
instant, Axonaut calls Make through a webhook each time the opportunity changes.
When to use it
a manager wants to know when a deal changes stage without watching the pipeline all day.
Watch out
any edit fires it, not only stage changes, so add a filter before posting messages.
Axonaut27Watch Updated Orders

Watch Updated Orders

Instant trigger

In MakeTriggers when an existing order is updated.

An order edited in Axonaut, for instance a changed quantity, can update the logistics or production tools already working on it.

How it fires
instant, the updated order reaches Make through a webhook from Axonaut.
When to use it
the warehouse works from a separate list and needs corrections the moment sales make them.
Watch out
despite the internal key about contacts, Make displays this module as Watch Updated Orders.
Axonaut28Watch Updated Products

Watch Updated Products

Instant trigger

In MakeTriggers when an existing product is updated.

Price or description changes in the Axonaut catalog can be copied to your shop and sales documents, so every channel shows the same offer.

How it fires
instant, Axonaut notifies Make by webhook when a product is edited.
When to use it
you adjust prices in Axonaut and want the online store to follow without a manual update.
Watch out
test with Run once on a single product before letting the scenario touch your live store.
Axonaut29Watch Updated Projects

Watch Updated Projects

Instant trigger

In MakeTriggers when an existing project is updated.

Progress recorded on an Axonaut project can be shared with the client or the team where they look, without a status meeting.

How it fires
instant, Make is told through Axonaut's webhook whenever the project is updated.
When to use it
a studio updates project details in Axonaut and wants the delivery board or client portal refreshed.
Watch out
a burst of edits sends a burst of runs, each costing operations on your plan.
Axonaut30Watch Updated Tasks

Watch Updated Tasks

Instant trigger

In MakeTriggers when an existing task is updated.

Reassigned or completed tasks in Axonaut can update their copy in another planner, so both views tell the same story.

How it fires
instant, Axonaut sends the task change to Make through a webhook.
When to use it
a rep closes a follow-up task in Axonaut and the team's to-do app should mark it done too.
Watch out
if the other tool also writes back to Axonaut, the two can trigger each other endlessly.
Axonaut31Watch Updated Tickets

Watch Updated Tickets

Instant trigger

In MakeTriggers when an existing ticket is updated.

Each change on a support ticket in Axonaut can reach the customer or the team lead, so nobody has to ask where a request stands.

How it fires
instant, Axonaut calls Make by webhook every time the ticket is updated.
When to use it
clients should get a short email when their ticket changes status, written from the ticket's data.
Watch out
send the email only when the status really moved, using a filter, or customers get a message for every internal note.
Modules

Axonaut modules: what Make can do in your account

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

Axonaut1

Add a Document to a Company

Action

In MakeAdds a document for a specific company.

Attaches a file to a company record in Axonaut, so signed contracts or briefs live next to the customer instead of in someone's downloads folder.

When to use it
an e-signature tool returns a signed PDF and you want it filed on the right client automatically.
Watch out
on the Free plan, Make handles files up to 5 MB, so large scans may need a paid plan.
Axonaut2

Create a Company

Action

In MakeCreates a new company.

Adds a new company to Axonaut from data another module provides, giving every lead or customer a proper record without typing.

When to use it
a web form, a signup or a spreadsheet row brings a new organization that should exist in your CRM.
Watch out
run Search Companies first if the same company might already be there, or you will create duplicates.
Axonaut3

Create an Employee

Action

In MakeCreates a new employee.

Registers a new person on your team inside Axonaut from an HR form or another tool, so the CRM knows who works with you from day one.

When to use it
hiring is tracked in a separate app and the arrival of a newcomer should set up their Axonaut profile.
Watch out
map the details carefully on the first test with Run once, since a wrong profile then needs Update an Employee.
Axonaut4

Create an Event

Action

In MakeCreates a new event.

Logs an event in Axonaut, such as a meeting or a call, from outside the CRM, so the customer history stays complete even when the action happened elsewhere.

When to use it
a booking tool confirms a client meeting and the rep wants it recorded on the account.
Watch out
each booking writes a new event; resending the same data creates a second one.
Axonaut5

Create an Expense

Action

In MakeCreates a new expense.

Records a cost in Axonaut from a receipt tool, a card statement or a form, so spending reaches the CRM without a second data entry.

When to use it
staff submit expenses through a form and finance wants them in Axonaut straight after approval.
Watch out
check amounts and currency formats on a Run once test before letting real expenses through.
Axonaut6

Create an Invoice

Action

In MakeCreates a new invoice.

Produces an invoice in Axonaut from data held elsewhere, so a sale closed in another system turns into billing with no retyping.

When to use it
an online checkout or a signed order in another app should create the matching invoice in Axonaut.
Watch out
an invoice is a legal document; test with Run once on a test customer before switching the scenario on.
Axonaut7

Create an Opportunity

Action

In MakeCreates a new opportunity.

Opens a new deal in your Axonaut pipeline, so every qualified lead gets a place in the sales process instead of sitting in an inbox.

When to use it
a demo request or a pricing inquiry arrives through a form and should become a deal for a rep.
Watch out
tie it to the right company, usually the one just created or found in an earlier module.
Axonaut8

Create an Order

Action

In MakeCreates a new order.

Books an order in Axonaut from a sale made elsewhere, so the CRM holds the full picture of what each customer bought.

When to use it
a shop or payment tool registers a purchase and Axonaut should record the order for follow-up.
Watch out
a new order fires Watch Created Orders too, so check that no other scenario reacts twice.
Axonaut9

Create a Payment

Action

In MakeCreates a new payment.

Records a payment in Axonaut when money arrives through another tool, keeping the unpaid list accurate without manual matching.

When to use it
a payment provider confirms a transfer and the related invoice in Axonaut should show it as paid.
Watch out
find the right invoice first with Search Invoices, since a payment on the wrong one is harder to spot than a missing one.
Axonaut10

Create a Product

Action

In MakeCreates a new product.

Adds an item to the Axonaut catalog from a supplier list, a shop or a spreadsheet, so quotes and invoices can use it right away.

When to use it
new references are prepared in a shared sheet and should appear in Axonaut once validated.
Watch out
search the catalog with Search Products before creating, to avoid two versions of the same item.
Axonaut11

Create a Project

Action

In MakeCreates a new project.

Opens a project in Axonaut from an event in another tool, so delivery work starts with a record the whole team can follow.

When to use it
a signed quote or a kickoff form should set up the project without a project manager typing it.
Watch out
a created project fires Watch Created Projects, handy for chaining but a loop risk if that scenario writes back.
Axonaut12

Create a Quotation

Action

In MakeCreates a new quotation.

Drafts a quotation in Axonaut from a configurator, a form or a spreadsheet, so a sales rep starts from a ready document rather than a blank page.

When to use it
prospects build their request online and the sales team wants a quote prepared from those answers.
Watch out
review a few generated quotes before switching on, since prices and lines come straight from your mapping.
Axonaut13

Create a Supplier

Action

In MakeCreates a new supplier.

Registers a supplier in Axonaut from a vendor onboarding form or a procurement tool, so purchasing data lives in the same place as sales.

When to use it
buyers approve a new vendor elsewhere and accounting needs it in Axonaut to log expenses against it.
Watch out
check Search Suppliers first to avoid creating the same vendor twice under slightly different names.
Axonaut14

Create a Ticket

Action

In MakeCreates a new ticket.

Turns a support request from email, chat or a form into a ticket in Axonaut, so every question gets tracked from the first message.

When to use it
customers write to a support address and the team wants each request logged on the client's account.
Watch out
auto-replies and newsletters can become tickets too; filter them out before this module.
Axonaut15

Delete a Company

Action

In MakeDeletes an existing company.

Removes a company from Axonaut on a signal from another tool, keeping the CRM clean when a record should no longer exist.

When to use it
a data cleanup sheet marks test or duplicate companies and you want them gone in one pass.
Watch out
a deletion does not come back; run it on a single record with Run once before any batch.
Axonaut16

Delete an Employee

Action

In MakeDeletes an existing employee.

Takes an employee out of Axonaut when their departure is recorded somewhere else, so the team list matches reality.

When to use it
your HR tool closes a contract and the person should also leave the CRM.
Watch out
the removal is final; if anyone may need the profile's history, update it instead of deleting.
Axonaut17

Delete an Opportunity

Action

In MakeDeletes an existing opportunity.

Erases a deal from the Axonaut pipeline, useful for clearing test entries or duplicates created by an import.

When to use it
a cleanup scenario spots duplicate opportunities and should keep only one of each.
Watch out
a real lost deal belongs in Register an Opportunity as Lost, which keeps it in your history; deleting wipes it.
Axonaut18

Delete a Project

Action

In MakeDeletes an existing project.

Removes a project from Axonaut, typically one created by mistake or cancelled before it started.

When to use it
a quote is withdrawn and the project prepared for it in advance should disappear too.
Watch out
there is no undo, and linked tools that mirror projects will fire Watch Deleted Projects scenarios if you have them.
Axonaut19

Get a Company

Action

In MakeRetrieves an existing company.

Reads one company's full record from Axonaut, giving the rest of your scenario its details to use in emails, documents or other apps.

When to use it
a trigger brings only part of the data and you need the complete company before sending anything.
Watch out
it targets a single company you already know; to find one by name, use Search Companies instead.
Axonaut20

Get an Employee

Action

In MakeRetrieves an existing employee.

Fetches one employee from Axonaut so later modules can use their details, for instance to address a notification to the right person.

When to use it
a task or ticket names an owner and you need that colleague's full profile to reach them.
Watch out
it reads one known employee; to browse the team, Search Employees returns several bundles.
Axonaut21

Get an Expense

Action

In MakeRetrieves an existing expense.

Pulls a single expense from Axonaut with its details, so an approval message or a report can quote it accurately.

When to use it
an update trigger tells you an expense changed and the finance lead wants the latest version in a message.
Watch out
the internal key reads Expanse, but this is the Get an Expense module Make shows in the list.
Axonaut22

Get an Invoice

Action

In MakeRetrieves an existing invoice.

Retrieves one invoice from Axonaut, giving you what you need to send a reminder, archive a copy or update an accounting tool.

When to use it
a payment arrives elsewhere and you want to check the related invoice before recording it.
Watch out
it returns one invoice; to review unpaid ones in bulk, use Search Invoices.
Axonaut23

Get an Opportunity

Action

In MakeRetrieves an existing opportunity.

Loads a single deal from Axonaut so the rest of the scenario can react to its current state, owner or amount.

When to use it
a message about a deal should include its latest details rather than the old ones stored elsewhere.
Watch out
place it after a module that already knows which opportunity you mean, such as a trigger or a search.
Axonaut24

Get an Order

Action

In MakeRetrieves an existing order.

Reads one order from Axonaut, so shipping, production or reporting tools receive exactly what the customer bought.

When to use it
a logistics request needs the full order details before a delivery slip is created.
Watch out
it needs a known order; when you only have a customer name, start with Search Orders.
Axonaut25

Get a Product

Action

In MakeRetrieves an existing product.

Fetches one product from your Axonaut catalog so a shop, a sheet or a document can show the same details you keep in the CRM.

When to use it
an order line names a product and you want its full description before sending a confirmation.
Watch out
each call reads one product and costs one operation; for a whole catalog, Search Products is lighter.
Axonaut26

Get a Project

Action

In MakeRetrieves an existing project.

Retrieves a single Axonaut project so a status update, client report or team message can quote its current details.

When to use it
a ticket mentions a project and support needs its context before answering the client.
Watch out
it reads one project you already identified; List Projects is the module for browsing them.
Axonaut27

Get a Quotation

Action

In MakeRetrieves an existing quotation.

Reads one quotation from Axonaut, useful to check what was proposed before a reminder or a follow-up goes out.

When to use it
a chase email should quote the proposal's contents rather than a generic message.
Watch out
it reads the quote as it stands at that moment; a later edit needs another read.
Axonaut28

Get a Supplier

Action

In MakeRetrieves an existing supplier.

Pulls one supplier's record from Axonaut, so purchase requests or payment notices use the right details.

When to use it
an expense names a vendor and accounting wants the supplier's data in the approval message.
Watch out
it expects one known supplier; to look one up, Search Suppliers comes first.
Axonaut29

Get a Ticket

Action

In MakeRetrieves an existing ticket.

Loads one support ticket from Axonaut with its details, ready to be quoted in a reply, an escalation or a report.

When to use it
a team lead wants a digest message about a ticket that just changed, with its full content.
Watch out
reading a ticket does not change it; to set a new status, use Update a Ticket.
Axonaut30

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Reaches any endpoint of the Axonaut API from your scenario, using the same connection, for the cases the 83 listed modules do not cover.

When to use it
you need an Axonaut object or action with no dedicated module, and the API documentation describes it.
Watch out
this module asks you to read the API documentation yourself; nothing is prefilled as in the other modules.
Axonaut31

Register an Opportunity as Lost

Action

In MakeRegisters an existing opportunity as lost.

Marks a deal as lost in Axonaut while keeping it in your history, so win rates and reports stay honest.

When to use it
a prospect declines through a form or an email reply and the rep should not have to update the CRM by hand.
Watch out
the deal stays in Axonaut; if you want it gone for good, that is Delete an Opportunity.
Axonaut32

Register an Opportunity as Won

Action

In MakeRegisters an existing opportunity as won.

Closes a deal as won in Axonaut, the step that usually opens delivery, billing and a thank-you to the client.

When to use it
an e-signature tool reports a signed contract and the matching opportunity should switch to won.
Watch out
this counts as an update, so any scenario watching updated opportunities will fire as well.
Axonaut33

Update a Company

Action

In MakeUpdates an existing company.

Changes a company record in Axonaut with fresher data from another tool, so contact details stay current without manual edits.

When to use it
a customer updates their details in a portal or form and the CRM should hold the new version.
Watch out
map only the fields you mean to change; an empty mapping can overwrite good data.
Axonaut34

Update an Employee

Action

In MakeUpdates an existing employee.

Edits an employee profile in Axonaut from your HR source, keeping titles and contact details aligned across tools.

When to use it
a promotion or a team change is recorded in the HR app and Axonaut should reflect it.
Watch out
if a scenario also watches updated employees, an update here will start it too.
Axonaut35

Update an Opportunity

Action

In MakeUpdates an existing opportunity.

Adjusts a deal in Axonaut, for example its amount or its stage, based on what happens outside the CRM.

When to use it
a prospect books a demo in a scheduling app and the related opportunity should move forward.
Watch out
to close a deal, the dedicated won and lost modules are clearer than a generic update.
Axonaut36

Update a Product

Action

In MakeUpdates an existing product.

Modifies a product in the Axonaut catalog from a supplier price list or a shop, so quotes always use current prices.

When to use it
a supplier sends new prices in a spreadsheet and Axonaut should follow once the sheet is approved.
Watch out
test on one product first; a wrong mapping here changes the catalog every quote relies on.
Axonaut37

Update a Project

Action

In MakeUpdates an existing project.

Updates an Axonaut project with news from the tools where the delivery actually happens, keeping the CRM view accurate.

When to use it
a board card moves to done in your task app and the Axonaut project should record that progress.
Watch out
avoid ping-pong: if Watch Updated Projects feeds that same board, the two scenarios can keep waking each other.
Axonaut38

Update a Ticket

Action

In MakeUpdates an existing ticket.

Changes a support ticket in Axonaut, such as its status, from another channel, so the CRM shows where each request stands.

When to use it
an agent answers from a shared inbox and the ticket in Axonaut should move without a second click.
Watch out
customers notified through Watch Updated Tickets will hear about this change too.
Axonaut39

List Company's Events

Search

In MakeLists existing events of a specific company.

Gathers the events recorded on one company in Axonaut, giving you its recent meetings and calls in one go.

When to use it
before a renewal call, a rep wants a summary of past exchanges with that client sent to them.
Watch out
it returns zero, one or many bundles, one per event, and every following module runs for each of them.
Axonaut40

List Events

Search

In MakeLists existing events.

Returns events from across your Axonaut account, handy for building an activity report or a shared agenda outside the CRM.

When to use it
a manager wants a digest of the team's logged meetings compiled into one sheet or message.
Watch out
each event is a separate bundle; add an aggregator from Make's tools if you want one message instead of many.
Axonaut41

List Projects

Search

In MakeLists all existing projects.

You get every project stored in Axonaut as separate bundles (a bundle is one item passed to the next module), ready to feed a report or a shared sheet.

When to use it
pick it when the scenario needs the whole project list; unlike the other searches here, this one lists and does not narrow down.
Watch out
every project that comes out makes the following modules run once more, so each one costs an operation, the unit Make counts on your plan.
Axonaut42

Search Companies

Search

In MakeSearches for companies or lists them all.

This module hands back the Axonaut companies that match your search, or the full list when you leave it open, one bundle per company.

When to use it
reach for it when you only know part of a customer and need to find the record before updating it; if the ID is already in hand, Get a Company is the lighter choice.
Watch out
an empty result is normal and stops the branch, so test with Run once before trusting it.
Axonaut43

Search Employees

Search

In MakeSearches for employees or lists them all.

Your team roster in Axonaut comes out as one bundle per employee, either filtered by your search or complete.

When to use it
it fits a scenario that must check whether a person already exists before Create an Employee adds a duplicate.
Watch out
the search can return several people for the same query; decide which one the next module should use instead of letting all of them flow through.
Axonaut44

Search Expenses

Search

In MakeSearches for expenses or lists them all.

Expenses recorded in Axonaut come back here, matched to what you look for or listed in full, so finance data can move to another tool.

When to use it
choose it to gather expenses before pushing them to an accounting sheet; Get an Expense only suits the case where one known expense is needed.
Watch out
the internal key of this module carries a typo, yet the module name in the editor reads Search Expenses.
Axonaut45

Search Invoices

Search

In MakeSearches for invoices or lists them all.

With this search, the invoices of Axonaut reach your scenario as individual bundles, filtered by your query or all at once.

When to use it
use it when a payment arrives elsewhere and the matching invoice has to be found before anything is updated.
Watch out
a broad search can bring back many invoices, and every step after it runs for each of them.
Axonaut46

Search Opportunities

Search

In MakeSearches for opportunities or lists them all.

Deals from your Axonaut pipeline come back one by one, either the ones matching your search or the whole list.

When to use it
it shines before Register an Opportunity as Won or as Lost, when the scenario must first locate the right deal from a name or a company.
Watch out
if two deals share the same wording, both come out; add a filter between modules so only the right one moves on.
Axonaut47

Search Orders

Search

In MakeSearches for existing order or lists them all.

Orders stored in Axonaut surface in the scenario as bundles, narrowed to your criteria or listed in full.

When to use it
pick it to reconcile orders with a shop or a logistics tool, when you do not have the Axonaut ID that Get an Order expects.
Watch out
zero results is a valid answer, and the rest of the route simply does not run for that execution.
Axonaut48

Search Payments

Search

In MakeSearches for payments or lists them all.

This one returns the payments recorded in Axonaut, whether the ones you are looking for or all of them, each as its own bundle.

When to use it
it helps when a bank or billing tool needs to know if a payment was already logged, so Create a Payment is not called twice.
Watch out
no Get module exists for payments in this app, so this search is also the way to read a single one.
Axonaut49

Search Products

Search

In MakeSearches for products or lists them all.

Your Axonaut catalogue flows out of this module product by product, filtered by the search or complete.

When to use it
choose it to sync prices or references toward an online store, or to check that an item exists before Update a Product edits it.
Watch out
a large catalogue multiplies operations in every downstream module, so narrow the search whenever you can.
Axonaut50

Search Quotations

Search

In MakeSearches for quotations or lists them all.

Quotations saved in Axonaut come back as bundles, the matching ones or the entire list.

When to use it
use it to follow up on quotes from another tool, for instance to send a reminder email, when the quote ID is not known in advance.
Watch out
several quotes can share one customer, so map carefully which bundle feeds the next module.
Axonaut51

Search Suppliers

Search

In MakeSearches for suppliers or lists them all.

Supplier records from Axonaut arrive in your scenario one per bundle, matched to your query or listed completely.

When to use it
it fits before Create a Supplier, to avoid adding the same vendor twice, or before Create an Expense that needs the right supplier.
Watch out
if the search finds nothing, plan a fallback route rather than letting the scenario end silently.
Axonaut52

Search Tickets

Search

In MakeSearches for tickets or lists them all.

Support tickets stored in Axonaut come out here, the ones you search for or all of them, ready to be copied into a help desk or a chat channel.

When to use it
reach for it to find an open ticket before Update a Ticket changes it; Get a Ticket needs the exact ID.
Watch out
each ticket returned triggers the next steps separately, which adds operations quickly on a busy queue.
Need help

Need help automating Axonaut with Make?

A person reads every message.

FAQ

Axonaut and Make: common questions

01Is the Axonaut Make integration free?
Yes, Axonaut is a standard app in Make, so you can use it on the Free plan. That plan allows 2 active scenarios, runs scheduled scenarios no more often than every 15 minutes, stops a run after 5 minutes, handles files up to 5 MB and includes 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to one minute, remove the cap on active scenarios and allow runs of up to 40 minutes. Usage is counted in operations, one per module per bundle.
02What do you need to connect Axonaut to Make?
You need an Axonaut account and its API key, and the Axonaut documentation lists no other prerequisite. In Axonaut, click the wrench icon, then API, then Show your API key and confirm with ok. Copy the key. In Make, add any Axonaut module, click Add next to the Connection field, name the connection and paste the key into API Key before clicking Save. That single connection is then reused by every Axonaut module in your scenarios.
03Do Axonaut triggers in Make react instantly?
Yes. All 31 Axonaut triggers in Make are instant: Axonaut calls Make through a webhook as soon as a company, invoice, opportunity, ticket or other record is created, updated or deleted. Make does not have to check Axonaut at intervals for these. In the editor, the module shows a lightning badge rather than a clock. Keep in mind that every event starts a run, so a filter right after the trigger keeps you from spending operations on changes you do not care about.
04What if an Axonaut module is missing in Make?
Use Make an API Call. It sends any request the Axonaut API accepts, through the connection you already set up, so you are not limited to the 83 listed modules. You will need the Axonaut API documentation to know which endpoint and data to send. The Axonaut documentation on Make gives no numeric limit for these modules. If what you want lives in another tool, add that app's module to the same scenario and pass data between them.
05Should you use Make or n8n for Axonaut?
It depends on your criteria rather than on a winner. On the Make side, Axonaut offers 83 modules, 31 of them instant triggers, plus Make an API Call for the rest, and it runs on every plan including Free. n8n is another automation tool that often has a node for the same app. Compare what each offers for the exact Axonaut records you need, how you want to build, and which plan fits your volume, then test your first scenario on the tool that matches.