Resources · Make integration

SOS Inventory Make integrationAutomate SOS Inventory with Make.

Need your stock, orders and shipments to reach the rest of your tools? The SOS Inventory Make integration gives you 7 modules: six lists and one open API call. This page shows ops teams how to connect the account and run a first scenario.

Try the SOS Inventory integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the SOS Inventory Make integration let you do?

The SOS Inventory Make integration lets a Make scenario, the automation you build in Make, read your inventory data: invoices, items, locations, lots, sales orders and shipments. Each of those is a module, one brick of the scenario, and every record it returns becomes a bundle that the next module can use.

A shipping recap for the warehouse. List Shipments pulls your shipments, and the next module in the scenario can post them wherever the team already looks, so nobody has to open SOS Inventory to check what left.

A stock view per site. List Items can be filtered by location, type and tags, and List Locations gives you the sites themselves. Together they feed a sheet or a report that shows what sits where.

Lot tracking for quality checks. List Lots filters by status, archived state and location, which helps a quality lead follow the lots still in play without scrolling through old ones.

Know the limits before you start. The app has no trigger module, so SOS Inventory never starts a scenario by itself: Make runs it on a schedule or another app starts it. The six listed modules read data; for anything beyond those lists, Make an API Call reaches the rest of the SOS Inventory API. If you are still weighing tools, the n8n vs Make comparison and the Make review help, and Make pricing explains how operations are counted.

Connect

How do you connect SOS Inventory to Make?

  1. 01

    Add a module and open the connection form

    You need an active SOS Inventory account first. In your scenario, add any SOS Inventory module and click Create a connection. The connection is your SOS Inventory account linked to Make once, then reused by every module of the app.

  2. 02

    Give the connection a clear name

    The Connection name field is optional, but a name like the company or the environment helps a lot once several people share the same Make team and pick connections from a list.

  3. 03

    Paste your credentials

    Enter the credentials you copied from SOS Inventory, or follow the on-screen instructions. For the advanced setup, register an application in the SOS Inventory Developer portal and copy the Client ID and Client secret it shows you.

First scenario

Build your first scenario with SOS Inventory

GoalWhen the scenario runs on its schedule, Make lists your SOS Inventory locations, then the items in each one, so you get a stock view site by site.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big +. Search for SOS Inventory and pick List Locations as the first module.

  2. 02

    Link your account

    Click Create a connection and follow the steps above. Once the connection exists, Make can read your SOS Inventory data and fill the module with what it finds.

  3. 03

    Add the items

    Click the + on the right of the first module and add List Items. In its location filter, map the location returned by List Locations; Make shows what the previous module returned.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario one time, and you can open each module to read the bundles it received. Each module run on a bundle is an operation, the unit Make counts on your plan.

  5. 05

    Schedule and switch it on

    Open the clock on the first module, the Scheduling setting. A new scenario runs every 15 minutes by default; keep that or pick your own rhythm, then switch the scenario on.

Modules

What each SOS Inventory module does

SOS Inventory gives you 7 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

SOS Inventory1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

This module reaches any endpoint of the SOS Inventory API with the connection you already set up, so you are not stuck with the six lists.

When to use it
you need an endpoint of the SOS Inventory API that none of the six list modules covers.
Watch out
unlike the other modules, nothing is prepared for you here, so keep the SOS Inventory API documentation open while you fill it.
SOS Inventory2

List Invoices

Search

In Make“Lists invoices.”

List Invoices hands your SOS Inventory invoices to the scenario, one bundle per invoice, ready to send to accounting or a shared sheet.

When to use it
the finance side wants invoice data outside SOS Inventory without anyone exporting it by hand.
Watch out
a search can return zero, one or many invoices, and every one that goes through the next module costs an operation.
SOS Inventory3

List Items

Search

In Make“Lists all items optionally filtered by location, type, and tags.”

You get your catalog of items, and you can narrow it by location, type and tags so the scenario only carries the products that matter for the job.

When to use it
building a stock view for one warehouse, or a list of items that share a tag.
Watch out
without a filter the module lists all items, which can mean many bundles and many operations downstream.
SOS Inventory4

List Locations

Search

In Make“Lists locations.”

List Locations returns the sites defined in SOS Inventory, which gives the rest of the scenario a clean reference of where stock can live.

When to use it
before listing items or lots per site, or to keep a directory of warehouses in sync in another tool.
Watch out
each location comes out as its own bundle, so later modules run once per site unless you aggregate them.
SOS Inventory5

List Lots

Search

In Make“Lists all lots optionally filtered by status, archived, location.”

This one brings back your lots, with filters on status, archived state and location, so a quality or traceability flow only sees the lots it should.

When to use it
following the lots still active in one location, or reviewing the archived ones apart.
Watch out
set the archived filter on purpose, otherwise old lots can mix with the live ones in your results.
SOS Inventory6

List Sales Orders

Search

In Make“List Sales Orders”

Sales orders from SOS Inventory flow into the scenario one by one, so a sales or fulfillment team can see them in the tool they already use.

When to use it
feeding a team channel, a CRM or a planning sheet with the orders waiting to be prepared.
Watch out
the module only reads orders, so any other endpoint of the API goes through Make an API Call.
SOS Inventory7

List Shipments

Search

In Make“Lists shipments.”

With List Shipments, what left the warehouse becomes data your scenario can pass on, one bundle per shipment, for customer service or reporting.

When to use it
your support team works in another tool and needs to know whether an order has left.
Watch out
the list can grow quickly, so test with Run once and check how many bundles come back before switching the scenario on.
Need help

Need help automating SOS Inventory with Make?

A person reads every message.

FAQ

SOS Inventory and Make: common questions

01Is the SOS Inventory Make integration free?
Yes, on the Make side. SOS Inventory is a standard app, so it is available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. You still need your own active SOS Inventory subscription, which is billed by SOS Inventory, not by Make.
02What do you need to connect SOS Inventory to Make?
An active SOS Inventory account and an API key. In Make, add any SOS Inventory module, click Create a connection, optionally name it, then enter the credentials copied from SOS Inventory. For the advanced setup, register an application in the SOS Inventory Developer portal, enter the callback URI if the portal asks for one, and copy the Client ID and Client secret shown after registration. The connection is then reused by all seven modules.
03Can SOS Inventory start a Make scenario in real time?
No. The app has no trigger module, scheduled or instant, so SOS Inventory cannot start a scenario on its own. You have two ways around it. Put an SOS Inventory list module first and set the Scheduling clock: a new scenario runs every 15 minutes by default, and 15 minutes is also the minimum on the Free plan. Or start the scenario from another app that has a trigger, then call the SOS Inventory modules after it.
04What if a module is missing in the SOS Inventory Make integration?
Use Make an API Call. It calls any endpoint of the SOS Inventory API with the same connection, which covers what the six list modules do not. Check first in the SOS Inventory API documentation that the endpoint you need exists, then test it with Run once. You build the request yourself, so the SOS Inventory API documentation becomes your reference. Note that the Make documentation for this app is marked as AI-generated from the vendor docs, so check important details with SOS Inventory directly.
05Should you use Make or n8n with SOS Inventory?
It depends on your team rather than on the app. On Make, SOS Inventory comes with seven modules: six lists and Make an API Call, all usable from the Free plan and built in a visual editor where each module shows the bundles it received. Many apps also have an n8n node, so check what exists there for SOS Inventory before deciding. If your other automations already live in one tool, keeping SOS Inventory in the same place is usually the simplest choice.
Same platform

Other docs you might need on this stack.

Browse all integrations