Seven Senders

Connect AI agents to Seven Senders, a European parcel delivery orchestration and tracking platform. Agents create orders and shipments, push state events, generate carrier labels, and pull end to end tracking history so cross-border delivery data stays current in every system.

Verified 17 actions Session available

Seven Senders website ↗ Platform Documentation ↗ Capability data verified 2026-08-12

An order is paid in the shop and needs a tracking identity before any parcel exists

Create Order imports it as the top level record that shipments will attach to

Get Carrier Selections returns the carriers suitable for that destination country and postal code

Add Order State records paid and in production as they happen, which the customer's tracking reflects

The picked quantity is compared against the ordered quantity, since a short pick means a second parcel is still owed

Any order that looks finished but is not goes to the fulfillment owner with both counts

They confirm the order is complete, and only then does Update Order set boarding complete and close it to new shipments

What This Integration Enables

Seven Senders is not a courier and does not own a van. It is the layer that turns a European cross-border delivery, which in practice means several carriers with several status vocabularies across several countries, into one record with one narrative. That makes this connector different from every carrier connector in the catalog in a way that matters for how you use it: what you write here is largely what your customer reads. Create Order imports the order as the top level entity, Create Shipment attaches a trackable parcel to it, Add Order State pushes lifecycle events such as paid, in production, or canceled, and Get Tracking History returns the carrier scan events with timestamps, status, and location. Those pieces are the customer-facing truth, not an internal mirror of it.

The order and shipment surfaces are complete in both directions. Get Orders and Get Shipments list and filter, with orders filterable by order ID, order URL, state, language, and boarding status, and shipments filterable by tracking code, reference number, recipient details, carrier service, and order ID, both capped at a hundred records per call. Get Order and Get Shipment read single records by internal numeric ID. Update Order and Update Shipment change only the fields you supply, which is how a tracking code gets attached or corrected after the fact. Delete Order and Delete Shipment permanently remove a record. Add Shipment Event records a refund or a return to warehouse on a parcel, which is the signal that closes the loop on a delivery that came back.

Labels and carriers round it out. Create Label generates a shipping label with a chosen carrier and service level and returns the tracking code plus label metadata, for outbound, return, or both directions in one request, and Download Label writes the PDF into FlowRunner file storage and returns a URL. List Carriers reports the carriers available on the account with their codes, display names, and countries of operation, and Get Carrier Selections narrows that to the ones suitable for a specific destination, optionally by country and postal code. Authentication is an access key exchanged automatically for a short-lived token. There are no triggers, so the flow is driven by shop events and by polling Get Tracking History or Get Shipments on a schedule.

Without FlowRunner

Tracking scattered across carriers A cross-border order's parcels live in three carrier portals with three status vocabularies

Customers told nothing between dispatch and delivery The shop knows an order shipped and learns the rest when someone complains

Order state kept only in the shop Paid, in production, and canceled exist in the ERP and nowhere the delivery data can see them

With FlowRunner

Tracking normalized in one record Shipments attach to one order and carrier scan events arrive as a single history

Customers updated from real events Status changes come from carrier scans the flow reads, not from a dispatch timestamp

Order state pushed where it is visible Lifecycle events land alongside the delivery data, so tracking and analytics agree with the shop

Use Case Scenarios

One order, several parcels, one story the customer reads

An order is paid in Shopify or Magento. The agent calls Create Order immediately, before anything is picked, so the order has a tracking identity from the start, and calls Add Order State with paid. As the warehouse works, each parcel that leaves becomes a Create Shipment attached to that order ID, with the carrier and tracking code supplied. When the shop splits a delivery across two warehouses and two carriers, which is normal in cross-border retail and confusing for the customer, both shipments hang off the same order and Get Tracking History returns each one's carrier scans in a form the shop can present together. The customer sees one order with two parcels rather than two unexplained tracking links from carriers they have never heard of.

Delivery exceptions that reach a person while they are still fixable

On a schedule the agent walks the open shipments with Get Shipments and pulls Get Tracking History for each, comparing the newest carrier event against the last one recorded. Ordinary progress updates flow into the order record and out to the customer through Klaviyo. The interesting cases get routed instead of announced: a parcel with no carrier scan since a handover event days old, a failed delivery attempt, a shipment whose carrier reports it heading back. Each becomes an automation exception in Zendesk with the full scan history attached, so the agent handling it opens a ticket that already contains the evidence. Returns that do come back get Add Shipment Event so the delivery record says so, rather than the parcel simply going quiet.

Choosing the carrier per destination, not per country

Cross-border shipping punishes a single carrier choice, because the carrier that is strong in one country is often mediocre two borders away and unavailable in a specific postal area. Before generating a label, the agent calls Get Carrier Selections with the destination country and postal code and reads back the carriers suitable for it, filters against the business rules about service levels and cost, and calls Create Label with the chosen carrier and service. Download Label writes the PDF into FlowRunner file storage for the packing bench, and the returned tracking code goes onto the shipment so the tracking record is complete from the moment the label prints. The result is logged to Google Sheets so the carrier mix per destination is a thing the business can see and argue about.

Human-in-Loop Highlight

The gate on Seven Senders is unusual for a logistics connector because the risky action does not move a parcel. It publishes a claim. Add Order State records events such as paid, in production, or canceled, and those states appear in tracking and analytics, which means they reach the customer's tracking page. Pushing canceled onto an order whose parcel is genuinely on a van tells a customer their order was canceled while it is being delivered to them, and there is no correcting event that unrings that. Update Order has the quieter version of the same property: setting boarding complete closes the order to new shipments, so a split delivery's second parcel can never be attached to it afterward, and the customer's view of the order permanently shows one parcel where two were owed.

So the split is by direction of travel. Forward states that report progress, meaning paid and in production, the agent pushes freely, because they are true when it pushes them and they make the customer better informed. Terminal and closing states it prepares and hands over. Before setting boarding complete it compares the picked quantity against the ordered quantity and asks the fulfillment owner in Slack: "Order 9104 has 1 shipment boarded, 4 of 6 units. Backorder on 2 units shows no ship date. Setting boarding complete closes this order to further shipments and the customer's tracking will show it as fully boarded. Close it, or leave it open for the backorder?" Cancellations get the same treatment with the current carrier scan attached, because a cancellation request that arrives after handover is a return, not a cancellation, and the difference is visible in the tracking history the agent already has.

That is human-in-the-loop on a customer-facing statement rather than on a spend, which is the correct reading of what this platform is for. Two permanent operations belong in the same conversation for a simpler reason. Delete Order and Delete Shipment cannot be undone, and deleting a shipment does not recall a parcel. It removes the record of one that is still moving, which blinds both the shop and the customer while the physical thing continues on its way. Neither belongs in an automated cleanup routine unless that routine reports what it intends to remove first.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via Slack

Human decides

Agent resumes with decision

Agent Capabilities

17 actions

Orders

Create Order Imports an order into the account as the top level entity shipments attach to for tracking, taking the merchant order ID and optional metadata such as order date, language, and tags. Call it early, before parcels exist, so the order has a tracking identity from the start.
Get Orders Retrieves a paginated list of orders with filters for order ID, order URL, state, language, and boarding status, up to a hundred records per call. The read behind sweeping for orders left open past their expected completion.
Get Order Retrieves a single order by its Seven Senders internal numeric ID with its metadata and current state.
Update Order Updates an order by internal numeric ID, changing only the fields supplied. Commonly used to set boarding complete, which closes the order to new shipments and is therefore a decision rather than a housekeeping call.
Delete Order Permanently deletes an order by internal numeric ID. This cannot be undone, and it removes the record the customer's tracking is built on.
Add Order State Records a lifecycle state change on an order, for example paid, in production, or canceled. These states appear in tracking and analytics, so this action writes something a customer can read rather than an internal flag.

Shipments

Create Shipment Creates a trackable parcel and attaches it to an order by Order ID, taking recipient address details and an optional carrier and tracking code. Several shipments on one order is the normal shape for a split delivery.
Get Shipments Retrieves a paginated list of shipments with filters for tracking code, reference number, recipient details, carrier service, and order ID. The read behind a scheduled sweep of everything still in transit.
Get Shipment Retrieves a single shipment by internal numeric ID with recipient details, carrier, and current tracking status.
Update Shipment Updates a shipment by internal numeric ID, changing only the fields supplied. The usual reason is attaching or correcting a tracking code after the label was produced elsewhere.
Delete Shipment Permanently deletes a shipment by internal numeric ID. This cannot be undone and does not stop the parcel, so it removes visibility of something still in motion.
Add Shipment Event Records a refund or return event on a shipment, signaling that a parcel was refunded or came back to the warehouse. The action that makes a return an explicit fact in the record rather than a shipment that went quiet.

Tracking

Get Tracking History Retrieves the full tracking event history for a shipment, returning carrier scan events with timestamps, status, and location. The normalized view that makes several carriers readable as one narrative.

Labels

Create Label Generates a shipping label with a chosen carrier and service level and returns the tracking code plus label metadata, for outbound, return, or both directions. Supply recipient and carrier details and the package weight.
Download Label Downloads a generated label as a PDF into FlowRunner file storage and returns a URL, using the label ID from Create Label. The form a packing bench or a customer email can actually use.

Carriers

List Carriers Lists the carriers available in the account with each carrier code, display name, and countries of operation, paginated. The read that defines the choices a routing rule can make.
Get Carrier Selections Returns the carriers suitable for a given destination, optionally narrowed by country and postal code. The right call before creating a label, because carrier suitability in cross-border shipping varies below country level.

Frequently Asked Questions

What can FlowRunner do with Seven Senders?

FlowRunner agents can run Create Order, Get Orders, and Get Order in Seven Senders, plus 14 more actions.

Does connecting Seven Senders to FlowRunner require OAuth?

No. Seven Senders connects to FlowRunner with session-based authentication, no OAuth flow required.

Can Seven Senders trigger a FlowRunner workflow automatically?

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

Start building with Seven Senders

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

Start Building Free Talk to us