Resources · Make integration

AX Semantics Make integrationAutomate AX Semantics with Make.

Can Make feed and watch your AX Semantics documents without code? The AX Semantics Make integration gives you 8 modules: 1 scheduled trigger, 6 actions and 1 search. This page shows how to link your account, build a first scenario and pick the right module.

Try the AX Semantics integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the AX Semantics Make integration do?

The AX Semantics Make integration lets Make manage the documents in your AX Semantics account. You build a scenario, which is the automation you set up in Make as a chain of modules, and it adds, updates, finds or deletes documents for you, or reacts when content has been generated.

Product data that arrives by itself. A new row lands in another app you already use. Make passes it to Add a Document, and AX Semantics gets a fresh document without anyone copying fields by hand.

Generated text that leaves AX Semantics on its own. Watch Generated Content picks up new output on the scenario's schedule, and the next module sends it wherever your team publishes or reviews it.

A tidy account. Search Documents finds the documents that match, then Update a Document or Delete a Document handles each one, so stale records stop piling up.

The official doc gives no field list and no numeric limit for this app, so this page names none. When a listed module falls short, Make an API Call reaches the rest of the AX Semantics API with the same connection. The same app often exists as an n8n node too; the n8n vs Make comparison lays out the criteria. New to the editor? The Make training starts from zero, and the Make pricing page explains how operations are counted.

Connect

How do you connect AX Semantics to Make?

  1. 01

    Copy your Refresh Token

    Log in to AX Semantics and open API Access. Copy the Refresh Token value and keep it somewhere safe: Make asks for it in a moment, and it is the key that links your account.

  2. 02

    Create the connection in Make

    Add any AX Semantics module to your scenario and click Create a connection. A connection is your AX Semantics account linked to Make once and reused by every module of the app. The Connection name field is optional.

  3. 03

    Paste the token and save

    Paste the value into the Refresh Token field and click Save. If AX Semantics asks you to authenticate and confirm access, accept it, and the module can then read your account.

First scenario

Your first scenario with AX Semantics

GoalWhen a new record shows up in another app, Make adds a matching document in AX Semantics.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Pick the app where your source records live and choose its trigger as the first module.

  2. 02

    Pick Add a Document

    Click the + on the right of that first module, search for AX Semantics and pick Add a Document. Select your connection or click Create a connection.

  3. 03

    Map the data

    Fill the module fields with data from the first module. Once the connection exists, Make lists what it can read in your account, so you pick from a menu instead of typing.

  4. 04

    Test with Run once

    Click Run once. Each module shows the bundles it received, a bundle being one item passed along, so you can check that the new document looks right.

  5. 05

    Schedule and switch on

    Open the clock on the first module; a new scenario runs every 15 minutes by default. Adjust it if needed, then switch the scenario on so it keeps working without you.

Triggers

What starts an AX Semantics scenario

1 module starts a scenario when something happens in AX Semantics. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by AX Semantics as soon as it happens.

AX Semantics1Watch Generated Content

Watch Generated Content

triggerIn the docs only

This trigger hands your scenario the content AX Semantics has generated, so the text can move on to the next step without a manual export. A trigger is the first module, the one that decides when the scenario starts.

How it fires
scheduled. Make checks AX Semantics on the scenario's schedule, every 15 minutes by default, and the Free plan cannot go below that interval.
When to use it
your writers or reviewers work in another tool and should receive new output as soon as the scenario picks it up.
Watch out
the doc gives no description of this module; its type comes from its name, so confirm what it returns with Run once before you switch the scenario on.
Modules

Every AX Semantics module, explained

AX Semantics gives you 7 modules in 2 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Actions

5 modules
AX Semantics1

Add a Document

ActionIn the docs only

Creates a new document in your AX Semantics account from data that reached the scenario, so nobody has to rebuild the record by hand before text can be generated.

When to use it
a new item appears in another app and AX Semantics needs its own document for it.
Watch out
run it once per incoming bundle, or duplicates will pile up quickly.
AX Semantics2

Update a Document

ActionIn the docs only

Changes a document that already exists, which keeps AX Semantics in step with the source data instead of creating a second copy.

When to use it
a price, a name or a detail changed upstream and the existing document should reflect it.
Watch out
it needs to know which document to change, so place Search Documents before it when you do not already have that reference.
AX Semantics3

Get Details of a Document

ActionIn the docs only

Reads one document and returns what AX Semantics holds about it, ready to be mapped into the following modules of the scenario.

When to use it
you already know which document you need, for example right after the trigger, and want its full content rather than a list.
Watch out
it targets a single document; for several matches, start with the search module instead.
AX Semantics4

Delete a Document

ActionIn the docs only

Removes a document from your AX Semantics account, which keeps the workspace free of records that no longer match anything real.

When to use it
an item was withdrawn in the source app and its document has no reason to stay.
Watch out
the document leaves your account for good, so test on a throwaway document with Run once before activating.
AX Semantics5

Make an API Call

ActionIn the docs only

Sends your own request to any endpoint of the AX Semantics API, using the connection you already created, and returns the answer as a bundle.

When to use it
the listed modules do not cover what you need and the API does.
Watch out
this is the most technical module on the page, since you must know the endpoint yourself; keep it for the cases the other modules leave open.

Searches

2 modules
AX Semantics6

Search Documents

SearchIn the docs only

Looks through your AX Semantics documents and returns every match, one bundle per document, so the next modules can work through them one by one.

When to use it
before an update or a deletion, to find which documents the change concerns.
Watch out
a search can return zero, one or many results, and each result costs the following modules an operation, meaning one run of one module.
AX Semantics7

Setting Up AX Semantics Webhooks

ActionIn the docs only

This entry appears in the Make doc for the app under its searches, and its name points to webhook setup, a webhook being the way an app notifies another tool the moment something happens.

When to use it
only after reading the doc page, because the official sources give no description of what it does.
Watch out
do not treat it as an instant trigger; the only trigger this app lists is scheduled.
Need help

Need help automating AX Semantics with Make?

A person reads every message.

FAQ

AX Semantics and Make: common questions

01Is the AX Semantics Make integration free?
Yes, AX Semantics is a standard app in Make, so it works from the Free plan. That plan allows 2 active scenarios, a minimum of 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 bring the interval down to 1 minute and remove the cap on active scenarios. Your AX Semantics subscription is a separate matter that this page does not cover.
02What do you need to connect AX Semantics to Make?
You need an AX Semantics account and its Refresh Token. In AX Semantics, open API Access and copy the Refresh Token value. In Make, add an AX Semantics module, click Create a connection, paste the token in the Refresh Token field and click Save. If you are prompted to authenticate, confirm access. The connection is then reused by every AX Semantics module in your scenarios. Treat the token like a password and keep it private.
03Does the AX Semantics trigger work in real time?
No. Watch Generated Content is a scheduled trigger: Make checks AX Semantics on the scenario's schedule instead of being notified the moment content is ready. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. Paid plans can go down to 1 minute. The app lists no instant trigger in Make. If you need faster reactions, check whether your plan allows a shorter schedule before building around it.
04What if a module is missing for AX Semantics in Make?
It depends on what you need. The Make an API Call module can reach any endpoint of the AX Semantics API with the connection you already have, so it covers what the listed modules leave out. The doc gives no numeric limit for this app. If the API itself does not offer the action, the step has to be handled by another app in the scenario. Test such a call with Run once before you switch the scenario on.
05Should you use Make or n8n for AX Semantics?
It depends on your criteria rather than on the app. In Make, AX Semantics comes with a scheduled trigger, document actions, a search and a Make an API Call module, all through one connection. The same app often has an n8n node as well. Compare the modules each tool offers for your case, where your other automations already run, and which editor your team finds easier to maintain. Both tools can be tested on a small scenario before you commit.
Same platform

Other docs you might need on this stack.

Browse all integrations