Resources · Make integration

IntegrityNext Make integrationAutomate IntegrityNext with Make.

Can Make keep your IntegrityNext supplier records up to date for you? The IntegrityNext Make integration gives you 3 modules: two actions and one search. This page shows what they do, how to link your account and how to build a first working scenario.

Try the IntegrityNext integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the IntegrityNext Make integration do for you?

The IntegrityNext Make integration lets a Make scenario, meaning the automation you build as a chain of bricks called modules, write supplier records into IntegrityNext and read them back. You add the modules, link your account once, and Make handles the copying that you would otherwise do by hand.

Supplier records that follow your other tools. Put another app's data first in the scenario, then Create and Update Supplier writes each new or changed supplier into IntegrityNext, so the list there matches the one your team already maintains.

Supplier data sent where people read it. List Supplier Data pulls records out of IntegrityNext, and the next module passes them on to a spreadsheet, a report or a message. Each record travels as a bundle, one item handed from one module to the next.

Everything else the API allows. Make an API Call reaches parts of IntegrityNext that the two other modules leave out, with the same connection.

Know the limit before you start: Make itself states that its documentation for IntegrityNext is incomplete, because little public information exists about the app. Expect to test each module with real data. If you are new to the editor, the Make training covers the basics, and the n8n vs Make comparison helps if you are still choosing a tool.

Connect

How do you connect IntegrityNext to Make?

  1. 01

    Add an IntegrityNext module

    In your scenario, click the + and search for IntegrityNext, then pick any of its modules. The field for the account shows a Create a connection button: click it to open the connection window.

  2. 02

    Name the connection

    Giving the connection a name is optional, but it helps when several accounts live in the same Make workspace. A connection is your IntegrityNext account linked to Make once, then reused by every IntegrityNext module.

  3. 03

    Authorize and save

    Depending on what the window asks, either approve Make on the IntegrityNext page that opens or paste the key IntegrityNext gives you. Click Save, and the connection appears in the module.

First scenario

Your first scenario with IntegrityNext

GoalWhen a supplier is added or changed in another app, Make writes it into IntegrityNext.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Here the first module belongs to the app where your supplier list already lives.

  2. 02

    Add Create and Update Supplier

    Click the + on the right of that first module, search for IntegrityNext and choose Create and Update Supplier. Select your connection, or click Create a connection if this is the first time.

  3. 03

    Map the supplier data

    Fill the module fields by clicking into each one and picking the matching value from the first module. Make shows what the previous module returned, so no typing of names is needed.

  4. 04

    Test with Run once

    Click Run once to run the scenario a single time. Open the bubble above each module to read the bundles it received, then check the supplier inside IntegrityNext.

  5. 05

    Schedule and switch it on

    On the first module, set the schedule, which is every 15 minutes by default, then switch the scenario on. From then on, each run copies new supplier changes across.

Modules

What the IntegrityNext modules do

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

IntegrityNext1

Create and Update Supplier

ActionIn the docs only

You get a supplier record in IntegrityNext that is written or refreshed for you, straight from data that already sits in another tool. It is the module that turns your scenario into a sync rather than a report.

When to use it
a supplier is approved in your purchasing tool and should show up in IntegrityNext without anyone retyping it.
Watch out
Make publishes no description of this module, so run it once on a test supplier and look at the result in IntegrityNext.
IntegrityNext2

List Supplier Data

SearchIn the docs only

This search gives you the supplier records held in IntegrityNext, ready to reuse in the rest of the scenario. A search can return zero, one or many bundles, and every module placed after it then runs once per bundle.

When to use it
a buyer wants the supplier list copied into a shared spreadsheet so the whole team reads the same data.
Watch out
many results mean many operations, the unit Make counts on your plan, so filter early when you can.
IntegrityNext3

Make an API Call

ActionIn the docs only

With this module you reach any endpoint of the IntegrityNext API from your scenario, reusing the connection you already created. It covers what Create and Update Supplier and List Supplier Data do not offer.

When to use it
you need a piece of IntegrityNext data that neither of the two named modules touches.
Watch out
you write the request yourself, so keep the IntegrityNext API reference open and test each call with Run once.
Need help

Need help automating IntegrityNext with Make?

A person reads every message.

FAQ

Questions about the IntegrityNext Make integration

01Is the IntegrityNext Make integration free?
Yes, IntegrityNext is a standard app in Make, so it works from the Free plan. That plan keeps 2 scenarios active, waits at least 15 minutes between two scheduled runs, stops a run after 5 minutes, accepts files up to 5 MB and allows 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. This answer covers Make only: the IntegrityNext subscription itself is a separate matter between you and IntegrityNext.
02What do you need to connect IntegrityNext to Make?
An IntegrityNext account and a Make account are the starting point. Make's documentation lists no other prerequisite for this app and gives no official connection steps, because its coverage of IntegrityNext is marked as limited. The generic path applies: add an IntegrityNext module, click Create a connection, optionally name it, authorize Make or paste the key IntegrityNext provides, then click Save. If a request in that window is unclear, your IntegrityNext administrator is the right person to ask.
03Does the IntegrityNext integration react in real time?
No, because IntegrityNext has no trigger module in Make, so nothing inside IntegrityNext can start a scenario. You still have two ways to begin. The first is a schedule on the first module, every 15 minutes by default, with List Supplier Data placed first to read records. The second is to start from a trigger of another app, for example the tool where suppliers are first entered, and then send the data on to Create and Update Supplier.
04What if an IntegrityNext module is missing in Make?
Use Make an API Call. It calls any endpoint of the IntegrityNext API with the connection you already set up, so the gap left by the two named modules can be filled without a second login. Keep in mind that Make describes its IntegrityNext documentation as limited, so you will rely on the API reference from IntegrityNext to build the request. Test it with Run once before you switch the scenario on.
05Should you use Make or n8n for IntegrityNext?
It depends on the criteria that matter to your team. On the Make side, the facts are clear: 3 modules, a Free plan to start, and Make an API Call for the rest. Many apps also have an n8n node, so check whether IntegrityNext has one before deciding. Compare how each tool covers the actions you need, how you prefer to build, and who will maintain the workflow. The comparison page linked earlier on this page lays out those criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations