Resources · Make integration

Axiom Make integrationAutomate Axiom with Make.

Can Make start Axiom for you when something happens in another tool? Yes. The Axiom Make integration gives you 2 modules, both actions, and no trigger. This guide is for people who know Axiom but are new to Make, and it walks you from the connection to a first working scenario.

Try the Axiom integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Axiom Make integration let you automate?

The Axiom Make integration links your Axiom account to Make so a scenario, the automation you build in Make, can act on Axiom without code. It has 2 modules: Trigger an Axiom, which launches an Axiom, and Make an API Call, which reaches the rest of the Axiom API.

Because Axiom has no trigger in Make, the scenario always starts somewhere else. Picture a sales team whose web form receives a lead: the form app fires first, then Trigger an Axiom launches the matching Axiom with the lead data mapped in.

A second pattern needs no other app at all. You put Trigger an Axiom first and let the schedule on that module start the run. A new scenario runs every 15 minutes by default, and you can change that clock later.

The third case is for builders who hit the edge of the listed modules. Make an API Call reuses the same connection and calls any endpoint of the Axiom API, so a missing module rarely blocks you.

Be aware that Make's own documentation for Axiom is thin: it says there is not enough public information to document the app fully. Expect to test each module with Run once before you trust it. If a run fails, the Make troubleshooting guide covers the usual causes, and Make pricing explains how operations are counted.

Axiom may also have an n8n node. If you are weighing both tools, read n8n vs Make before you commit.

Connect

How do you connect your Axiom account to Make?

  1. 01

    Add an Axiom module

    In your scenario, click the +, search for Axiom and pick one of its 2 modules. Then click Create a connection. A connection is your Axiom account linked to Make once and reused by both modules.

  2. 02

    Name the connection

    Make offers a name field for the connection. It is optional, but a clear label such as the workspace or the person who owns the account saves confusion when a teammate opens the scenario later.

  3. 03

    Authorize and save

    Depending on what Axiom asks for, either approve Make on the Axiom page that opens, or paste the key Axiom gives you. Click Save. The module now shows your account and is ready to be filled in.

First scenario

Build your first scenario with Axiom

GoalWhen a new record lands in another app, Make launches an Axiom with that record's data.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the canvas. This first module is the one that starts every run.

  2. 02

    Pick the starting app

    Choose the app where the event happens, a form tool or a CRM for instance, and pick its trigger. Link that account with Create a connection as you would for Axiom.

  3. 03

    Add Trigger an Axiom

    Click the + on the right of the first module, search for Axiom and pick Trigger an Axiom. Use your Axiom connection, then fill the fields Make shows and map values from the first module.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received, a bundle being one item passed along. Check that Axiom got the data you expected.

  5. 05

    Schedule and switch on

    Open the clock on the first module. The default is every 15 minutes; on the Free plan that is also the shortest interval. Set it, then switch the scenario on.

Modules

What can the Axiom modules do?

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

Axiom1

Make an API Call

ActionIn the docs only

This module lets you reach any endpoint of the Axiom API from your scenario, with the connection you already set up. It turns a gap in the module list into a request you write yourself.

When to use it
you need an Axiom action that Trigger an Axiom does not cover, and you have the Axiom API reference at hand.
Watch out
you build the request by hand, so run it with Run once and read the returned bundle before going live.
Axiom2

Trigger an Axiom

ActionIn the docs only

This one hands the work over to Axiom. Make does not describe it, so going by its name only: it launches one of your Axioms, the automations you set up in Axiom, when the scenario reaches it.

When to use it
an event in another app, such as a new signup or a paid order, should kick off an Axiom without anyone opening Axiom.
Watch out
Make publishes no field description for this module, so open it after connecting and check what it asks for.
Need help

Need help automating Axiom with Make?

A person reads every message.

FAQ

Axiom and Make: common questions

01Is the Axiom Make integration free?
Yes, Axiom is a standard app, so it works from the Make Free plan. The Free plan has limits worth knowing: 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) drop the interval to 1 minute and allow unlimited active scenarios. Usage is counted in operations, one operation being one module run on one bundle. Your Axiom subscription is a separate matter that Make does not cover.
02What do you need to connect Axiom to Make?
An Axiom account and a Make account are enough to begin. Make's documentation lists no specific prerequisite for Axiom. You add an Axiom module, click Create a connection, optionally name it, then either approve Make on the Axiom page or paste the key Axiom provides, and save. The same connection then serves both modules, Trigger an Axiom and Make an API Call, so you only go through this once per account. If the authorization screen asks for something unexpected, check it in your Axiom settings first.
03Does the Axiom integration react in real time?
No, Axiom has no trigger module in Make, so nothing in Axiom can start a scenario by itself. You have two ways around it. Start the scenario with a trigger from another app, ideally an instant one, which the app fires through a webhook the moment something happens. Or put Trigger an Axiom first and rely on the schedule of the scenario, every 15 minutes by default and never shorter than 15 minutes on the Free plan. Paid plans let you go down to 1 minute.
04What if the Axiom module you need is missing in Make?
Use Make an API Call. It reuses your Axiom connection and can reach any endpoint of the Axiom API, which covers what the two listed modules do not. You write the request yourself from the Axiom API reference, then test it with Run once. Keep in mind that Make says its own documentation for Axiom is limited, because there is not enough public information about the app. For anything the page does not answer, the Axiom side is the reference to check.
05Should you use Make or n8n for Axiom?
It depends on the tool your team already uses and knows. Axiom may also have an n8n node; check the n8n side before you compare. In Make you get 2 modules, including Make an API Call for anything missing, and a visual editor where you test with Run once. The fair way to choose is to build the same small flow in each and see which one your team reads more easily. No ranking holds for every case, and cost or speed claims between the two are not settled here.
Same platform

Other docs you might need on this stack.

Browse all integrations