Qapla
LogisticsConnect AI agents to Qapla', an Italian multi-carrier shipment tracking platform. Agents push shipments and orders, pull tracking updates, detect couriers, and create labels so post-shipping visibility stays in sync across carriers.
What This Integration Enables
Qapla sits on the post-purchase tier: it takes shipments across a wide multi-carrier network, standardizes their states, and turns those states into notifications your customer reads. That framing is the whole point of the connector, because it means the operations here are not neutral data writes. Push Shipments imports up to 100 shipments to start tracking, and importing them starts the channel's customer notifications. Delete Shipment removes a shipment and stops its tracking and its pending notifications. An agent working with Qapla is operating a customer communication channel whether or not it thinks of it that way.
FlowRunner agents push shipments and pre-shipment orders in batches, then retrieve a single shipment with its status history and parcels. They list shipments filtered by ship date, order date, or upload date, and pull only the shipments whose status changed inside a window. They resolve courier codes, detect a likely courier from a tracking number's format, create and retrieve shipping labels with optional cash on delivery, and check the channel's remaining credit balance. Get Qapla Statuses returns the reference map of standardized statuses, which is what lets one workflow behave the same way across couriers instead of carrying a translation table per carrier. API keys are scoped to a single channel, so a business running several storefronts configures several connectors rather than one.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Shipments enter tracking as they ship, not as a nightly file
As each order is dispatched, the agent collects it into a working batch. When the batch is ready, or the day closes, it resolves any missing courier with Detect Courier, checks the batch against what is already loaded, and calls Push Shipments. Customers begin receiving the channel's tracking notifications without anyone building a spreadsheet, and the shipment record in Shopify or the ERP is updated with the Qapla reference so the two stay joined.
Status changes drive support and finance, not just email
On a schedule the agent calls Get Tracking Updates for the window since the last run and receives only shipments whose standardized status moved. Deliveries close their fulfillment record. Failed and returning states open a case in Zendesk with the tracking history already attached. Because the statuses are standardized by the platform, the same branch logic covers every courier in the channel, which is the practical reason to sit behind an aggregator instead of integrating each carrier directly.
Credit balance watched before it becomes an outage
Labels and tracking consume channel credit. The agent calls Get Credits on a schedule and, when the balance falls under the threshold the team set, posts the current balance and the recent daily burn to the operations channel. Running out of credit mid-afternoon stops labels being created, which stops parcels leaving. Watching a number is exactly the kind of work that should never depend on someone remembering.
Human-in-Loop Highlight
The gate sits on Push Shipments, and it is there because in Qapla an import is a send. Pushing a batch starts tracking and starts the channel's customer notifications, up to 100 real people at a time, and Delete Shipment only stops notifications that are still pending. Anything already dispatched has arrived. Two failure modes make that expensive. A re-run of yesterday's batch notifies the same customers twice about parcels they already received. A tracking number whose courier was guessed wrong sends a notification whose tracking link points at the wrong carrier's site, so the customer clicks through to a page that says the shipment does not exist. So the agent prepares the batch, runs Detect Courier over the uncertain rows, checks for overlap with what is already loaded, and then stops: "Batch ready, 84 shipments. 3 tracking numbers match more than one courier format. 6 already exist in Qapla from this morning's run. Push all 84, push the 75 clean rows, or hold?" A person answers in one message, and only then do 84 customers hear anything. That is human-in-the-loop placed on the batch boundary, because the batch boundary is where the notification volume is decided.
Agent Capabilities
13 actionsShipments
4- Push Shipments Imports up to 100 shipments to start tracking and trigger the channel's customer notifications. Used to move the day's dispatches into tracking, and reviewed by a person because the import is also a send.
- Get Shipment Retrieves one shipment with its current status and optional tracking history, notifications, order rows, and parcels. Used when support or finance needs the full picture on a single parcel.
- List Shipments Lists shipments filtered by ship date, order date, or upload date. Used for reconciliation and reporting across a period.
- Delete Shipment Removes a shipment and stops its tracking and pending notifications. Used to withdraw a shipment loaded in error, with the limit that already sent notifications cannot be recalled.
Tracking
1- Get Tracking Updates Returns shipments whose tracking status changed within a date and time window, using standardized statuses. Used as the change feed that drives support, finance, and customer messaging.
Couriers
2- Get Couriers Lists the couriers available to the channel with their codes and tracking URL templates. Used to resolve a carrier code before pushing a shipment.
- Detect Courier Identifies the likely courier or couriers for a tracking number by its format. Used to fill in a missing carrier, and to expose the rows where the format is ambiguous rather than picking one.
Labels
2- Create Label Generates a shipping label with a selected courier, with optional cash on delivery. Used when the label is produced inside the workflow rather than in a separate shipping tool.
- Get Label Retrieves a previously created label as JSON, with the document in PDF, JPG, or ZPL. Used to hand the label to a printer, a warehouse system, or a document archive.
Orders
2- Push Orders Imports up to 100 pre-shipment orders. Used to register orders in the platform before a tracking number exists.
- List Orders Lists orders filtered by order date or upload date. Used to reconcile what was registered against what actually shipped.
Account
2- Get Credits Returns the remaining credit balance for the channel. Used to alert on low balance before label creation starts failing.
- Get Qapla Statuses Returns the reference map of standardized tracking statuses. Used so branch logic is written once against standard states rather than per carrier.
Frequently Asked Questions
What can FlowRunner do with Qapla?
FlowRunner agents can run Push Shipments, Get Shipment, and List Shipments in Qapla, plus 10 more actions.
Does connecting Qapla to FlowRunner require OAuth?
No. Qapla connects to FlowRunner with an API key, no OAuth flow required.
Can Qapla trigger a FlowRunner workflow automatically?
Qapla doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Qapla
$100 in credits. No card required. Connect in minutes.