Introduction

Ship24 Shipment Tracking for n8n allows you to automate shipment tracker creation, monitoring, and delivery updates directly inside your n8n workflows using the Ship24 API. The integration includes two nodes: the Ship24 action node for creating and querying trackers, and the Ship24 Trigger node for receiving live tracking events via webhooks.

By connecting Ship24 with services such as Google Sheets, databases, CRMs, ecommerce platforms, or internal systems, you can automatically create trackers, retrieve shipment events, react to real-time delivery updates, and synchronize tracking data across your automation workflows. The Ship24 n8n community node is designed for automation workflows that process multiple shipments, handle bulk tracking operations, and integrate shipment visibility into operational systems. The node supports full n8n multi-item processing, allowing large shipment lists to be handled efficiently while maintaining structured results and resilient error handling.

In this article

• What does the n8n node do?
• Requirements
• Installation
• Credentials Setup
• Node Overview
• Webhook Trigger
• Example Workflow Structure
• Bulk Processing Behaviour
• Example Data Structure
• Limits and Safeguards
• Troubleshooting

What does the n8n node do?

The Ship24 n8n node allows you to automate shipment tracking workflows by integrating Ship24 directly into your n8n automation environment.
With Ship24 in n8n, you can:

• Create shipment trackers from tracking numbers
• Create trackers and immediately retrieve tracking results
• Retrieve tracking results using a tracking number
• Retrieve tracking results using a tracker ID
• Update tracker subscription status
• Process shipments in bulk from spreadsheets, APIs, or databases
• Build automated workflows that monitor shipment progress
• Receive live tracking events automatically via webhooks
• Integrate shipment tracking with other automation systems

Typical use cases include:

• Tracking ecommerce orders stored in Google Sheets
• Creating trackers automatically when new orders arrive
• Updating shipment status in CRMs or internal systems
• Monitoring active shipments and refreshing tracking results
• Triggering notifications when delivery milestones change
• Reacting to live tracking events as they happen via webhooks

Requirements

Before using the Ship24 n8n node, you will need:

• A valid Ship24 plan and API key
• An n8n instance with community nodes enabled
• A data source containing tracking numbers (such as Google Sheets, a database, or API)

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

Installation

The Ship24 integration for n8n is distributed as a community node.
To install it:

1. Open n8n.
2. Go to Settings → Community Nodes.
3. Click Install.
4. Enter the package name: n8n-nodes-ship24
5. Restart n8n if required.

Once installed, the Ship24 node will appear in the n8n node list and can be added to workflows.

Credentials Setup

Before using the node, you must connect your Ship24 API key.

1. Add a Ship24 node to your workflow.
2. When prompted for credentials, create new credentials.
3. Select Ship24 API.
4. Enter your Ship24 API key.
5. Save the credentials.

The connection can then be reused across all Ship24 nodes in your workflows.

Node Overview

The Ship24 node provides two main resources:

Tracker

Used for shipment tracking operations:

• Create trackers
• Create trackers and retrieve results
• Retrieve tracking results
• Update tracker subscription status

Utility

Provides advanced API access by allowing users to define:

• HTTP method
• API path
• Query parameters
• Request body

This allows advanced users to call additional Ship24 API endpoints directly from n8n.

Webhook Trigger

The Ship24 Trigger node starts a workflow automatically whenever Ship24 sends a tracking event to your webhook URL. This allows you to react to live delivery updates in real time, without polling the API.

Setup

1. Add the Ship24 Trigger node to a new workflow.
2. Two webhook URLs are displayed at the top of the node panel:

• Test URL — active while the workflow is open in the editor. Click Execute step to start the node listening, then use the Ship24 dashboard test button to send a sample payload and verify your workflow.
• Production URL — active when the workflow is activated (toggle top-right). This is the URL to save in your Ship24 dashboard.

3. Go to Ship24 Dashboard → Integrations → Webhook, paste the URL, test it, and save.

Once the Production URL is saved in your dashboard, Ship24 will push tracking events to your workflow automatically for all subscribed trackers.

Webhook Payload

Ship24 sends tracking events as a JSON array. Each element contains the tracker details, shipment status, individual events, and delivery statistics. The node passes the raw payload through so you can map any field directly in your workflow.

Webhook Secret

Ship24 allocates a random webhook secret to your account, visible in your dashboard. It is sent with every request as:

Authorization: Bearer your_webhook_secret

To validate it, add an IF node after the trigger and compare {{ $request.headers.authorization }} to your expected value. This is optional but recommended to ensure requests genuinely originate from Ship24.

Example Workflow Structure

Most Ship24 automation workflows follow a similar structure.

Step 1 -- Retrieve tracking numbers

Retrieve tracking numbers from a source such as:

• Google Sheets
• Ecommerce orders
• Databases
• APIs
• Internal systems

Step 2 -- Create or retrieve trackers

Use the Ship24 node to:

• Create shipment trackers
• Retrieve shipment tracking results
• Update existing trackers

Step 3 -- Process results

Use the returned shipment data to:

• Update spreadsheets
• Update CRM systems
• Store shipment events in databases
• Send email notifications

Additional nodes such as IF, Switch, or Code nodes can be used to control workflow logic.

Bulk Processing Behaviour

The Ship24 node fully supports n8n multi-item workflows. Each incoming item typically contains one tracking number.
Example input items:
[
{ "trackingNumber": "0123456789" },
{ "trackingNumber": "0123456790" },
{ "trackingNumber": "0123456791" }
]

When bulk mode is enabled, the node automatically groups tracking numbers into API requests of up to 100 tracking numbers per request.

Example:

Each input item still produces one output item.

Example Data Structure

A common input format used in workflows is:

Optional columns may include:

• Courier Code
• Order Number
• Shipment Reference
• Destination Country Code
• Destination Post Code

Limits and Safeguards

To ensure stable automation workflows, you can include safeguards such as:

• Skipping shipments already marked as Delivered
• Avoiding refresh calls if the shipment was recently checked
• Processing shipments sequentially
• Allowing workflows to continue if a single shipment fails

The node also supports continueOnFail, allowing workflows to continue processing even when an individual item returns an error.

Troubleshooting

API key error

• Ensure you have the correct plan type
• Ensure your Ship24 API key is valid and correctly entered in the credentials configuration.

No tracking results returned

Check that:

• The tracking number is valid
• The supporting tracker details are accurate
• The shipment exists in the carrier system
• The tracker was successfully created

Invalid tracker ID

Tracker ID operations require a valid UUID format. The tracker ID is returned when a tracker is created

Bulk workflow returns partial errors

Bulk requests may contain multiple trackers. If some trackers fail validation or are rejected by the API, structured error responses are returned for those items.

Workflow stops on error

Enable continueOnFail in the node settings to allow workflows to continue processing other shipments even if one item fails.

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

Updated on: 23/06/2026