Resources · Make integration

Shippo Make integrationAutomate Shippo with Make.

Can Make handle your Shippo orders, shipments and labels for you? The Shippo Make integration gives you 13 modules: 3 triggers, 7 actions and 3 searches. This page shows you how to link your account, build a first scenario and pick the right module.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Shippo Make integration do for you?

The Shippo Make integration links your Shippo account to Make so that orders, shipments and shipping labels can move between Shippo and your other tools without code. You build a scenario, which is the automation itself: a chain of modules, each one a single step such as watching labels or creating an order.

Orders that land in Shippo on their own. An online store receives a sale in another app, and Create an Order sends it to Shippo, so nobody retypes the address or the items.

A shipping log your team can read. Watch Shipping Labels picks up every label created or updated, and the next module writes it to a sheet or a chat channel that support checks when a customer asks where a parcel is.

Answers pulled on demand. Search Shipments and List Orders return several records at once, which suits a report or a cleanup pass across your data.

What the page cannot promise: the three triggers are scheduled, so Make checks Shippo on the scenario's schedule instead of hearing about changes the moment they happen. When a Shippo feature has no module, Make an API Call reaches the rest of the API with the same connection. If you also look at n8n, the n8n vs Make comparison lays out the differences, Make pricing explains plans and operations, and Make training helps if you are starting from zero.

Connect

How do you connect Shippo to Make?

  1. 01

    Create an API key in Shippo

    In your Shippo account portal, open the API Configuration section and click Developer keys. Choose Create new test key while you experiment, or Create new live key for real shipments, then copy the key shown on screen.

  2. 02

    Add a Shippo module and open the connection

    In Make, add any Shippo module to your scenario and click Create a connection. A connection is your Shippo account linked to Make once, then reused by every Shippo module you add later.

  3. 03

    Paste the key and save

    Give it a clear label in Connection name if you like, for example one name for the test key and another for the live one. Paste the API key you copied from Shippo and confirm. Make can now read and write your Shippo data.

First scenario

Your first scenario: send new orders to Shippo

GoalWhen a sale is recorded in your store or form tool, Make creates the matching order in Shippo.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. This first module comes from the app where your sales are recorded.

  2. 02

    Set up the starting module

    Search that app by name, pick the module that returns new sales, and link your account with Create a connection. Fill its fields; Make lists what it can read once the connection exists.

  3. 03

    Add Create an Order

    Click the + on the right of the first module, search for Shippo and pick Create an Order. Use the Shippo connection you made, then map the customer and item data coming from the previous module.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Open each module's bubble to read the bundles it received, a bundle being one item passed along, here one sale. Then check that the order shows up in Shippo.

  5. 05

    Schedule and switch it on

    Open the clock on the first module to set the schedule, every 15 minutes by default for a new scenario. Switch the scenario on, and new sales now reach Shippo without anyone copying them.

Triggers

Shippo triggers in Make

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

Shippo1Watch Parcels

Watch Parcels

Scheduled trigger

In MakeTriggers if a parcel has been created or updated.

Watch Parcels starts your scenario whenever a parcel is created or updated in Shippo, so the package itself, not the order around it, becomes your starting point. Each parcel it finds travels on as its own bundle.

How it fires
it is a scheduled trigger, so Make checks Shippo on the scenario's schedule and picks up the changes found since the last check.
When to use it
pick it when a packing station edits parcel details and another tool has to reflect that change.
Watch out
updates count too, so a parcel edited several times can start several runs; add a filter if you only care about new ones.
Shippo2Watch Shipments

Watch Shipments

Scheduled trigger

In MakeTriggers if a shipment has been created or updated.

With Watch Shipments, every shipment created or updated in Shippo becomes the start of a run, which lets you follow deliveries without opening the dashboard. You get one bundle per shipment.

How it fires
scheduled; Make asks Shippo for changes each time the scenario's schedule comes around, it does not hear about them instantly.
When to use it
choose it when customer support or a CRM needs to know that a shipment exists or has changed.
Watch out
a shipment and its label are separate objects in Shippo, so if your step depends on the label, Watch Shipping Labels is the better entry point.
Shippo3Watch Shipping Labels

Watch Shipping Labels

Scheduled trigger

In MakeTriggers if a shipping label has been created or updated.

Watch Shipping Labels hands your scenario each label created or updated in Shippo, which is the moment a package is truly ready to leave. It suits every flow that begins once a label exists.

How it fires
this trigger is scheduled: Make polls Shippo on the scenario's schedule, so a label appears in the scenario at the next check.
When to use it
use it to log labels in a sheet, alert the warehouse in a chat channel or notify the customer through your email tool.
Watch out
updated labels fire the scenario as well, so a filter on the data you care about keeps you from sending the same message twice.
Modules

Shippo modules in Make

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

Shippo1

Create an Order

Action

In MakeCreates an order.

Create an Order adds an order to Shippo from data sent by another module, so sales recorded elsewhere reach your shipping tool without retyping.

When to use it
right after the module that brings in a sale from your store, form or spreadsheet.
Watch out
it creates a new order on every run, so a trigger that also fires on updates can produce duplicates unless you filter first.
Shippo2

Create a Shipment

Action

In MakeCreates a new shipment.

This action opens a new shipment in Shippo, the object that describes what travels and where, built from the data your scenario already holds.

When to use it
when your flow starts from a delivery request instead of an order, for example a replacement part sent to a customer.
Watch out
a shipment is not a label; to get something printable you still need Create Label by Rate further down the chain.
Shippo3

Create Label by Rate

Action

In MakeCreates a shipping label based on a rate object.

Create Label by Rate turns a chosen rate into a shipping label, the step that makes a package ready to hand over to the carrier.

When to use it
once your scenario has a rate object from Shippo and the decision about which service to use is settled.
Watch out
the module works from a rate object, so it needs that rate to exist before it runs; place it after the modules that give you one.
Shippo4

Get an Order

Action

In MakeRetrieves a single order.

Get an Order fetches one specific order from Shippo with its full content, handy when an earlier module only told you which order changed.

When to use it
in the middle of a scenario, to read the details of an order before writing them to a CRM or an invoice tool.
Watch out
it returns a single order, so you have to tell it which one; to browse several, List Orders is the right module.
Shippo5

Get a Shipment

Action

In MakeRetrieves a single shipment.

To read one shipment in detail, Get a Shipment pulls it from Shippo and makes every piece of its data available to the modules that follow.

When to use it
after a module that tells you which shipment is concerned, when a later step needs information stored on the shipment itself.
Watch out
it targets exactly one shipment; if you do not know which, start with Search Shipments and let it return candidates.
Shippo6

Get a Shipping Label

Action

In MakeRetrieves a single shipping label.

Get a Shipping Label retrieves a single label from Shippo, which lets you resend or archive it without logging in to the dashboard.

When to use it
when a support request mentions a package and your agent needs the label data in the helpdesk ticket.
Watch out
one run returns one label; for a batch of them, Search Shipping Labels returns several bundles instead.
Shippo7

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Make an API Call is the fallback that reaches any endpoint of the Shippo API while reusing the connection you already created, so you are never stuck when a module is missing.

When to use it
when the Shippo feature you need has no dedicated module on this page.
Watch out
here you write the request yourself, so keep the Shippo API reference open and test with Run once before switching the scenario on.
Shippo8

List Orders

Search

In MakeRetrieves all orders.

List Orders brings back the orders stored in Shippo, each one as its own bundle, which gives you a full picture to sort, count or export.

When to use it
for a report in a spreadsheet or a check that every sale made it into Shippo.
Watch out
as a search, it can return zero, one or many orders, and each module after it runs once per order, which adds operations to your plan.
Shippo9

Search Shipments

Search

In MakeRetrieves all shipment objects.

Search Shipments returns the shipment objects from your Shippo account, so the next modules can work through them one at a time.

When to use it
when you need to find a shipment before acting on it, or to copy shipment data into a sheet for the operations team.
Watch out
if nothing matches, the modules after it simply do not run; add a check so an empty result does not go unnoticed.
Shippo10

Search Shipping Labels

Search

In MakeRetrieves all shipping labels.

Pulling every label at once is the job of Search Shipping Labels, which hands each one to the rest of the scenario as a separate bundle.

When to use it
for a warehouse recap, an audit of labels already created or a backfill into a tool you just adopted.
Watch out
a long list means many operations downstream, so add a filter right after the search to keep only the labels you need.
Need help

Need help automating Shippo with Make?

A person reads every message.

FAQ

Shippo and Make: frequent questions

01Is the Shippo Make integration free?
Yes, Shippo is a standard app in Make, 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 (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one operation being one module running on one bundle. Your Shippo subscription is separate and handled on the Shippo side.
02What do you need to connect Shippo to Make?
You need an active Shippo account and an API key. In the Shippo account portal, go to API Configuration, click Developer keys, then create a live key or a test key depending on your needs and copy it. In Make, add a Shippo module, click Create a connection, optionally name the connection, paste the key and confirm. That connection is then reused by every Shippo module in your scenarios, so you only do this once per key.
03Do the Shippo triggers in Make react in real time?
No. All three Shippo triggers, Watch Parcels, Watch Shipments and Watch Shipping Labels, are scheduled. Make checks Shippo on the schedule set on the first module, every 15 minutes by default for a new scenario. On the Free plan, 15 minutes is also the shortest interval between two scheduled runs; paid plans go down to 1 minute. Shippo has no instant trigger in Make, so a change is picked up at the next check rather than the second it happens.
04What if a Shippo module is missing in Make?
Use Make an API Call. The Shippo app in Make includes this module, and it can call any endpoint of the Shippo API with the same connection as the other modules. That covers features the 13 listed modules leave out. Keep in mind that you build the request yourself, so test it with Run once. Also note that the Make documentation for Shippo is marked as AI-generated from the official Shippo docs, and Make advises verifying important details with Shippo directly.
05Should you use Make or n8n for Shippo?
It depends on the modules you need and the tool you already run. In Make, Shippo comes with 13 modules, including 3 scheduled triggers and a Make an API Call module for anything else. n8n often offers a node for the same app, so the practical test is to compare the actions each side lists against your own workflow. If your other scenarios already live in Make, keeping Shippo there avoids splitting your automations across two tools.