Resources · Make integration

Easyship Make integrationAutomate Easyship with Make.

Can Make react the moment a label prints or a parcel moves? The Easyship Make integration gives you 10 modules: 5 instant triggers and 5 actions. This guide shows how to link your account, build a first scenario and pick the right module for each shipping task.

Try the Easyship integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Easyship Make integration do for you?

The Easyship Make integration lets your shipping account talk to your other tools without a line of code. You build a scenario, the automation you assemble in Make as a chain of modules, and Easyship either starts it through a webhook or receives the shipments your scenario creates, reads, updates or deletes.

Orders turned into shipments. A store that logs orders in a spreadsheet can send each new row to Create a Shipment. Easyship registers the parcel and returns shipping quotes, so nobody retypes addresses by hand.

Customers told when something goes wrong. Watch Shipment Cancelled fires as soon as a shipment is cancelled, which is the right moment to warn support or reopen the order in your CRM. Watch Shipment Checkpoint Created covers the happier path: each new tracking checkpoint can feed a status column or a customer message.

Label paperwork filed for you. When Watch Shipping Label Created fires, the bundle (one item passed from module to module) carries the documents and tracking details of the label, ready to be stored or shared.

Know the edges before you start. The get, update and delete actions work on one shipment by its ID, and the Make doc for Easyship warns that it was generated with AI from the vendor documentation, so confirm critical details with Easyship. For anything outside the listed modules, Make an API Call reaches the rest of the API. Not sure which platform fits your team? The n8n vs Make comparison lays out the criteria, the Make pricing guide explains plans, and Make training walks you through your first builds.

Connect

How do you connect Easyship to Make?

  1. 01

    Generate an API token in Easyship

    You need an active Easyship account. In its dashboard, click Connect, then New Integration, pick API Integration, give it a name and click Connect. Easyship shows an API token on screen: copy it now.

  2. 02

    Add an Easyship module in Make

    Open your scenario, add any Easyship module and click Create a connection. A connection is your Easyship account linked to Make once, then reused by every Easyship module. The Connection name field is optional but helps when you run several accounts.

  3. 03

    Paste the token and save

    Paste the token you copied from Easyship, or follow the instructions Make displays, and confirm. From then on, every other Easyship module in any scenario can pick this same connection from its dropdown.

First scenario

Build your first scenario with Easyship

GoalWhen a new order lands in another app, Make creates the matching shipment in Easyship and pulls its current details back.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the big +. Pick the app where your orders arrive, such as a spreadsheet or your store, as the first module.

  2. 02

    Add Create a Shipment

    Click the + to the right of that first module, search Easyship and choose Create a Shipment. Select your Easyship connection, then map the order data from the first module into the shipment.

  3. 03

    Read the shipment back

    Add Get a Shipment after it and map the shipment ID returned by the previous module. You now hold the current details of the parcel, ready for a later step such as a message or a status column.

  4. 04

    Test with Run once

    Click Run once with a real test order waiting. Open the bubble above each module to read the bundles it received and check that the shipment appears in your Easyship account.

  5. 05

    Schedule and switch it on

    Click the clock on the first module. A new scenario checks every 15 minutes by default, which is also the shortest gap on the Free plan. Save, then flip the scenario switch on.

Triggers

What starts an Easyship scenario?

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

Easyship1Watch Shipment Cancelled

Watch Shipment Cancelled

Instant trigger

In Make“Triggers when a shipment is cancelled.”

This trigger starts your scenario whenever a shipment is cancelled in Easyship, so the rest of your stack learns about it without anyone forwarding an email. Each cancellation arrives as one bundle you can map into later modules.

How it fires
instant, Easyship calls Make through a webhook as soon as the cancellation happens.
When to use it
a buyer changes their mind and you want support alerted and the order reopened in your CRM or store.
Watch out
the trigger only listens once its webhook exists, so click Create a webhook before Create a connection when you add it.
Easyship2Watch Shipment Checkpoint Created

Watch Shipment Checkpoint Created

Instant trigger

In Make“Triggers when shipment's checkpoints increased.”

Here you get a signal every time a shipment gains a new tracking checkpoint. Each new checkpoint on a parcel becomes its own run, with the shipment data in the bundle.

How it fires
instant, Easyship notifies Make by webhook the moment the checkpoint count goes up.
When to use it
you keep a live tracking column in a spreadsheet or push progress updates to customers who asked to follow their parcel.
Watch out
a parcel can collect several checkpoints on its journey, and each one runs the scenario and spends operations, the unit Make counts on your plan. If only stage changes matter, Watch Shipment Tracking Status Changed is the calmer choice.
Easyship3Watch Shipment Events

Watch Shipment Events

Instant trigger

In Make“Triggers when one of the selected events occurs.”

One trigger, several possible events: you choose which shipment events should wake the scenario, and Make starts as soon as any of them occurs. That keeps related cases in a single scenario instead of three separate ones.

How it fires
instant, Easyship sends each selected event to Make through a webhook right when it happens.
When to use it
a shared logistics log where several kinds of shipment events should land in the same table.
Watch out
mixed events reach the same next module, so read the event type in the bundle before you map a step that only makes sense for one kind of event.
Easyship4Watch Shipment Tracking Status Changed

Watch Shipment Tracking Status Changed

Instant trigger

In Make“Triggers when a shipment status has changed, as defined by user.”

Your scenario starts each time the tracking status of a shipment changes, which is less noisy than following every checkpoint. It suits teams who think in stages rather than in individual scans.

How it fires
instant, Easyship alerts Make by webhook as soon as the status moves.
When to use it
an ops manager wants a Slack or email alert when a parcel changes stage, without a message for every scan in between.
Watch out
the official description says the change is defined by the user, so review the module settings before your first test to confirm which status changes will actually reach Make.
Easyship5Watch Shipping Label Created

Watch Shipping Label Created

Instant trigger

In Make“Triggers when a new shipping label is generated. Provides documentation and tracking information.”

As soon as Easyship generates a new shipping label, Make receives it together with the label documents and the tracking information. You get the paperwork and the tracking link in one bundle, ready to file or share.

How it fires
instant, Easyship pushes the new label to Make through a webhook the moment it exists.
When to use it
a warehouse that wants every label saved to a shared drive and the tracking link sent to the buyer.
Watch out
this reacts to labels only; a shipment created without a label yet will not start the scenario, so pair it with another trigger if you need both moments.
Modules

What can Make do in Easyship?

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

Easyship1

Create a Shipment

Action

In Make“Creates a shipment and receive accurate shipping quotes.”

Registers a new shipment in Easyship from data coming out of your scenario and hands you back accurate shipping quotes, so you can compare options without logging in.

When to use it
an order confirmed in your store or a row added to a sheet should become a parcel ready to ship.
Watch out
run a single test order with Run once before activating, because every live order will create a real shipment.
Easyship2

Delete a Shipment

Action

In Make“Deletes shipment by ID.”

Removes one shipment from Easyship using its ID, which keeps your dashboard clean when an order dies upstream.

When to use it
an order is refunded or cancelled in your store before anything was sent, and the shipment no longer has a reason to exist.
Watch out
a deletion cannot be undone from Make, so feed it only the IDs you mean to remove and test it on a dummy shipment first.
Easyship3

Get a Shipment

Action

In Make“Returns a shipment by ID with current details.”

Fetches one shipment by its ID with its current details, giving later modules fresh data instead of whatever was true when the scenario began.

When to use it
right after a trigger or a Create a Shipment step, when you need the full record to write a customer message or update a report.
Watch out
it needs an ID; it does not search, so map the ID from an earlier module rather than typing one.
Easyship4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the rest of the Easyship API to your scenario while reusing the connection you already created, so you are never stuck with only the listed modules.

When to use it
you need an Easyship feature that none of the other nine modules covers.
Watch out
you write the request yourself from the Easyship API documentation, so test the call with Run once and read the returned bundle carefully before mapping it further.
Easyship5

Update a Shipment

Action

In Make“Updates shipment by ID.”

Changes an existing shipment identified by its ID, so a correction made elsewhere reaches Easyship without anyone editing the parcel by hand.

When to use it
a customer fixes their delivery address in your helpdesk and the shipment has to follow before the label is printed.
Watch out
map the ID from a trigger or from Get a Shipment; a wrong ID edits the wrong parcel.
Need help

Need help automating Easyship with Make?

A person reads every message.

FAQ

Easyship and Make: common questions

01Is the Easyship Make integration free?
Yes, on the Make side. Easyship is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lift the scenario cap and go down to 1 minute between runs. You still need your own active Easyship account, which Easyship bills separately under its own pricing.
02What does it take to connect Easyship to Make?
An active Easyship account and an API access token. In Easyship, click Connect, then New Integration, choose API Integration, name it and click Connect to display the token. In Make, add an Easyship module, click Create a connection and paste the token. With an instant trigger, Make first asks you to click Create a webhook, then Create a connection. The same connection then serves every Easyship module in your scenarios.
03Do Easyship triggers in Make run in real time?
Yes. All 5 Easyship triggers are instant: Easyship calls Make through a webhook as soon as the event happens, whether that is a cancellation, a new checkpoint, a status change, a new label or one of the events you selected. You do not wait for a polling interval. Each event still counts as an operation on your plan, so a trigger that fires often, like checkpoints, uses more of your monthly credits than one that fires rarely.
04What if an Easyship module is missing in Make?
Use Make an API Call. It calls any endpoint of the Easyship API from your scenario with the connection you already set up, so the 5 actions and 5 triggers are not a ceiling. You build the request from the Easyship API docs and test it with Run once. Keep in mind that the Make doc for Easyship states it was AI-generated from vendor documentation, so confirm important behavior directly with Easyship.
05Make or n8n for Easyship: which one fits?
It depends on the tool your team already runs. In Make, Easyship comes with 10 modules, instant triggers for cancellations, checkpoints, status changes and labels, plus Make an API Call for the rest, all in a visual editor. The same app often has an n8n node too, so check what that node covers before you choose. The n8n vs Make comparison, linked above, lists the criteria side by side without ranking one platform over the other.
Same platform

Other docs you might need on this stack.

Browse all integrations