Resources · Make integration

shopix Make integrationAutomate shopix with Make.

Every new shopix order can start an automation on its own. The shopix Make integration gives you 2 modules: one trigger that watches new orders and one API call. This page shows you how to link your account and build a first working scenario.

Try the shopix integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the shopix Make integration do for you?

The shopix Make integration links your shopix account to Make so that new orders flow into an automation without anyone copying them by hand. In Make, that automation is called a scenario: a chain of modules, each one a single brick that watches, acts or searches.

Pick up each new order. Watch new orders hands every fresh order to your scenario as a bundle, which is simply one item passed from one module to the next. From there, the order can move into any other app you use in Make, such as a spreadsheet for the finance team or a chat channel for the warehouse.

Reach what the catalog leaves out. Make an API call talks to the shopix API directly, with the same connection. It is the way to cover any request the order trigger does not handle, as long as the shopix API offers it.

Know the gaps before you build. The Make documentation for shopix is marked as limited: Make says there is not enough public information about the app to write a full guide. The page you are reading sticks to what that documentation lists, so expect to test with Run once and check each bundle yourself. If a scenario stalls, the Make troubleshooting guide walks through the usual errors.

New to the editor? The Make training covers scenarios, modules and mapping from zero. And if you are also weighing n8n, which often has a node for the same app, read n8n vs Make before you commit to one tool.

Connect

How do you connect shopix to Make?

  1. 01

    Add a shopix module

    Open your scenario, click the + and search for shopix. Pick any of its two modules, then click Create a connection. A connection is your shopix account linked to Make once, and every shopix module reuses it afterwards.

  2. 02

    Name the connection

    Give the connection a name you will recognize later, for example the store or the team it belongs to. This step is optional, but it saves guesswork the day you manage more than one shopix account in the same Make organization.

  3. 03

    Authorize and save

    Depending on what shopix asks for, either approve Make on the shopix authorization page or paste the key shopix gives you. Then click Save. The module can now read your account.

First scenario

Your first scenario with shopix

GoalWhen a new order lands in shopix, Make sends it to the shopix API request you choose.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the big + to add the first module. That empty canvas is where the whole flow lives.

  2. 02

    Set the order trigger

    Search for shopix, choose Watch new orders and select your connection. Fill in the fields Make shows; once the connection works, Make lists what it can read from your account.

  3. 03

    Add the API call

    Click the + on the right of the trigger and add Make an API call. Point it at the shopix API request you need and map values from the order bundle the trigger produced.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received, so you can open the order data and confirm the call went through as planned.

  5. 05

    Schedule and switch it on

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

Triggers

What starts a shopix scenario?

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

shopix1Watch new orders

Watch new orders

triggerIn the docs only

Your scenario picks up orders that are new in shopix since its last check and passes each one along as a separate bundle, ready for the next module to use.

How it fires
scheduled. Make checks the app on the scenario's schedule. Make's documentation gives no type for this module, so this reading comes from its name and deserves a quick test.
When to use it
whenever a sale should set something in motion, like alerting the person who ships or logging the order somewhere else.
Watch out
orders wait until the next check, 15 minutes at the earliest on the Free plan.
Modules

What else can Make do with shopix?

shopix gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

shopix1

Make an API call

ActionIn the docs only

With this module you can call any endpoint of the shopix API from your scenario, reusing the connection you already created, so nothing new to set up.

When to use it
as soon as you need something from shopix that Watch new orders does not give you, since the app has no other module in Make.
Watch out
Make's shopix documentation is marked as limited, so you need the endpoint and its parameters from shopix itself.
Need help

Need help automating shopix with Make?

A person reads every message.

FAQ

Questions about the shopix Make integration

01Is the shopix Make integration free?
Yes, shopix is a standard app, so it works on the Make Free plan. That plan has real limits though: 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) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module per bundle, so each new order that goes through two modules uses two.
02What do you need to connect shopix to Make?
A shopix account and a Make account. The Make documentation lists no other prerequisite and no specific sign-in steps for shopix, so the generic flow applies: add a shopix module, click Create a connection, optionally name it, then either authorize Make on the shopix page or paste the key shopix provides, and click Save. If you are unsure which credential shopix expects, check your shopix account settings before you start, because Make does not say which of the two methods applies to this app.
03Does the shopix trigger in Make fire in real time?
No. Watch new orders works as a scheduled trigger: Make checks shopix on the scenario's schedule instead of being notified the moment an order is placed. Note that Make's documentation does not state the type, so this is read from the module's name. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. On a paid plan you can go down to 1 minute. If you need faster handling, that is the setting to change, not the module.
04What if the shopix module you need is missing in Make?
Use Make an API call. It reaches any endpoint of the shopix API with the connection you already have, which is how you cover everything beyond the order trigger. Keep in mind that Make marks its shopix documentation as limited, due to a lack of public information about the app. That means you will find the endpoints and their parameters on the shopix side, not in Make. Test every call with Run once and read the returned bundle before you switch the scenario on.
05Should you use Make or n8n for shopix?
It depends on what you already run. n8n often has a node for the same app, so check whether shopix is covered there before choosing. On the Make side, you get two modules for shopix: Watch new orders to start a scenario and Make an API call for everything else, plus a visual editor where you test with Run once. If your other automations already live in one of the two tools, keeping shopix in the same place is usually the simpler choice. The comparison page linked above lays out the criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations