Resources · Make integration

Storeman Make integrationAutomate Storeman with Make.

Can Make watch your Storeman items and spaces and act on them for you? Yes. The Storeman Make integration gives you 13 modules: 8 triggers, 3 actions and 2 searches. This guide shows how to link your account, build a first scenario and pick the right module.

Try the Storeman integration on MakeSee the 13 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Storeman Make integration do?

The Storeman Make integration links your Storeman account to Make, a no-code tool where you chain apps together. It notices when items or spaces are created, updated or deleted, and it can create items, highlight a space or list what your account holds, with no code to write.

Pass new work downstream. Watch Created Item starts a scenario (the automation you build in Make) each time an item appears, so the next app in the chain gets it without a copy and paste.

Feed Storeman from elsewhere. Create an Item turns a record from another app into a Storeman item. A form entry or a spreadsheet row can land in Storeman on its own.

Keep a trace of removals. Watch Deleted Item and Watch Deleted Space tell you what disappeared, which helps when a teammate asks where something went.

A word of honesty: Make's documentation for Storeman is thin. It says there isn't enough public information about the app to describe it fully, so no module comes with a field list or a description. Test each module on a sample before you rely on it, and see the Make troubleshooting guide if a run fails. If you are still choosing a tool, the n8n vs Make comparison lays out the criteria, and the Make training covers the editor from scratch.

Connect

How do you connect Storeman to Make?

  1. 01

    Add a Storeman module

    In a new scenario, click the +, search for Storeman and pick any module. Then click Create a connection. A connection is your Storeman account linked to Make once and reused by every Storeman module.

  2. 02

    Name it and authorize

    Give the connection a name if you like, something that says which account it is. Then either authorize Make on the Storeman page that opens, or paste the key Storeman gives you, depending on what the window asks for.

  3. 03

    Save the connection

    Click Save. Make now lists the Storeman data it can read in the module fields. The connection stays available the next time you add a Storeman module, so this step only happens once per account.

First scenario

Your first scenario with Storeman and Make

GoalWhen a new record shows up in another app, Make adds it to Storeman as an item.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the app where your records start (a form, a sheet) and choose its trigger.

  2. 02

    Add Create an Item

    Click the + on the right of that first module, search Storeman and pick Create an Item. Click Create a connection if your account isn't linked yet.

  3. 03

    Map the data

    Fill the fields of Create an Item with values from the first module. Each record travels as a bundle, one item passing from one module to the next, so you just click the values you want.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received. Open Storeman and check the new item looks the way you expect.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. Keep it or change it, then switch the scenario on.

Triggers

What can start a Storeman scenario?

8 modules start a scenario when something happens in Storeman. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Storeman as soon as it happens.

Storeman1Watch Created Item

Watch Created Item

triggerIn the docs only

Watch Created Item hands your scenario every item added to Storeman since the last check, one bundle per new item. You get a clean starting point for anything that should follow a new entry.

How it fires
scheduled, Make checks Storeman on the scenario's schedule, so nothing happens between two checks.
When to use it
pick it when only brand new items matter and edits to older ones should stay out of the flow.
Watch out
each new item costs at least one operation, the unit Make counts on your plan, so a busy account uses more of it.
Storeman2Watch Created Space

Watch Created Space

triggerIn the docs only

With Watch Created Space, a scenario starts when Make, at a scheduled check, finds a space that did not exist at its previous check. That gives you a hook to set things up around each new space instead of waiting for someone to notice it.

How it fires
scheduled, Make checks Storeman on the scenario's schedule.
When to use it
a new space should trigger a follow-up elsewhere, such as a note to the person in charge or a Highlight a Space right after.
Watch out
spaces renamed or changed are not new, so they stay invisible to this trigger.
Storeman3Watch Deleted Item

Watch Deleted Item

triggerIn the docs only

Here the goal is a record of what left Storeman: Watch Deleted Item returns the items removed since the last check. It is the only way in this list to react to an item disappearing.

How it fires
scheduled, Make checks Storeman on the scenario's schedule.
When to use it
you keep a log of removals in a sheet, or you want a teammate told when an item goes away.
Watch out
the item is gone from Storeman, so a later Storeman module will most likely find nothing to read. Save what you need from the bundle in the same run.
Storeman4Watch Deleted Space

Watch Deleted Space

triggerIn the docs only

Removing a space is rarely trivial, and Watch Deleted Space makes sure it doesn't go unnoticed. Your scenario receives each space deleted since Make last looked.

How it fires
scheduled, Make checks Storeman on the scenario's schedule.
When to use it
you want an alert, or a line in a log, every time a space is taken down, so nobody wonders later where it went.
Watch out
the documentation says nothing about what happens to the items of a deleted space. Test on a throwaway space before you build a cleanup flow on top of it.
Storeman5Watch Items

Watch Items

triggerIn the docs only

Watch Items gives your scenario items from Storeman at each check, without the created, updated or deleted wording of its neighbors. Think of it as the broad version of the item triggers.

How it fires
scheduled, Make checks Storeman on the scenario's schedule.
When to use it
when you are not sure which event matters yet and want to see what comes through first.
Watch out
the documentation does not say how it picks items or how it differs from Watch Created Item. Click Run once and read the bundles before you connect anything that writes data.
Storeman6Watch Spaces

Watch Spaces

triggerIn the docs only

For a scenario that should follow your spaces in general, Watch Spaces returns spaces from Storeman at every check. It is the space counterpart of Watch Items.

How it fires
scheduled, Make checks Storeman on the scenario's schedule.
When to use it
you are exploring what Storeman sends before settling on Watch Created Space or Watch Updated Space for a precise event.
Watch out
no official description explains which spaces it returns. Run it once on your account and look at the output bundles, then decide if the narrower triggers suit you better.
Storeman7Watch Updated Item

Watch Updated Item

triggerIn the docs only

Changes to existing items are what Watch Updated Item catches. Each item edited since the last check becomes a bundle, so the rest of the scenario can pass the new version along.

How it fires
scheduled, Make checks Storeman on the scenario's schedule.
When to use it
another tool must stay in step with Storeman whenever someone edits an item.
Watch out
avoid ending that same scenario with a module that edits the item again, or you risk feeding the trigger with your own changes. Test with Run once before switching on.
Storeman8Watch Updated Space

Watch Updated Space

triggerIn the docs only

Watch Updated Space tells your scenario which spaces were modified since Make's previous check. You find out about changes to a space without opening Storeman to look.

How it fires
scheduled, Make checks Storeman on the scenario's schedule.
When to use it
a change to a space should be echoed somewhere else, like a message to the team or an update in a tracking sheet.
Watch out
Highlight a Space may count as an update. If you use both, keep them in separate scenarios and test with Run once first.
Modules

What can Make do in Storeman?

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

Storeman1

Create an Item

ActionIn the docs only

Create an Item adds a new item to Storeman from data your scenario already holds, so nobody has to type it in again. It is the module that feeds Storeman from the outside.

When to use it
a form entry, an order or a row in a sheet should become a Storeman item on its own.
Watch out
the documentation lists no fields. Once the connection exists, Make shows what it accepts, so start with a test record.
Storeman2

Highlight a Space

ActionIn the docs only

Highlight a Space acts on one space of your Storeman account, as its name says, so a scenario can draw attention to it without anyone clicking in the app.

When to use it
right after Watch Created Space, to flag the new space for the team.
Watch out
no description explains what highlighting changes in Storeman. Run it once on a test space and check the result in the app before you let it touch real ones.
Storeman3

List Items

SearchIn the docs only

List Items pulls the items of your account into the scenario, each one as its own bundle. It answers the question of what is in there right now, rather than what just changed.

When to use it
you need the full set of items to copy them to a sheet or check them against another tool.
Watch out
a search can return zero, one or many bundles, and every module after it runs once per bundle, which adds operations.
Storeman4

List Spaces

SearchIn the docs only

Need the spaces of your account in hand? List Spaces returns them to the scenario, one bundle per space, so later modules can loop through them.

When to use it
you want an inventory of spaces in a sheet, or you need to pick one space before running Create an Item or Highlight a Space.
Watch out
an empty result stops the modules that follow it. Test with Run once to see what your account returns.
Storeman5

Make an API Call

ActionIn the docs only

Make an API Call lets you reach any endpoint of the Storeman API from your scenario, reusing the same connection. It is how you cover what the 12 other modules leave out.

When to use it
you need a Storeman feature that has no dedicated module, and you have the API reference at hand.
Watch out
this module asks you to know the endpoint and its parameters. It is the most technical option on this page, so try the dedicated modules first.
Need help

Need help automating Storeman with Make?

A person reads every message.

FAQ

Storeman and Make: common questions

01Is the Storeman Make integration free?
Yes, Storeman is a standard app in Make, available from the Free plan. That plan has limits you should know before you build: 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) lower the interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one per module run on one bundle. Your Storeman subscription is a separate matter.
02What do you need to connect Storeman to Make?
A Storeman account and a Make account are enough to start, since the documentation lists no other prerequisite. Add any Storeman module, click Create a connection, give it a name if you like, then authorize Make on the Storeman page or paste the key Storeman provides. Click Save and the connection is ready for every Storeman module in your scenarios. If the window asks for something you can't find, look in your Storeman account settings first, because Make's page for this app gives no specific setup steps.
03Do Storeman triggers in Make fire in real time?
No. Make's documentation lists the 8 Storeman triggers without describing them, but their Watch names point to scheduled triggers: Make checks Storeman on the scenario's schedule instead of being called by the app. The clock badge on the module confirms it. A new scenario checks every 15 minutes by default, and 15 minutes is also the shortest interval on the Free plan. Paid plans can go down to 1 minute. Between two checks nothing runs, so an item created right after a check waits for the next one. If speed matters, shorten the schedule on a paid plan rather than expecting an instant reaction.
04What if a Storeman module is missing in Make?
Use Make an API Call. This module can call any endpoint of the Storeman API with the connection you already set up, so it covers what the 12 other modules don't. You will need the Storeman API reference to know which endpoint to call. Keep in mind that Make's own documentation for Storeman is limited: it says there isn't enough public information about the app, so no module comes with a field list. Testing each step with Run once is the safest way to learn what comes back.
05Should you use Make or n8n for Storeman?
It depends on what you need to check first. On the Make side, the facts are clear: 13 Storeman modules, 8 of them triggers, plus Make an API Call for the rest, and the app works on the Free plan. For n8n, look up whether a Storeman node exists and what it covers before you compare, because this page doesn't document it. Then weigh the two on the modules you actually need, not on general claims. The n8n vs Make comparison on this site lists the criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations