Ship24
LogisticsTrack packages across hundreds of couriers worldwide through Ship24. Agents register tracking numbers, retrieve full checkpoint history and delivery status, track a parcel in a single call, and resolve courier codes before creating trackers.
What This Integration Enables
Ship24 does one job across hundreds of couriers worldwide: turn a tracking number into a normalized stream of checkpoints and a detected shipment status, whether the parcel rides USPS, DHL, China Post, or a regional carrier you have never heard of. This connector makes that stream available to agents. FlowRunner agents register trackers as shipments are created, attach your own order ID as a clientTrackerId so lookups speak your system's language, pull full checkpoint history with milestone timestamps and estimated delivery, track a parcel in a single call, and resolve courier codes before creating trackers. The position this page takes: post-purchase experience is a data latency problem. The store that answers "where is my order" before the customer asks is running the same carriers as everyone else; it just found out first. Agents are how you find out first. - Register every outbound shipment for monitoring at the moment it ships - Drive customer notifications from delivery milestones across all carriers - Surface exceptions to the fulfilment team while intervention is still cheap - Log shipment status into sheets and reporting systems for lane-level analysis The clientTrackerId is the detail that makes this scale cleanly. By storing your order number on the tracker at creation, every later lookup runs on an identifier your systems already know, so the workflow never maintains a mapping table between Ship24's IDs and your own.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Every shipment monitored from the first scan
A [Shopify](/integrations/shopify) order ships. The agent calls Create Tracker with the tracking number, courier code, destination country, and postcode, storing the order number as clientTrackerId. Because the endpoint is idempotent, retries never create duplicates. From that moment the parcel is on watch: status checks key off the order ID your systems already use, and no one maintains a spreadsheet of tracking numbers by hand.
The delivery email that sends itself
The scheduled sweep calls Get Tracking Results for active trackers. When a shipment reaches its delivered milestone, the agent sends the customer confirmation through [Gmail](/integrations/gmail) with the delivery time and final checkpoint location, and closes the order. When status shows out-for-delivery, the heads-up goes out that morning. The support queue's most common ticket declines for the simplest reason: the answer keeps arriving before the question.
The exception desk with a morning queue
Overnight, the agent flags every tracker whose status reads exception or whose checkpoints have gone quiet past the lane's normal cadence. Each flagged shipment posts to the fulfilment channel in [Slack](/integrations/slack) with its full event history, and the batch logs to [Google Sheets](/integrations/google-sheets) for pattern analysis: which carriers stall where, which lanes eat the most exceptions. The team starts the day working a ranked queue of problems that are hours old instead of discovering problems that are weeks old.
Human-in-Loop Highlight
Search Tracking By Number carries a warning in its own contract: tracking numbers are not globally unique, so one number can return multiple trackings tied to different trackers. An agent that grabs the first result and mails a customer "your parcel was delivered in Osaka" about someone else's shipment has sent a confidently wrong message to a real inbox, and the follow-up correction never fully unrings that bell. The same discipline applies downstream of exceptions: a failed-delivery status is where money moves, because the natural next steps are a reshipment or a refund, both unrecoverable once granted against a parcel that was actually still moving. So FlowRunner workflows resolve trackers by clientTrackerId wherever possible, treat any multi-result lookup as ambiguous and route it to a person, and put every reship-or-refund decision in front of the fulfilment owner with the checkpoint history attached. The monitoring runs at machine scale across every carrier at once. The messages and money that leave based on it wait for certainty or a human, whichever comes first.
Agent Capabilities
7 actionsTrackers
3- Create Tracker Registers a shipment for monitoring by tracking number, with optional courier codes, origin and destination countries, destination postcode, and shipping date for accuracy. Idempotent: identical calls return the same tracker, never a duplicate.
- List Trackers Returns a page of existing trackers with trackerId, tracking number, references, flags, and creation date. Page-based pagination for walking the full account.
- Get Tracker Retrieves a single tracker's metadata by trackerId or your own clientTrackerId. No checkpoint events; use Get Tracking Results for history.
Tracking
3- Get Tracking Results Returns full results for an existing tracker: detected shipment status, all checkpoint events newest first, milestone timestamps, and estimated delivery. The read every notification and exception flow keys off.
- Track (Create and Get Results) One-call convenience that creates the tracker if needed and immediately returns its results. Built for single-step tracking without separate tracker management.
- Search Tracking By Number Returns results for existing trackers matching a tracking number, which may be multiple, since numbers are not globally unique. The lookup this page's ambiguity gate applies to.
Couriers
1- List Couriers Returns the full supported courier list with courierCode, name, website, operating country, postal-operator and deprecation flags, and any extra fields a courier requires. The resolution step before accurate tracker creation.
Frequently Asked Questions
What can FlowRunner do with Ship24?
FlowRunner agents can run Create Tracker, List Trackers, and Get Tracker in Ship24, plus 4 more actions.
Does connecting Ship24 to FlowRunner require OAuth?
No. Ship24 connects to FlowRunner with an API key, no OAuth flow required.
Can Ship24 trigger a FlowRunner workflow automatically?
Ship24 doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Ship24
$100 in credits. No card required. Connect in minutes.