Resources · Make integration

WeSupply Make integrationAutomate WeSupply with Make.

Orders live in one tool, shipment updates in another, and WeSupply needs both. The WeSupply Make integration gives you 3 action modules to push that data in without code. This page shows how to link your account and build a first scenario.

Try the WeSupply integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the WeSupply Make integration do?

The WeSupply Make integration lets a scenario (the automation you build in Make, a chain of bricks called modules) send data into WeSupply. The app offers 3 action modules and no trigger, so another app or a schedule starts the flow, and WeSupply receives the result.

Orders that reach WeSupply on their own. Your shop or ERP creates the order, and Import an Order passes it to WeSupply with the connection you set up once. Nobody retypes it.

Shipments that stay current. When a carrier or a warehouse tool reports a change, Update a Shipment writes it back into WeSupply, so the shipment in WeSupply matches what really happened.

Everything the list does not cover. Make an API Call reaches any endpoint of the WeSupply API with the same connection. It asks for more care, since you read the WeSupply API docs to know what to send.

What Make does not do here: WeSupply has no trigger in Make, so a scenario cannot start on a WeSupply event. The Make documentation for this app also warns that its content is AI-generated and may contain mistakes, so check anything critical with WeSupply. For a wider view of the tool, read our Make review, or compare both platforms in n8n vs Make. If you prefer a guided start, see Make training.

Connect

How do you connect WeSupply to Make?

  1. 01

    Get your WeSupply credentials

    You need an active WeSupply account. In WeSupply, open Settings, then Webhook & API, then OAuth Credentials, and copy the Client ID and the Client secret shown on screen.

  2. 02

    Add a WeSupply module

    In your Make scenario, add any WeSupply module and click Create a connection. The Connection name field is optional; a clear name helps when you later run several WeSupply accounts side by side.

  3. 03

    Paste the credentials

    Enter the credentials copied from WeSupply, or follow the on-screen instructions, and save. That connection (your WeSupply account linked to Make) is then reused by every WeSupply module you add.

First scenario

Your first scenario with WeSupply

GoalWhen your store records a new order, Make imports it into WeSupply.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. The first module comes from the app where your orders are born, since WeSupply has no trigger of its own.

  2. 02

    Pick the order source

    Search that app by name, choose the module that returns new orders and link its account. Each order it finds travels on as a bundle, one item passed from a module to the next.

  3. 03

    Add Import an Order

    Click the + on the right of the first module, search WeSupply and pick Import an Order. Select your WeSupply connection, then map the order data coming from the previous module.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open the bubbles to read the bundles each module received, then check in WeSupply that the order arrived as expected.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module. A new scenario runs every 15 minutes by default, and the Free plan cannot go below that. Then switch the scenario on.

Modules

What the WeSupply modules do

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

WeSupply1

Import an Order

ActionIn the docs only

Import an Order hands WeSupply an order that was created somewhere else, so the order exists in WeSupply without anyone copying it by hand. It is the natural second step after a module that spots new orders in your store or ERP.

When to use it
the moment a sale is confirmed in your shop and WeSupply should start following it.
Watch out
each imported order counts as one operation, an execution Make bills on your plan, so a large backlog consumes quickly.
WeSupply2

Make an API Call

ActionIn the docs only

Make an API Call opens the rest of the WeSupply API to your scenario, using the connection you already created. You get access to whatever the two named modules leave out, without setting up authentication a second time.

When to use it
a WeSupply action you need has no dedicated module in Make.
Watch out
you choose the endpoint and write the request yourself, so keep the WeSupply API documentation open while you build it.
WeSupply3

Update a Shipment

ActionIn the docs only

Update a Shipment changes a shipment that WeSupply already knows, so what WeSupply shows keeps pace with the carrier or the warehouse. As its name says, it works on an existing shipment rather than creating one.

When to use it
your logistics tool reports a new status for a parcel already registered in WeSupply.
Watch out
the module needs to know which shipment to change, so map that reference from the earlier module before running it.
Need help

Need help automating WeSupply with Make?

A person reads every message.

FAQ

Questions about WeSupply and Make

01Is the WeSupply Make integration free?
Yes, on the Make side. WeSupply is a standard app, available 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 (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution, with usage counted in credits each month. Your WeSupply subscription is separate and handled by WeSupply.
02What do you need to connect WeSupply to Make?
You need an active WeSupply account and API access. The Make documentation asks for an API Key and describes OAuth credentials for the setup. In WeSupply, go to Settings, then Webhook & API, then OAuth Credentials, and copy the Client ID and the Client secret. In Make, add a WeSupply module, click Create a connection, name it if you wish and paste those values. The connection then serves all 3 WeSupply modules in your scenarios.
03Can a WeSupply event start a Make scenario?
No. WeSupply has no trigger in Make, neither scheduled nor instant, so the scenario has to start somewhere else. Two options exist. Put a trigger from another app first, for example the store where orders appear, and add the WeSupply module after it. Or start the scenario on its own schedule, set on the first module: every 15 minutes by default, 15 minutes at the shortest on the Free plan and 1 minute on paid plans.
04What if a WeSupply module is missing in Make?
Use Make an API Call. It reaches any endpoint of the WeSupply API with the connection you already have, so an action outside Import an Order and Update a Shipment is still possible. You pick the endpoint and build the request from the WeSupply API documentation. Keep in mind that the Make documentation for this app is flagged as AI-generated and may contain mistakes, so confirm important details with WeSupply support before relying on them.
05Should you use Make or n8n for WeSupply?
It depends on what you need to cover. In Make, WeSupply brings 3 modules: order import, shipment update and a generic API call that reaches the rest of the API. None of them starts a scenario, so another app or a schedule leads the flow. Before choosing n8n, check whether it offers a WeSupply node and which actions that node covers, then compare with this list. The comparison page linked higher up sets the two platforms side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations