Resources · Make integration

AfterShip Make integrationAutomate AfterShip with Make.

Your shipments can land in AfterShip without anyone typing a tracking number. The AfterShip Make integration gives you 9 modules: 8 actions and 1 search. This page shows how to link your account and build a first scenario that creates trackings on its own.

Try the AfterShip integration on MakeSee the 9 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the AfterShip Make integration do for you?

The AfterShip Make integration lets a Make scenario, the automation you build in Make, create, read, update and delete trackings in your AfterShip account, and manage who gets notified about them. Each step of that scenario is a module, and you connect your account once with an API key.

Trackings that create themselves. When another app records a shipment, Create a Tracking opens the matching tracking in AfterShip, and Add a Notification attaches the people who should hear about it. Support stops copying numbers by hand.

A clean tracking list. A cancelled order in your shop can call Update a Tracking or Delete a Tracking, so AfterShip only holds parcels that still matter.

Answers for the help desk. Search Trackings or Get a Tracking pulls the current record into a ticket or a sheet, so an agent can reply without opening AfterShip.

One limit to know up front: AfterShip has no trigger in Make, so it cannot start a scenario by itself. The scenario starts on its schedule or on another app, and AfterShip modules come after. The official Make doc for this app also warns that it is AI-generated and should be checked against AfterShip's own documentation.

The same app often has a node in n8n too; the n8n vs Make comparison lays out the criteria. New to the editor? The Make training walks through it, and Make pricing explains what counts on your plan.

Connect

How do you connect AfterShip to Make?

  1. 01

    Create an API key in AfterShip

    In AfterShip, open the API keys settings page from the main dashboard and click Create API key. Give it a name you will recognize, pick the signature header, set admin API permissions, click Save, then copy the key shown on screen.

  2. 02

    Add an AfterShip module in Make

    In your scenario, search for AfterShip, pick any of its modules and click Create a connection. The Connection name field is optional, but a clear name helps when you run several AfterShip accounts.

  3. 03

    Paste the key and save

    Paste the API key you copied from AfterShip and confirm. That connection, your AfterShip account linked to Make, is now reused by every AfterShip module you add, so you only do this once.

First scenario

Build your first scenario with AfterShip

GoalWhen an order ships in another app, Make creates its tracking in AfterShip and adds the people to notify.

  1. 01

    Start from the app that knows the shipment

    On the Scenarios page, create a new scenario and click the + to add the first module. Pick the app where shipments are recorded, such as your shop or a spreadsheet, since AfterShip has no trigger of its own.

  2. 02

    Add Create a Tracking

    Click the + on the right of that module, search AfterShip and choose Create a Tracking. Create the connection with your API key, then map the tracking number coming from the first module.

  3. 03

    Attach who gets notified

    Add Add a Notification after it and map the same tracking number, then the receivers taken from the order. Each bundle, one order passing from module to module, gets its own notification.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received, so you can check the tracking appeared in AfterShip before going further.

  5. 05

    Set the schedule and switch it on

    Open the clock on the first module to set how often it runs, every 15 minutes by default, then switch the scenario on. Each module run on a bundle is one operation on your plan.

Modules

What each AfterShip module does

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

AfterShip1

Add a Notification

Action

In Make“Adds notification receivers to a tracking number.”

Makes sure the right people hear about a parcel by adding notification receivers to an existing tracking number. The buyer or your account manager stays informed without anyone touching AfterShip.

When to use it
right after a tracking is created, when the order already tells you who should follow the delivery.
Watch out
it works on a tracking that already exists, so place it after Create a Tracking or a search.
AfterShip2

Create a Tracking

Action

In Make“Creates a new tracking.”

Opens a new tracking in AfterShip from data another app already holds, so a shipped order shows up in your dashboard with no manual entry. This is usually the first AfterShip module in a scenario.

When to use it
as soon as your shop or warehouse tool records a shipment with its tracking number.
Watch out
test with Run once first, so a mapping mistake does not create a batch of wrong trackings.
AfterShip3

Delete a Tracking

Action

In Make“Deletes an existing tracking.”

Removes a tracking from AfterShip for good, which keeps your list limited to parcels that are really on their way. Pair it with a search when you only know the order, not the record.

When to use it
an order gets cancelled before it leaves, or a tracking was created by mistake.
Watch out
check with Run once that the module targets the right record before switching the scenario on, or you remove the wrong tracking.
AfterShip4

Get a Notification

Action

In Make“Retrieves an existing notification.”

Reads who is currently set to receive notifications for a tracking, so the next module can show or check that list. Handy when a customer says nobody told them about their parcel.

When to use it
in a support flow, to paste the current receivers into a ticket before changing anything.
Watch out
it only reads; to change the list, follow it with Add a Notification or Remove a Notification.
AfterShip5

Get a Tracking

Action

In Make“Retrieves an existing tracking.”

Brings back one tracking record you already know, so its details can flow into an email, a ticket or a spreadsheet row. It answers the question “where is this parcel” inside another tool.

When to use it
a ticket arrives with a tracking number and your agent wants the record next to it.
Watch out
it needs one specific tracking; when you only have a partial clue, start with Search Trackings instead.
AfterShip6

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the AfterShip API with the same connection, which covers what the eight other modules leave out. You write the request yourself, so this one asks for a look at AfterShip's API reference.

When to use it
the action you need has no dedicated module in this list.
Watch out
a wrong path or method only shows up when the call runs, so read the answer bundle after Run once before switching the scenario on.
AfterShip7

Remove a Notification

Action

In Make“Removes an existing notification.”

Takes receivers off a tracking so they stop hearing about that parcel. Useful for keeping updates away from a contact who has left the account or asked to be removed.

When to use it
a customer changes the contact on an order and the old address should drop out.
Watch out
run Get a Notification first if you are unsure who is on the list, so you remove the right receiver.
AfterShip8

Update a Tracking

Action

In Make“Updates an existing tracking.”

Changes an existing tracking so AfterShip matches what really happened to the order, without rebuilding the record. You keep the same record instead of deleting and recreating it.

When to use it
an order is edited in your shop after shipping and the tracking should reflect the change.
Watch out
the module needs the tracking to exist; when the scenario only has the order, find the record with Search Trackings first.
AfterShip9

Search Trackings

Search

In Make“Searches for trackings or lists them all.”

Finds trackings in your AfterShip account, or lists all of them, and hands each result to the next module as its own bundle. It is the way to act on records you cannot name one by one.

When to use it
building a report of open parcels in a sheet, or finding a tracking before updating it.
Watch out
it can return zero, one or many bundles, and each one run through later modules counts as operations.
Need help

Need help automating AfterShip with Make?

A person reads every message.

FAQ

Questions about AfterShip and Make

01Is the AfterShip Make integration free?
Yes, on the Make side. AfterShip is a standard app, so its modules are available from the Free plan, which includes 2 active scenarios, a minimum of 15 minutes between scheduled runs, and 5 minutes of execution per run. Paid plans such as Core, Pro, Teams and Enterprise lower the interval to 1 minute and count usage in credits, meaning operations, per month. You still need an active AfterShip account with an API key; AfterShip's own subscription is described on its pricing page, and this page quotes no price for it.
02What do you need to connect AfterShip to Make?
An active AfterShip account and an API key. In AfterShip, go to the API keys settings page, click Create API key, name it, choose the signature header, set admin API permissions and save. Copy the key shown on screen. In Make, add any AfterShip module, click Create a connection, optionally name the connection, then paste the key. That single connection serves all nine AfterShip modules, so you will not repeat the steps for each one.
03Can AfterShip start a Make scenario on its own?
No. AfterShip has no trigger module in Make, neither scheduled nor instant, so nothing in AfterShip can launch a scenario. You start the scenario another way: with a trigger from another app, such as the tool where orders are recorded, or simply on a schedule, which is every 15 minutes by default on a new scenario. The AfterShip modules then do their work after that first step, for example creating a tracking or searching the existing ones.
04What if an AfterShip module is missing in Make?
Use Make an API Call. With the same connection, it can reach any endpoint of the AfterShip API, which covers actions the eight listed modules do not offer. You will need AfterShip's API reference to write the request, then Run once to check the answer. Keep in mind that the Make documentation for this app states it is AI-generated from AfterShip's docs and may contain mistakes, so confirm important details with AfterShip directly before relying on them.
05Should you use Make or n8n for AfterShip?
It depends on your criteria rather than on a winner. In Make you get 9 AfterShip modules, one connection reused by all of them, and Make an API Call for the rest of the API. The same app often exists as an n8n node as well, so compare what each tool offers for the exact actions you need and which one your team already works in. The comparison page linked higher up lists the differences between the two tools side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations