Resources · Make integration

ShipStation Make integrationAutomate ShipStation with Make.

Can your orders and labels in ShipStation move on their own? The ShipStation Make integration gives you 40 modules, four of them instant triggers. This guide is for shipping and ops teams: connect the account, build a first scenario, then pick the right module.

Try the ShipStation integration on MakeSee the 40 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the ShipStation Make integration automate?

The ShipStation Make integration links your ShipStation account to Make, a no-code tool where you build a scenario: a chain of modules that runs on its own. ShipStation can start that chain the moment an order or a shipment changes, and Make can then create, tag, assign or look up orders, products, stores and warehouses for you.

Orders taken outside your store land in ShipStation. A phone order typed into a form or a spreadsheet row becomes a real order through Create Order, so the packing team works from a single queue.

Each new order finds its owner. Listen for Order Events fires as soon as ShipStation receives or edits an order; Assign User to Order and Add Tag to Order then route it to the right person, with a tag the whole warehouse can filter on.

A printed label tells the rest of the business. Listen for Shipment Events fires when a label is generated, which is the right moment to warn customer support or update a sales tool in the next module. Keep in mind that marking an order as shipped does not fire it.

A few limits before you start. Make's documentation for ShipStation is marked as limited, and the app has no Make an API Call module, so what you can do stops at these 40 modules. The Update modules do not accept partial changes: they expect the whole record every time. If you are weighing Make against n8n, the n8n vs Make comparison puts the two side by side, and Make training walks you through your first scenarios step by step. When a run fails, Make troubleshooting lists the usual fixes.

Connect

How do you connect ShipStation to Make?

  1. 01

    Open a ShipStation module

    In your scenario, add any ShipStation module, for example Create Order. Under the connection field, click Create a connection. A connection is your ShipStation account linked to Make once, then reused by every ShipStation module.

  2. 02

    Give the connection a name

    This step is optional but pays off later. Type a name that says which account it is, such as the store or the team it belongs to, so nobody picks the wrong one when several accounts sit side by side.

  3. 03

    Authorize and save

    Follow what Make asks next: either approve access on the ShipStation page that opens, or paste the key that ShipStation gives you. Click Save. The module now lists the stores, orders and warehouses Make can read.

First scenario

Your first scenario: send outside orders to ShipStation

GoalWhen a new order is recorded in another tool, Make creates the same order in ShipStation.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big +. Add the module of the tool where these orders are written today, a form or a spreadsheet, and connect that tool.

  2. 02

    Add Create Order

    Click the + on the right of that first module, search for ShipStation and pick Create Order. Click Create a connection if you have not linked your account yet.

  3. 03

    Map the order data

    Fill the fields of Create Order with values from the first module: click a field and pick the matching item that arrived in its bundle, the single record passed from one module to the next.

  4. 04

    Test with Run once

    Add one test order in your source tool, then click Run once. Open the bubble above each module to read the bundle it received, and check the new order in ShipStation.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set Scheduling. A new scenario checks every 15 minutes by default. Then switch the scenario on so it keeps working without you.

Triggers

Which ShipStation triggers start a scenario?

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

ShipStation1Listen for Order Events

Listen for Order Events

Instant trigger

In Make“Receives notifications about new and updated orders.”

This trigger starts your scenario whenever ShipStation receives a new order or an existing one changes, and hands Make the order as one bundle. It is the lightest way to react to your sales without checking ShipStation by hand.

How it fires
instant, ShipStation calls Make through a webhook as soon as the order event happens.
When to use it
to route fresh orders to a packer or to copy them into a reporting sheet while they are still hot.
Watch out
an edited order fires it too, so a module that changes the same order can start the scenario again.
ShipStation2Listen for Order Events (with Item Info)

Listen for Order Events (with Item Info)

Instant trigger

In Make“Receives notifications about new and updated orders (including detailed information about individual items that are part of the order).”

Same moment as the plain order trigger, but the bundle also carries the detail of every item inside the order. Pick it when the products matter more than the order header.

How it fires
instant, ShipStation calls Make through a webhook as soon as an order is created or updated.
When to use it
a scenario that reacts to what was bought, such as alerting the person who handles fragile goods or feeding a stock sheet line by line.
Watch out
since an order can hold several items, plan how later modules should treat each one before you map anything.
ShipStation3Listen for Shipment Events

Listen for Shipment Events

Instant trigger

In Make“Receives notifications about new shipments. The triggering event for ship notifications is the generation of a shipping label. Marking an order as shipped WILL NOT trigger this webhook.”

Wakes your scenario up the moment a shipping label is generated in ShipStation, with the new shipment in the bundle. That is the exact point where a parcel becomes real for your customer.

How it fires
instant, ShipStation calls Make through a webhook as soon as the label exists.
When to use it
to warn support, update a sales tool or post in a team channel once an order is ready to leave.
Watch out
marking an order as shipped, by hand or with Mark an Order as Shipped, does not start this trigger. Only a label generated in ShipStation does.
ShipStation4Listen for Shipment Events (with Item Info)

Listen for Shipment Events (with Item Info)

Instant trigger

In Make“Receives notifications about new shipments, including detailed information about individual items that are part of the shipment. The triggering event for ship notifications is the generation of a shipping label. Marking an order as shipped WILL NOT trigger this webhook.”

The detailed version of the shipment trigger: when a label is generated, Make receives the shipment plus the items it contains. Useful when you care about what left the warehouse, not only that something left.

How it fires
instant, ShipStation calls Make through a webhook as soon as the label is created.
When to use it
to track which products actually shipped, for a stock count or a supplier follow-up.
Watch out
orders marked as shipped without a label never reach this trigger, so a partial picture is possible if your team mixes both habits.
Modules

What can each ShipStation module do in Make?

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

ShipStation1

Add Funds

Action

In Make“Adds funds to a carrier account using the payment information on file.”

Tops up one of your carrier accounts using the payment method already on file in ShipStation, so nobody has to log in to recharge before printing labels.

When to use it
when refilling a carrier balance should be a step of a scenario rather than a chore someone remembers.
Watch out
it spends real money, and Run once executes it for real, so test it on purpose.
ShipStation2

Add Tag to Order

Action

In Make“Adds a tag to an order.”

Sticks a tag on an order, which gives your warehouse a label it can filter on inside ShipStation without editing the order itself.

When to use it
right after an order trigger, to mark rush orders, wholesale buyers or anything that needs a second look.
Watch out
pick the tag from List Tags, which returns every tag your account defines, instead of typing it from memory.
ShipStation3

Assign User to Order

Action

In Make“Assigns a user to an order.”

Puts a named ShipStation user in charge of an order, so each packer opens the app and sees their own pile instead of the full queue.

When to use it
after Listen for Order Events, with a filter deciding who takes which order.
Watch out
pick the user from List Users first, so the scenario hands the order to someone the account actually knows.
ShipStation4

Create Order

Action

In Make“Creates a new order.”

Adds a brand new order to ShipStation from data held somewhere else, so orders taken by phone, email or a form join the same shipping queue as your store orders.

When to use it
as the action of a scenario whose trigger sits in the tool where those orders are first written.
Watch out
run a single test with Run once before switching on, or a mapping error creates many wrong orders.
ShipStation5

Create Warehouse

Action

In Make“Creates a new warehouse (Ship From Location).”

Registers a new warehouse, which ShipStation calls a Ship From Location, so a new address can appear on your labels without anyone opening the settings.

When to use it
when opening a pickup point or a partner warehouse is itself recorded in another tool you already automate.
Watch out
check List Warehouses first to avoid creating a second copy of an address you already have.
ShipStation6

Deactivate Store

Action

In Make“Deactivates the specified store.”

Switches off one of the stores connected to your ShipStation account; Reactivate Store is the module that turns it back on.

When to use it
when a sales channel is paused, for instance a seasonal shop, and that decision lives in another tool.
Watch out
an inactive store can no longer be changed through Update Store until you reactivate it.
ShipStation7

Delete Order

Action

In Make“Removes a selected order from ShipStation's UI. This is a "soft" delete action so the order will still exist in the database, but will be set to "inactive".”

Hides an order from the ShipStation screens. Behind the scenes the order stays in the database with an inactive status, which makes this a soft delete rather than a true removal.

When to use it
to clear test orders or duplicates created by another scenario.
Watch out
since the record still exists, do not count on this module to erase customer data for good.
ShipStation8

Get Carrier

Action

In Make“Gets a selected carrier's details.”

Returns the details of one carrier linked to your account, as a single bundle that the next modules can read.

When to use it
when a scenario already knows which carrier it deals with and needs its details before choosing a service or adding funds.
Watch out
if you do not know the carrier yet, start with List Carriers, which returns them all.
ShipStation9

Get Customer

Action

In Make“Gets a selected customer's details.”

Fetches the record of one customer, so a later module works with the buyer's full record rather than what the order alone carries.

When to use it
after an order trigger, when you need more about the buyer than the order itself shows.
Watch out
it reads one customer you already point to; to browse or match customers, List Customers is the better starting point.
ShipStation10

Get Order

Action

In Make“Retrieves a single order from the database.”

Pulls one order, fresh from ShipStation, as one bundle. Handy when a scenario holds an order reference and wants the current state rather than an old copy.

When to use it
before Update Order, so you start from the full record and change only what you mean to change.
Watch out
one order per run; to find orders by criteria, use List Orders.
ShipStation11

Get Product

Action

In Make“Gets a selected product's details.”

Reads the full record of one product in your ShipStation catalog and passes it on as a single bundle.

When to use it
as the step right before Update Product, since that module expects the whole product and not just the field you want to change.
Watch out
without a product reference in hand, List Products is where you begin.
ShipStation12

Get Store

Action

In Make“Gets a selected store's details.”

Looks up one connected store and returns its details, so a scenario knows which sales channel it is working with.

When to use it
before Update Store, or to check a store's state before refreshing or reactivating it.
Watch out
the store must be one of those installed on the account; List Stores shows them.
ShipStation13

Get Warehouse

Action

In Make“Returns details for a selected warehouse (Ship From Location).”

Gives you the details of one warehouse, the Ship From Location printed on your labels, in a single bundle.

When to use it
as the read step before Update Warehouse, so the full record is ready to send back.
Watch out
it targets a warehouse you already know; List Warehouses covers the rest.
ShipStation14

Mark an Order as Shipped

Action

In Make“Marks an order as shipped without creating a label in ShipStation.”

Closes the loop for parcels that left without a ShipStation label, for example a local drop-off or a courier booked elsewhere: the order shows as shipped and no label is created.

When to use it
when the shipping proof arrives from another tool and ShipStation should reflect it.
Watch out
these orders never start the shipment triggers and appear in List Fulfillments, not in List Shipments.
ShipStation15

Reactivate Store

Action

In Make“Reactivates the specified store.”

Turns a store you had deactivated back on, which is the counterpart of Deactivate Store.

When to use it
when a paused sales channel reopens and that event is logged in another tool your scenario watches.
Watch out
reactivate before any Update Store step, because an inactive store refuses any change.
ShipStation16

Refresh Store

Action

In Make“Initiates a store refresh.”

Asks ShipStation to refresh one connected store, so its latest data is pulled in without anyone opening the app.

When to use it
when an event outside ShipStation, such as a batch of orders pushed to your shop, means it is worth pulling the latest data now.
Watch out
the module only starts the refresh, so place any order search in a separate run rather than right after it.
ShipStation17

Remove Tag From Order

Action

In Make“Removes a tag from the specified order.”

Takes a tag off an order, so filters in ShipStation stop showing it once the situation is solved.

When to use it
paired with Add Tag to Order, to lift an on-hold or needs-review tag when the missing information arrives.
Watch out
it removes one tag from one order, so map both the order and the exact tag you want gone.
ShipStation18

Unassign User from Order

Action

In Make“Unassigns a user from an order.”

Frees an order from the user it was assigned to, which sends it back to the shared queue.

When to use it
when a packer is away or when a routing rule changes, so orders can be reassigned with Assign User to Order.
Watch out
combine it with a filter so it only runs on orders that actually have an owner.
ShipStation19

Update Order

Action

In Make“Updates an existing order. Only orders in an open status in ShipStation (awaiting_payment, awaiting_shipment, and on_hold) can be updated through this method. This call DOES NOT currently support partial updates. The entire resource must be provided in the body of the request.”

Changes an existing order that is still open in ShipStation, awaiting payment, awaiting shipment or on hold.

When to use it
when a correction, such as a new address from support, must reach the order before it ships.
Watch out
there is no partial update. The complete order must be sent, so read it with Get Order first and map every value back.
ShipStation20

Update Product

Action

In Make“Updates an existing product. This call DOES NOT currently support partial updates. The entire resource must be provided in the body of the request.”

Rewrites a product in your ShipStation catalog with the values your scenario provides.

When to use it
when product data is maintained in another tool, a sheet or a catalog app, and ShipStation should follow it.
Watch out
the whole product must be sent, not only the changed field; run Get Product before it and map every value back.
ShipStation21

Update Store

Action

In Make“Updates an existing, active store. Inactive stores cannot be modified via the API. This call DOES NOT currently support partial updates. The entire resource must be provided in the body of the request.”

Edits the settings of an active store connected to ShipStation, based on data your scenario carries.

When to use it
when store details are managed centrally and must be pushed to ShipStation after each change.
Watch out
inactive stores are refused, and the call replaces the full record, so start from Get Store and send everything.
ShipStation22

Update Warehouse

Action

In Make“Updates an existing warehouse (Ship From Location). This call DOES NOT currently support partial updates. The entire resource must be provided in the body of the request.”

Updates a Ship From Location, the warehouse address used on your labels.

When to use it
when a site moves or its contact changes and the source of truth is another system.
Watch out
this call also expects the complete warehouse record. Read it with Get Warehouse, change what you need in the mapping, then send the whole thing.
ShipStation23

Void Label

Action

In Make“Voids the specified label by shipmentId.”

Cancels a shipping label, identified by its shipment, so a parcel that will not leave does not keep a live label.

When to use it
when an order is cancelled after its label was printed and the cancellation is recorded in another tool.
Watch out
it needs the shipment reference, not the order; List Shipments helps you find it.
ShipStation24

List Carriers

Search

In Make“Lists all carriers”

Returns every carrier set up in your account, one bundle each, which is the easy way to see what you can ship with.

When to use it
at the start of a scenario that then reads services or packages for each carrier.
Watch out
each carrier is a separate bundle, so the modules after it run once per carrier and count operations each time.
ShipStation25

List Customers

Search

In Make“Lists all customers.”

Brings back your ShipStation customers as a series of bundles, ready to copy into a CRM or a mailing tool.

When to use it
to fill or check a customer list elsewhere, or to find the right record before Get Customer.
Watch out
a large customer base means many bundles, and every module after this one counts an operation per customer.
ShipStation26

List Fulfillments

Search

In Make“Obtains a list of fulfillments that match the specified criteria. Orders that have been marked as shipped either through the UI or the API will appear in the response as they are considered fulfillments.”

Finds the orders that were marked as shipped, from the ShipStation screens or through the API, which ShipStation treats as fulfillments.

When to use it
to report on parcels that left without a ShipStation label, the ones List Shipments leaves out.
Watch out
it can return zero, one or many bundles, so set your criteria tightly.
ShipStation27

List Marketplaces

Search

In Make“Lists the marketplaces that can be integrated with ShipStation.”

Shows which marketplaces ShipStation can connect to, one bundle per marketplace.

When to use it
when you are mapping a new sales channel and want to check from Make that ShipStation supports it before going further.
Watch out
this is the list of what can be integrated, not the list of your own stores; that is List Stores.
ShipStation28

List Orders

Search

In Make“Lists all orders for the specified criteria.”

Searches your orders with the criteria you set and returns each match as its own bundle.

When to use it
for a scheduled scenario that reviews open orders, or to find an order when you only know part of it.
Watch out
without a filter the result can be huge; each bundle then costs operations in every following module.
ShipStation29

List Packages

Search

In Make“Retrieves a list of packages for the specified carrier.”

Retrieves the package types offered by one carrier, so a scenario can pick a valid box instead of guessing.

When to use it
together with List Services, when you prepare shipping options for a given carrier.
Watch out
it works carrier by carrier, so you need the carrier first, from List Carriers or Get Carrier.
ShipStation30

List Products

Search

In Make“Lists all products.”

Walks through your ShipStation catalog and emits one bundle per product.

When to use it
to compare the catalog with another source, or to locate the product you want to change with Update Product.
Watch out
a big catalog produces many bundles; add a filter right after it so only relevant products go further.
ShipStation31

List Services

Search

In Make“Retrieves the list of available shipping services provided by the specified carrier.”

Lists the shipping services a given carrier provides, one bundle per service, so a scenario can choose among real options.

When to use it
when a scenario must choose the service to set on an order, or when you build a shipping options sheet.
Watch out
like List Packages, it expects a carrier, so place a carrier module before it.
ShipStation32

List Shipments

Search

In Make“Retrieves a list of shipments that match the specified criteria. Only valid shipments with labels generated in ShipStation will be returned in the response. Orders that have been marked as shipped either through the UI or the API will not appear as they are considered external shipments.”

Returns shipments that match your criteria, but only valid ones whose label was generated in ShipStation.

When to use it
to find the shipment behind a label before Void Label, or to report on what left with a ShipStation label.
Watch out
orders marked as shipped count as external and stay out of the result; look for them in List Fulfillments.
ShipStation33

List Stores

Search

In Make“Retrieves the list of installed stores on the account.”

Shows the stores installed on your ShipStation account, one bundle each.

When to use it
to loop over your sales channels and refresh, check or update each one in the following modules.
Watch out
each store is a separate bundle, and an inactive one cannot be edited with Update Store until Reactivate Store brings it back.
ShipStation34

List Tags

Search

In Make“Lists all tags defined for this account.”

Returns all the tags defined in your account, the same ones you see on orders in ShipStation.

When to use it
while building a scenario with Add Tag to Order or Remove Tag From Order, to pick the exact tag rather than typing it.
Watch out
it lists the tags available, not the orders that carry them; List Orders answers that.
ShipStation35

List Users

Search

In Make“Lists all users related to a connected account.”

Gives you the users of the connected ShipStation account, handy to know who can take an order.

When to use it
before Assign User to Order, so the scenario hands work to someone who really exists in the account.
Watch out
each user is a bundle; if you only need one, filter the list right after this module.
ShipStation36

List Warehouses

Search

In Make“Lists all warehouses (Ship From Locations).”

Lists every Ship From Location in your account, so a scenario can see all the addresses your labels can leave from.

When to use it
before Create Warehouse, to check an address is not already there, or to pick a warehouse for Get Warehouse.
Watch out
the result may hold several bundles, so the next modules run once per warehouse.
Need help

Need help automating ShipStation with Make?

A person reads every message.

FAQ

ShipStation and Make: frequent questions

01Is the ShipStation Make integration free?
Yes, ShipStation is a standard app in Make, so you can use it from the Free plan. That plan has limits: 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. Make counts each module run on each bundle as one operation against your monthly credits. Paid plans such as Core, Pro, Teams and Enterprise lift the interval to 1 minute and the number of active scenarios. Your ShipStation subscription is separate and is not covered here.
02What do you need to connect ShipStation to Make?
A ShipStation account and a Make account are enough to begin. Make's documentation for this app lists no specific prerequisite, so the generic connection flow applies. Add any ShipStation module, click Create a connection, optionally give it a name, then either approve access on the ShipStation page or paste the key ShipStation provides, and click Save. After that, the same connection serves all 40 ShipStation modules, so you only do this once per account.
03Do ShipStation triggers in Make fire in real time?
Yes. All four ShipStation triggers are instant: ShipStation calls Make through a webhook as soon as the event happens, instead of Make checking on a schedule. Two of them react to orders, created or updated, and two react to shipments. The shipment triggers fire when a label is generated in ShipStation. Marking an order as shipped, by hand or with the Mark an Order as Shipped module, does not fire them, so parcels sent without a label will not start those scenarios.
04What if a ShipStation module is missing in Make?
It depends on what you need. ShipStation has no Make an API Call module in Make, so you cannot do anything beyond the 40 modules listed on this page. Make's documentation for the app is also marked as limited. Before giving up, check whether a List module plus a filter can answer the need, since searches return every matching item. If the gap remains, another tool in your stack may hold the data, or the Hack'celeration team can study the case with you through the help form below.
05Make or n8n for ShipStation?
It depends on your criteria rather than on a winner. On the Make side, the facts are here: 40 ShipStation modules, four instant triggers, 23 actions and 13 searches, usable from the Free plan with no code. Many apps also have an n8n node, so check whether one exists for ShipStation and which operations it covers. Then compare the two on what you actually need to automate, the tool your team already knows and how you want to maintain scenarios over time.
Same platform

Other docs you might need on this stack.

Browse all integrations