Resources · Zapier integration

Axonaut Zapier integrationAutomate Axonaut with Zapier.

The Axonaut Zapier integration gives you 13 triggers, 14 actions and 6 searches to link your CRM, quotes and invoices to the rest of your tools. Below, what each one does, what it costs in tasks, and where it trips people up.

See the 33 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Axonaut Zapier integration actually does

It is a bridge between your Axonaut account and Zapier. Something happens in Axonaut (a company, a quote, a ticket shows up), Zapier notices it and runs the next steps for you. Or the other way round: another step tells Zapier to create a prospect, an invoice or an expense in Axonaut without anyone typing it.

Three results people build first. A sales pipeline that fills itself: Create Prospect or Create Company and Employee drops the new account into Axonaut, then Create Opportunity puts it in the right pipe. Billing without the copy-paste: Create Invoice and Create Invoice Payment write the invoice and mark what was paid. A support desk that leaves a trace: New Closed Ticket starts a Zap that logs a follow-up with Create Event.

Now the part the official page skips. None of the 13 triggers is instant: Zapier checks Axonaut on a timer, so on the free plan a new quote can wait up to 15 minutes before anything moves. Every action creates or reads something. There is no update and no delete on the list, so a Zap cannot change the status of an existing quote or remove a duplicate company. And searches mostly want an Axonaut ID, not a name (more on that below).

If you are weighing tools, the same breakdown exists on the Axonaut Make integration page, and the Make vs Zapier comparison sets the two side by side.

Vocabulary

Zapier vocabulary in one minute

Seven words come back on every line of this page. Here they are in plain English.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
Trigger
The event in an app that starts the Zap, such as a new invoice in Axonaut. Once the Zap is on, Zapier waits for it.
Action
What the Zap does after it starts: the step that writes, sends or creates something for you, here or in another app.
Task
The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
Polling vs instant
A polling trigger is checked on a timer, keeping only what is new. An instant trigger is pushed by the app the moment it happens.
Filter
A step that lets the Zap continue only when what arrived meets the condition you set. Otherwise the run stops there.
Search step
A step that looks up something already in an app, so the steps after it can use what it found.
Cost

What the Axonaut Zapier integration costs you

Axonaut is not a premium app on Zapier, so it works from the free plan. What you pay for is tasks, and the interval depends on your plan.

  • Free plan100 tasks per month, unlimited Zaps
  • Zap size on Free2 steps: one trigger, one action
  • Premium appNo, Axonaut works on the free plan
  • Trigger checksFree, never billed

The trigger never costs a task, and neither does Zapier checking Axonaut for new items, however often it looks. Each action that succeeds counts once: a Zap with three actions eats three times what a one-action Zap does. A failed action is not counted. The catch on the free plan is size: two steps, one trigger and one action. Add a filter, a search or a second action and you have a multi-step Zap, which needs a paid plan.

Connect

Connect your Axonaut account to Zapier

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. A connection is your Axonaut account linked once, then reused by every Zap step that talks to Axonaut.

  2. 02

    Pick Axonaut and confirm

    Type Axonaut in the search box of the dialog, select it, then click Add connection. You need an existing Axonaut account; Zapier does not create one for you.

  3. 03

    Sign in and grant access

    Log in to Axonaut in the tab that opens and let Zapier into the account. If the Zap has to touch records you do not own, make sure your Axonaut user has read or write rights on them first.

First Zap

Your first Axonaut Zap, step by step

GoalEvery new client company in Axonaut gets an opportunity in your pipe and an event that says who follows it up.

  1. 01

    Build: choose the trigger

    Start a new Zap in the editor, pick Axonaut as the app and New Company as the event, then select the Axonaut connection you just made.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent companies of the account, so you map the next steps on a real record rather than a blank one.

  3. 03

    Add Create Opportunity

    Add an Axonaut action, Create Opportunity. Fill the amount, probability, pipe and step, and the email of the Axonaut user in charge. Pipe and step must match Axonaut exactly.

  4. 04

    Add Create Event

    Add a second action, Create Event, and write the event content from the company data. This third step makes it a multi-step Zap, so it runs on a paid plan.

  5. 05

    Test, then Publish

    Test each action once and check the opportunity and the event in Axonaut. When both look right, click Publish to switch the Zap on.

Triggers

Axonaut triggers on Zapier

13 events start a Zap when something happens in Axonaut. Zapier checks for them at the interval your plan allows.

1

New Axonaut User

Polling trigger

In Zapier“Triggers when a new Axonaut user is created.”

This one watches your own Axonaut account and starts the Zap when a new user is added to it. It concerns the people working in Axonaut, not the employees stored under your client companies, which have their own trigger.

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 sales rep gets an account and you want an onboarding ticket opened for them with Create Ticket.
Watch out
users are also what Create Opportunity expects as business manager, so a fresh user is the moment to check that email.
2

New Closed Ticket

Polling trigger

In Zapier“Triggers when a ticket is closed.”

Fires when a support ticket gets closed in Axonaut, not when it is opened. That makes it the natural end point of a support flow: whatever must happen after the problem is solved hangs on this trigger.

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 customer success manager wants a follow-up call logged as an event on the account once the ticket is done.
Watch out
closing tickets in bulk produces a burst of items at once, which Zapier may hold back.
3

New Company

Polling trigger

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

Starts the Zap each time a company record is created in Axonaut, prospects and customers alike, since Create Prospect files both as companies.

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 account lands in the CRM and the sales team wants an opportunity opened straight away.
Watch out
never pair it with Create Prospect or Create Company and Employee in the same Zap, or each run creates a company that starts it again.
4

New Contract

Polling trigger

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

Picks up every contract freshly created in Axonaut and hands it to the next steps. A signed deal turning into a contract is usually where delivery work begins, so this trigger sits at the border between sales and operations.

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
an agency owner wants a kickoff ticket created for the project team each time a contract appears.
Watch out
contracts entered before the Zap was published are never picked up.
5

New Employee

Polling trigger

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

Reacts to a new employee record, meaning a contact person attached to a company in Axonaut. Think of it as the people-level twin of New Company: one company can carry several employees, and each one starts its own run.

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
an account manager wants an introduction event logged whenever a new contact joins a client.
Watch out
employees added before the Zap was published are never picked up.
6

New Expense

Polling trigger

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

Each expense recorded in Axonaut becomes a trigger event here. It is the bookkeeping side of the app: each new expense shows up as soon as Zapier's next check spots it.

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 finance lead wants a review ticket opened when an expense lands, with a filter to keep only the ones worth a second look.
Watch out
adding that filter turns the Zap into a multi-step one, so it needs a paid plan.
7

New Invoice

Polling trigger

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

Watches the invoices created in Axonaut and starts a run for each one. Whoever issues the invoice, a teammate in the interface or another Zap through Create Invoice, the trigger sees it the same way.

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 freelancer wants an event logged on the client file the moment an invoice goes out, to keep the history in one place.
Watch out
a Zap that starts on New Invoice and ends with Create Invoice loops on itself.
8

New Opportunity

Polling trigger

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

Fires on new opportunities in your Axonaut pipeline. Before you can test it, Zapier asks which opportunity status to watch, so the trigger only ever brings back deals in the status you chose.

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 sales manager wants a quotation drafted as soon as a deal enters the pipe.
Watch out
the status field is required. Pick the status deals have when they are created, not one they reach later, because the trigger reads each opportunity only once.
9

New Product

Polling trigger

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

Turns each product added to your Axonaut catalog into a Zap run. Useful when the catalog is the reference and other tools or teams need to hear about what was added.

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
an e-commerce manager wants a ticket opened for the content team each time a product is added, so the description gets written.
Watch out
importing a whole catalog at once can return a batch large enough for Zapier's flood protection to hold it back.
10

New Project

Polling trigger

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

Brings every project created in Axonaut into Zapier. Projects are where delivery is organized, so this trigger fits teams that run their production in Axonaut as well as their sales.

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 consultancy wants an event logged on the client account when its project starts, so account managers see it without opening the project.
Watch out
there is no update trigger, so later changes to the project never reach the Zap.
11

New Quotation

Polling trigger

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

Listens for new quotations in Axonaut. Like New Opportunity, it asks you to choose a quotation status before testing, and only quotes created in that status come through.

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 sales assistant wants an event on the account each time a quote is issued, so nobody sends a second one by mistake.
Watch out
a quote that is accepted later does not come back through this trigger, since each quote is read only once.
12

New Task

Polling trigger

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

Hands each new Axonaut task to Zapier as soon as it is spotted. Tasks are the to-dos you assign inside the CRM, so this is the trigger for workflows that react to work being handed out.

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
an operations manager wants every new task copied into a support ticket so it shows up in the team queue.
Watch out
with the free interval, a task created right after a check can wait up to 15 minutes.
13

New Ticket

Polling trigger

In Zapier“Triggers when a new support ticket is created.”

Kicks in when a support ticket is opened in Axonaut. It is the counterpart of New Closed Ticket: one starts the story, the other ends it, and you can run a Zap on each.

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 support lead wants an event logged on the customer's company so sales sees the issue before the next call.
Watch out
do not end this Zap with Create Ticket, or each new ticket spawns another one.
Actions

Axonaut actions on Zapier

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

1

Create Company and Employee

Action

In Zapier“Creates a new Company and its Employee”

Creates the company and its first contact in one go. You give it a company name and the employee's email, both required.

When to use it
a signup form gives you both the business and the person, and you want them linked from the start.
Watch out
the name is the company's, not the person's, and the email is the employee's. To find the contact before creating anything, use the find-or-create variant of Search Employee, below.
2

Create Employee

Action

In Zapier“Creates an Employee into a Company”

Attaches a new contact person to a company that already exists. The company ID is required, which means an earlier step has to know which company it is.

When to use it
a second contact at an existing client needs adding to the right account.
Watch out
an Axonaut ID, not a name. Get it from a trigger or a search step before this action.
3

Create Event

Action

In Zapier“Creates an Event”

Logs an event in Axonaut with its content, required, and an optional status saying whether it is already done. It is the way to leave a trace of what happened outside the CRM.

When to use it
a call booked or a ticket closed should show up in the account history.
4

Create Expense

Action

In Zapier“Creates an Expense”

Writes an expense into Axonaut. The tax amount is required and is typed as a plain number.

When to use it
receipts approved in another tool should land in the accounting side of Axonaut without a second entry.
Watch out
map a number into the tax field, not a text with a currency sign.
5

Create Invoice

Action

In Zapier“Creates an Invoice”

Issues an invoice with its lines: each one needs a name, a unit price without taxes and a quantity. The invoice is addressed through the email of an employee of the client company.

When to use it
an order paid elsewhere has to produce the matching invoice in Axonaut.
Watch out
that employee must already exist in Axonaut; create the contact first.
6

Create Invoice Payment

Action

In Zapier“Creates an Invoice Payment”

Marks a payment against an existing invoice. It wants the invoice ID, the amount, the payment date and a number for the payment nature, from 1 for debit to 6 for other.

When to use it
a payment confirmed by your bank or payment tool should close the invoice in Axonaut.
Watch out
the date must follow the RFC3339 format; left empty, the payment is dated at the time of the run.
7

Create Opportunity

Action

In Zapier“Creates an opportunity”

Opens a deal in one of your pipes. It is the most demanding action of the list: amount, probability, pipe, step and the business manager's email are all required.

When to use it
a qualified lead must appear in the sales pipeline at the right step.
Watch out
pipe and step use their exact Axonaut names, and the manager's email must belong to an Axonaut user.
8

Create Product

Action

In Zapier“Creates a Product”

Adds an item to the Axonaut catalog with just a product name required. Handy when the catalog is maintained somewhere else first.

When to use it
a new service is approved by the team and should be ready to quote right away.
Watch out
keep it away from a Zap that starts on New Product.
9

Create Prospect

Action

In Zapier“Creates a prospect / customer”

Adds a prospect or a customer to Axonaut from whatever your trigger brought in. Only the company name is required, so it is the lightest way to get an account into the CRM.

When to use it
a lead from your website becomes a company record without anyone retyping it.
Watch out
the name is the company's, not the person's. Contacts go through the actions below.
10

Create Quotation

Action

In Zapier“Creates a Quotation”

Drafts a quote attached to a company, identified by its Axonaut ID, which is required. An option makes the quote payable online.

When to use it
an opportunity reaches the point where a quote should go out without the rep building it by hand.
Watch out
online payment only works if Stripe or GoCardless is already enabled on your Axonaut account.
11

Create Supplier

Action

In Zapier“Creates a Supplier”

Records a supplier in Axonaut with only its name required. It keeps the purchasing side of the CRM in step with wherever suppliers are first approved.

When to use it
a procurement form approves a new vendor and you want it ready in Axonaut before the first expense.
12

Create Ticket

Action

In Zapier“Creates a Ticket”

Opens a support ticket in Axonaut; the title is the only required field. Simple enough to turn almost any event into a to-do for the support team.

When to use it
a complaint received by email or form should become a ticket with a clear title.
Watch out
never in a Zap triggered by New Ticket.
13

Find Expense

Action

In Zapier“Finds an Expense by ID”

Reads one expense by its ID and passes its data to the next steps. Zapier files it among the actions, not under the searches heading, so look for it in the main list.

When to use it
a step already holds the expense ID and a later step needs the full record.
Watch out
only the ID works; there is no lookup by amount or label.
14

Find Product

Action

In Zapier“Finds a Product”

Fetches a catalog product from its product ID, required. Like Find Expense, it sits among the actions rather than in the searches list.

When to use it
you have the product ID from a previous step and need its details to build an invoice line.
Watch out
without the exact ID there is nothing to find.
Searches

Axonaut searches on Zapier

6 search steps look for data that already exists in Axonaut, so a later step can use it.

Search steps sit at the bottom of the Action event list, under SEARCH. Some action fields also offer + Add search step, which inserts the search just before and wires its result in. Most Axonaut searches expect an ID, so they shine when an earlier step already carries it. Three settings decide what happens when the result is not the one expected.

1

Find Company

Search

In Zapier“Finds a Company”

Retrieves a company from its Axonaut identifier, which is required. The result feeds later steps with the company record.

When to use it
a Zap has the company ID and needs the full account before writing a quote.
Watch out
it does not search by name; Search Company is the one for that kind of lookup.
2

Find Contract

Search

In Zapier“Finds a Contract”

Pulls a contract by its unique ID, which is required. Once found, its details are available to every step after it in the Zap.

When to use it
a ticket mentions a contract ID and you want the contract data next to it before writing back.
Watch out
a contract number typed by a customer is not always the Axonaut ID.
3

Find Quotation

Search

In Zapier“Finds a Quotation by ID”

Gets a quotation by its ID and hands it to the next steps, typically to read it before acting on it.

When to use it
a payment arrives with a quote reference and you need that quote's details to continue.
Watch out
an ID that does not exist stops the Zap unless you change the no-result setting.
4

Find Supplier

Search

In Zapier“Finds a Supplier”

Looks up a supplier from its unique identifier in Axonaut. Useful on the purchasing side, next to Create Expense.

When to use it
an approved purchase carries the supplier ID and you want the supplier record before logging the cost.
5

Search Company

Search

In Zapier“Searches for a Company”

Searches the companies of your Axonaut account. The listing documents no particular field for it, so open it in the editor to see what it lets you search on.

When to use it
before creating an employee, to find the company that should receive it.
6

Search Employee

SearchFind or create

In Zapier“Searches an Employee”

Searches the employees stored in Axonaut. It also comes as Find Employee or Create Company and Employee: the same search with the create box ticked, which creates the company and the contact when nothing matches.

When to use it
before invoicing, to be sure the contact exists.
Watch out
the editor shows two lines, but it is one search.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap and skips the steps that needed it. Switched on, the Zap carries on with empty values.
  2. Create X if it doesn't exist yet?
    Ticking it turns the search into a find-or-create: the setting above disappears and Zapier asks for the fields needed to create the missing item.
  3. If multiple search results are found?
    Three ways out: keep the first match (the default), stop the Zap, or pass every match on at once.
When it breaks

When the Axonaut Zap breaks

Zapier attaches no help article to Axonaut, and no app-specific limit is documented. What breaks is the general behavior of Zaps, and a CRM full of create actions makes some of it more likely.

Four cases to know before you publish. If one of them hits you anyway, the Zapier troubleshooting page is the next stop.

  • The past is never picked up

    A Zap only reacts to what happens after it is switched on. Companies, invoices or tickets that already existed stay where they are; moving that backlog is a separate job.

  • A Zap that sets itself off

    New Company plus Create Prospect, New Ticket plus Create Ticket: a Zap that writes where its own trigger looks restarts again and again and burns through tasks fast.

  • Bulk imports get held back

    Import a catalog or a client list and the trigger may return a huge batch at once. Zapier's flood protection can hold it back before anything runs.

  • No duplicates, by design

    Zapier remembers what it has already seen on a polling trigger, so the same item never starts the Zap twice. An item edited later does not come back either.
Need help

Need help automating Axonaut with Zapier?

A person reads every message.

FAQ

Axonaut Zapier integration: frequent questions

01Is the Axonaut Zapier integration free?
Yes, it works from the free plan because Axonaut is not a premium app. The free plan gives you 100 tasks per month and unlimited Zaps, but each Zap is limited to two steps: one trigger and one action. As soon as you add a filter, a search step or a second action, the Zap becomes multi-step and needs a paid plan. You also need an Axonaut account of your own, since Zapier only connects to an existing one.
02How many tasks does an Axonaut Zap use?
One task per action that succeeds, nothing for the trigger. Zapier checking Axonaut for new items costs nothing, however often it looks. A Zap that creates an opportunity and then logs an event uses two tasks per run, so a busy pipeline can eat the free allowance of 100 tasks quickly. An action that fails is not counted. A few apps and actions take more than one task when they complete, so watch your usage during the first days.
03Is Axonaut on Zapier real time?
No. All 13 Axonaut triggers are polling triggers: Zapier asks Axonaut for new items at a fixed interval instead of being told the moment they happen. That interval is 15 minutes on the free plan, 2 minutes on Professional and 1 minute on Team and Enterprise. On a paid plan you can also run a check by hand from the editor. The trigger type comes from Axonaut's own API and cannot be changed in Zapier.
04What does it take to connect Axonaut to Zapier?
An Axonaut account, nothing more. In Zapier, open Apps, click + Add connection, pick Axonaut, then sign in and grant access in the tab that opens. If your Zaps will touch records owned by someone else, your Axonaut user needs read or write rights on them. Check also the requirements of the actions you plan: Create Opportunity needs the email of an Axonaut user and the exact names of a pipe and step.
05Why does an Axonaut search find nothing?
Usually because it expects an ID. Find Company, Find Contract, Find Quotation and Find Supplier all look things up by their Axonaut identifier, not by a name or an email. If the previous step only carries a name, the search comes back empty and, with default settings, the Zap stops there. Either pass the ID from a trigger that brings it, or use Search Company or Search Employee, and decide in the settings whether an empty result should stop the run.
06What if the Axonaut action you want is missing?
Then the Zap cannot do it directly. The Axonaut listing has no update and no delete action: every action creates something or reads one record by its ID. Changing the status of an existing quote or merging two companies has to happen in Axonaut itself. Look at the full list above before building, and if a workflow depends on an update, check whether another automation tool or a direct use of the Axonaut API covers it.
07Zapier, Make or n8n for Axonaut?
It depends on your criteria. Zapier gives you a ready-made Axonaut connection with 33 operations and a guided editor, in exchange for a polling interval and billing by the task. For Make and n8n, check first which Axonaut operations each one offers, how it bills and who hosts the tool. The right pick is the one that covers the operations your workflow depends on, at a cost you can read clearly for your volume.
Same platform

Other docs you might need on this stack.

Browse all integrations