FlowRunner
PricingContact
Theme
Start Free

AfterShip

Logistics

Track shipments with AI agents through AfterShip. Agents create and update trackings, fetch the last checkpoint, detect the right courier from a tracking number, and monitor delivery status across supported carriers.

9 actions API key available
AfterShip website ↗ Platform Documentation ↗ Capability data verified 2026-07-28
A fulfillment provider marks an order shipped and hands back a carrier tracking number
Detect Courier resolves the most likely carrier for the bare tracking number
Create Tracking registers the shipment with the resolved courier slug and the order ID as a custom field
Get Last Checkpoint runs on a schedule and pulls the current status and location for every open shipment
The agent compares status tags against expected transit time and flags shipments stalled past threshold
A stalled-shipment digest posts to the operations channel with checkpoint history attached
The ops lead reviews the exceptions and decides which customers get a proactive delay notice and which carriers get a claim filed

What This Integration Enables

Shipment tracking is a monitoring problem, and monitoring is exactly the work that should never belong to a person. AfterShip normalizes checkpoint data across more than a thousand carriers into one status vocabulary, which turns "where is order 4712" from a research task into a query. FlowRunner agents register trackings the moment fulfillment confirms, resolve unknown carriers before monitoring starts, sweep checkpoint history on a schedule, and keep titles and custom fields synced to your order records. The position this page takes: post-purchase visibility is not a customer service feature, it is an operations control loop. The agent watches every shipment so your team only touches the ones that go wrong. - Register trackings automatically from ShipBob, Shopify, or any fulfillment signal - Resolve carriers for bare tracking numbers before creating the tracking - Pull last checkpoints for fast status checks without the full event log - Sweep open trackings on a schedule and route stalls to a human - Keep order IDs and display titles synced on existing trackings

Without FlowRunner

Tracking by browser tab Someone pastes tracking numbers into carrier sites one at a time, and only for the orders customers already complained about
Carrier guesswork A bare tracking number with no carrier attached means trial and error across FedEx, UPS, and USPS lookup pages
Silent stalls A shipment sits at a sort facility for five days and nobody knows until the refund request arrives

With FlowRunner

Every shipment registered at ship time Trackings are created the moment fulfillment confirms, keyed to the order ID, monitored across AfterShip's supported carriers
Carrier resolved automatically Detect Courier ranks candidate carriers before the tracking is created, so monitoring starts against the right one
Stalls surface as exceptions Agents sweep checkpoints on a schedule and put stalled shipments in front of a person before the customer notices

Use Case Scenarios

Ship confirmation to monitored shipment, untouched by hands

A [ShipBob](/integrations/shipbob) shipped event fires with a carrier tracking number. The agent calls Detect Courier to rank the likely carriers, then Create Tracking with the winning slug, the order number as a custom field, and the customer name as the display title. From that moment AfterShip monitors the shipment, and the FlowRunner flow that created it can be queried by order ID for the rest of the shipment's life. No spreadsheet of tracking numbers, no unmonitored orders.

The delivery dashboard that maintains itself

Every morning a scheduled flow calls List Trackings, pages through the open shipments, and writes each one's status tag, courier, and latest location to [Google Sheets](/integrations/google-sheets). Shipments tagged as exceptions or stalled in transit past the expected window get a second call to Get Tracking for full checkpoint history, and the detail posts to [Slack](/integrations/slack) as a thread the fulfillment team works through. The dashboard is live because an agent rebuilds it daily, not because someone remembered to.

Proactive delay notices with a person on the send

A sweep finds a shipment whose last checkpoint is four days old at an intermediate facility. The agent drafts a delay notice with the order details, the checkpoint history, and a revised estimate, then routes it to the CX lead through FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) step. The lead approves, edits, or holds the message. Customers hear about delays from you before they notice them, but no automated apology reaches a customer without a person deciding it should.

Human-in-Loop Highlight

Delete Tracking removes a shipment's entire checkpoint history from AfterShip, and it cannot be undone. In cleanup flows that prune delivered or duplicate trackings, that history is often the only timestamped record of where a package was and when, which matters the moment a customer disputes delivery or a carrier claim needs evidence. So the pruning agent never deletes on its own judgment. It assembles the candidates, shows what each tracking carries, and a person confirms the batch before Delete Tracking runs. The same discipline applies one step upstream: a delay notice drafted from checkpoint data is a write that reaches a customer, so it waits for the CX lead. Machine speed for the sweep, human sign-off for the parts that cannot be recalled.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via preferred channel
Human decides
Agent resumes with decision

Agent Capabilities

9 actions

Trackings

6
  • Create Tracking Creates a new tracking so AfterShip begins monitoring a shipment across 1000+ supported carriers. Only the tracking number is strictly required; providing the courier slug avoids auto-detection. Supports a display title and custom fields such as order IDs.
  • Get Tracking Retrieves a single tracking by its AfterShip tracking ID, including its current status tag, delivery estimates, and full checkpoint history. The deep-dive call behind exception review.
  • Get Last Checkpoint Retrieves only the most recent checkpoint for a tracking. The fast path for current status and location without the full event log, ideal for scheduled sweeps.
  • List Trackings Retrieves a paginated list of trackings with keyword search across tracking numbers, titles, and related fields. The backbone of dashboards and stall sweeps.
  • Update Tracking Updates an existing tracking's display title or custom fields. Used to keep order references synced; the tracking number and courier of an existing tracking cannot be changed.
  • Delete Tracking Permanently deletes a tracking and its checkpoint history. This action cannot be undone, which is why this page's human gate exists.

Couriers

3
  • Detect Courier Detects the most likely couriers for a given tracking number without creating a tracking. Returns a ranked candidate list, used before Create Tracking when the carrier is unknown.
  • List Couriers Lists the couriers currently activated on your AfterShip account, the set AfterShip matches your trackings against.
  • List All Couriers Lists all couriers AfterShip supports, regardless of account activation. Used to discover courier slugs for Create Tracking and Detect Courier.

Frequently Asked Questions

What can FlowRunner do with AfterShip?

FlowRunner agents can run List Trackings, Get Tracking, and Create Tracking in AfterShip, plus 6 more actions.

Does connecting AfterShip to FlowRunner require OAuth?

No. AfterShip connects to FlowRunner with an API key, no OAuth flow required.

Can AfterShip trigger a FlowRunner workflow automatically?

AfterShip doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with AfterShip

$100 in credits. No card required. Connect in minutes.