> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.ship24.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Ship24 Order Tracking for Make

### Introduction

Ship24 Shipment Tracking for Make allows you to automatically create, update, and refresh shipment trackers using the Ship24 API inside Make automation scenarios.

By connecting Ship24 with apps such as Google Sheets, CRMs, ecommerce platforms, or internal systems, you can automate shipment monitoring and keep delivery data synchronized across your workflows.

Ship24 supports tracking across **2,500+ couriers and marketplaces worldwide**, enabling businesses to monitor shipment progress, retrieve tracking events, and update operational systems without manual intervention.

![](https://storage.crisp.chat/users/helpdesk/website/-/b/0/5/d/b05de28401784000/image_1xat53i.png =1600x900)

### In this article

* [What does the Make integration do?](#3-what-does-the-make-integration-do)
* [Requirements](#3-requirements)
* [Setup](#3-setup)
* [Webhook trigger for instant tracking updates](#3-webhook-trigger-for-instant-tracking-updates)
* [Example templates](#3-example-templates)
* [Scenario structure overview](#3-scenario-structure-overview)
* [Google Sheets structure example](#3-google-sheets-structure-example)
* [Limits and safeguards](#3-limits-and-safeguards)
* [Troubleshooting](#3-troubleshooting)

### What does the Make integration do?

The Ship24 Make integration allows you to automate shipment tracking workflows by connecting Ship24 with other apps inside your Make scenarios.

With Ship24 in Make, you can:

* Create shipment trackers from tracking numbers
* Create trackers and immediately retrieve tracking results
* Receive new tracking events instantly using the webhook trigger
* Refresh tracking information automatically
* Update external systems when shipment status changes
* Process shipments in bulk using spreadsheet or database inputs
* Build automated monitoring workflows that periodically check shipment updates

Typical use cases include:

* Tracking ecommerce orders stored in Google Sheets
* Updating shipment status in CRMs or order management systems
* Monitoring active shipments and refreshing results periodically
* Triggering notifications when delivery milestones change

### Requirements

Before using the Ship24 integration in Make, you will need:

* A **Ship24 API key**
* A **Make account**
* At least one connected data source such as Google Sheets, a database, or another system containing tracking numbers

You can access your API key in your [Ship24 dashboard](https://dashboard.ship24.com/integrations/api-keys).

### Setup

###### Connect your Ship24 account

To use Ship24 modules in Make, you first need to connect your Ship24 account using your API key.

1. Add a Ship24 module to your Make scenario.
2. When prompted, create a new connection.
3. Enter your Ship24 API key.
4. Save the connection.

Once connected, the Ship24 modules can be used across all your Make scenarios.

![](https://storage.crisp.chat/users/helpdesk/website/-/b/0/5/d/b05de28401784000/image_1p8la9w.png =1600x900)

### Webhook trigger for instant tracking updates

In addition to modules that create and refresh trackers on a schedule, the Ship24 integration includes a **New Tracking Event** instant trigger. This trigger starts your scenario the moment Ship24 registers a new tracking event, so your workflows react to shipment updates in real time without scheduled polling or refresh calls.

![](https://storage.crisp.chat/users/helpdesk/website/-/b/0/5/d/b05de28401784000/image_703eub.png =1600x900)

This is the recommended approach when you want to:

* Send instant notifications when a shipment status changes
* Update your CRM, database, or spreadsheet as soon as a tracking event occurs
* Reduce API usage by removing periodic refresh calls

###### Set up the webhook trigger

1. In your Make scenario, add the Ship24 **New Tracking Event** module as the trigger. No Ship24 connection is required for this module.
2. Make generates a webhook URL for the scenario. Copy this URL.
3. Open the [webhook settings in your Ship24 dashboard](https://dashboard.ship24.com/integrations/webhook).
4. Paste the webhook URL, click **Test**, then click **Save**.
5. Back in Make, click **Re-determine data structure** so the test payload maps all available fields.
6. Add the modules you want to run after the trigger and map the tracking data into them.

Once the scenario is activated, Ship24 automatically pushes every new tracking event for your active trackers to your scenario.

###### Available data

Each webhook call contains exactly one tracking update with one new event. The payload includes:

* **Metadata**: message ID and generation timestamp
* **Tracker**: tracker ID, tracking number, shipment reference, and client tracker ID
* **Shipment**: shipment ID
* **Events**: event ID, status, and occurrence datetime
* **Statistics**: shipment milestone timestamps

###### Important notes

||| The Ship24 dashboard stores a single webhook URL. Only one destination scenario can receive tracking events, and saving a new URL stops updates to the previous one.

|| Webhooks are sent for shipments that have an active Ship24 tracker, for example trackers created with the Ship24 modules in Make.

### Example templates

The Ship24 Make integration includes example templates to help you start automating shipment tracking quickly.

###### Simple shipment tracker

Creates a tracker for each tracking number and records the latest shipment status.

1. Read tracking numbers from Google Sheets.
2. Create Ship24 trackers and retrieve tracking results.
3. Write the latest status and timestamp back to the sheet.

This template is ideal for smaller lists or workflows where shipment data is refreshed regularly.

![](https://storage.crisp.chat/users/helpdesk/website/-/b/0/5/d/b05de28401784000/image_9bcysg.png =1600x900)

###### Smart shipment tracker with new and scheduled refresh

Automates both new tracker creation and periodic status updates.

1. Search for rows containing tracking numbers.
2. Route rows into two paths:

* **New shipments**: create trackers and retrieve results
* **Existing shipments**: refresh results if the last check is older than 3 hours

3. Update the spreadsheet with the latest tracking data.

This approach avoids unnecessary API calls and ensures active shipments remain up to date.

![](https://storage.crisp.chat/users/helpdesk/website/-/b/0/5/d/b05de28401784000/image_12e59ah.png =1600x900)

### Scenario structure overview

Most Ship24 automation workflows follow a similar pattern:

1. **Retrieve tracking numbers.** For example, search rows in Google Sheets or retrieve orders from an ecommerce platform.
2. **Create or refresh trackers.** Call the Ship24 API to create trackers or retrieve the latest tracking events.
3. **Update your system.** Write the latest shipment status back into your spreadsheet, CRM, or database.

Optional logic such as routers or filters can be added to control when trackers are created or refreshed.

### Google Sheets structure example

When using Google Sheets as a data source, your sheet should contain columns that allow the scenario to track shipment status.

| Column | Purpose |
| --- | --- |
| Tracking Number | Shipment tracking number |
| Latest Status | Latest shipment milestone or status |
| Last Update | Timestamp of the last tracking check |
| Tracker ID | Ship24 tracker identifier |

Additional optional columns may include:

* Courier Code
* Order Number
* Shipment Reference
* Destination Country

### Limits and safeguards

To keep performance stable and avoid unnecessary API calls, Ship24 templates typically include safeguards such as:

* Skipping shipments that are already **Delivered**
* Avoiding refresh calls if the last check occurred recently, for example within 3 hours
* Processing shipments sequentially
* Continuing scenario execution if a single row fails

### Troubleshooting

###### API key error

* Ensure your Ship24 API key is valid and correctly entered in the Make connection settings.
* Ensure your Ship24 plan matches the plan required by the module. Modules are split by plan type, per-shipment plans and per-call plans.

###### Tracking data not updating

Check that:

* A valid **tracking number** exists
* The shipment has not already been delivered
* The scenario filters are not excluding the row
* The scenario has run successfully

###### Scenario returns no results

Confirm that the data source contains tracking numbers matching the search filters used in the scenario.

###### Webhook trigger not receiving events

Check that:

* The Make scenario is turned **on**, since scheduled scenarios and instant triggers only run while active
* The webhook URL saved in your Ship24 dashboard matches the URL shown on the **New Tracking Event** module in your scenario
* No other webhook URL has been saved since, as Ship24 stores only one webhook URL at a time
* The shipment has an active Ship24 tracker

You can use the **Test** button on the Ship24 webhook settings page to send a sample payload and confirm the connection.

If you continue experiencing issues, [contact the Ship24 support team](https://www.ship24.com/contact-us).