Cargus

Connect AI agents to Cargus, a Romanian courier and parcel delivery service. Agents calculate shipping prices, create and print waybills, track shipments, and reconcile cash on delivery and invoices so Romanian parcel operations run without manual data entry.

Verified 21 actions Session available

Cargus website ↗ Platform Documentation ↗ Capability data verified 2026-08-10

Orders paid or marked ready to ship accumulate through the day in the store

Create Waybill registers each shipment against a pick up point and returns its barcode

Print Waybills writes the labels into FlowRunner file storage as a PDF the packing bench prints

List Orders For Pickup Point counts what is open at that location and what is already validated

The open AWB count, the parcel and weight totals, and the cutoff time go to the warehouse lead

The lead confirms the dock is complete, and only then does Manage Order validate the pickup for every open waybill at once

What This Integration Enables

Cargus runs its own network across Romania, and this connector is shaped by that fact rather than by a generic shipping abstraction. Addresses do not arrive as strings. They resolve down a chain: Get Countries, then Get Counties, then Get Localities with their postal codes and network availability, then Get Streets from the Cargus nomenclature itself. An agent that walks that chain produces an address the network already recognizes, which is a different and much better outcome than producing an address that looks correct and fails at sorting. Get Routing By Address goes one step further and returns the transit priority, transit route, and delivery route codes for a sender and recipient pair, so serviceability can be checked before a waybill exists at all.

The second structural idea is that the shipment is not the unit of dispatch. A pick up point is. Get Pickup Points lists the sender warehouses active on the account, Create Waybill registers a shipment against one of them, and the waybills sit open at that location until Manage Order validates them, which sends the courier pickup request to Cargus for everything open there. List Orders For Pickup Point, List Orders By Date, and Get Order By ID read that pickup book: parcel and envelope counts, weight, AWB count, pickup window, and status. If you have ever run a warehouse, this is a familiar shape, and it is worth designing the flow around rather than against.

Around that core the surface covers the rest of a Romanian parcel operation. Get Price Tables lists the contracted rate tables on the account and Calculate Shipping Price returns base cost, weight cost, insurance, taxes, and grand total for a lane. Print Waybills renders one or more AWBs as PDF or HTML in A4 or 10x14 label format and uploads the result to FlowRunner file storage. Track Shipments returns full scan history including returns and redirected AWBs, and Get Delta Events returns everything that changed in a date interval, which is the right call for a polling loop. List Cash On Delivery reads the repayment records collected in the collector account, and List Invoices reads what Cargus billed. There are no triggers here: the Cargus API exposes no webhook infrastructure, so status arrives by polling Track Shipments or Get Delta Events on a schedule.

Without FlowRunner

Each order typed into WebExpress Recipient county, locality, and street are re-entered per shipment from the order screen

Pickup requested from memory Someone remembers to launch the order before the cutoff, or the courier arrives to nothing

COD reconciled from statements Repayment records are matched to orders by hand, days after the money was collected

With FlowRunner

Waybills created from order data The address resolves through the Cargus nomenclature and the AWB comes back with a barcode

Pickup launched on a confirmed count The flow reports how many AWBs are open at the pick up point before anyone validates

COD matched inside the flow Repayment records are pulled by date and reconciled against the orders that generated them

Use Case Scenarios

Order to labeled parcel without WebExpress

An order is paid in WooCommerce or Shopify. The agent resolves the recipient's county with Get Counties and their locality with Get Localities, checks Get Routing By Address to confirm the pair is serviceable, then calls Create Waybill against the warehouse's pick up point LocationId and gets a barcode back. Print Waybills renders the label at 10x14 into FlowRunner file storage, and the URL goes to the packing bench queue. The order record in the store is updated with the AWB barcode so customer service can answer a question without leaving the store admin. Nothing was typed into the carrier portal, and the address was validated against the carrier's own nomenclature rather than against a guess.

The cash on delivery reconciliation nobody enjoys

Romanian e-commerce runs heavily on cash on delivery, and the money arrives days after the parcel does, in batches, in a collector account. On a schedule, the agent calls List Cash On Delivery for the period and reads each record with its barcode, sender, receiver, repayment amount, and payment order details. It matches each barcode back to the order that produced it and posts the settled ones to Xero. What it cannot match, meaning a repayment amount that does not equal the order total, a barcode with no order behind it, a refused delivery that came back with the money still owed, becomes an automation exception in Google Sheets with both figures side by side. The finance controller works a short list of real discrepancies instead of a full statement.

Status that customers hear about before they ask

Get Delta Events returns the latest tracking events for every AWB updated in a date interval, which makes a polling loop cheap rather than a per parcel poll storm. The agent runs it every hour, diffs the returned events against what it last recorded, and acts on the changes only. Delivered parcels close the order and stop the loop. Redirected AWBs and returns, both of which Track Shipments surfaces explicitly, get flagged into Slack for customer service with the scan history attached, because those are the two states where a customer is about to be unhappy and nobody has told anyone yet. One detail worth knowing while building this: waybill and tracking date filters use mm-dd-yyyy while order, cash, and invoice filters use yyyy-mm-dd, and each parameter states its own format.

Human-in-Loop Highlight

The gate on Cargus is Manage Order, and specifically the validate side of it. Validating a pickup order does not launch one shipment. It sends the courier pickup request to Cargus for every open waybill at that pick up point. The blast radius is a location and a moment, not a parcel, and the moment matters twice over: Delete Waybill works only on a waybill that has not been scanned yet, so validating starts the clock that closes the correction window on the whole batch at the same time. An AWB created against the wrong recipient locality at 14:40 is fixable at 14:55 and is a customer service ticket at 17:00.

So the agent creates waybills all day and does not validate. Before the cutoff it calls List Orders For Pickup Point for the current, open order at that location and reads back the parcel and envelope counts, the total weight, and the AWB count. Then it asks the warehouse lead in Slack: "Bucuresti depot has 214 open AWBs, 231 parcels, 1,840 kg, cutoff in 20 minutes. 3 AWBs were created after the last pallet was closed. Validate the pickup now?" The lead is standing where the parcels are and knows whether the count on the screen matches the count on the floor. That comparison is the entire value of the pause, and it is not something the API can do, because Cargus knows what was registered and only a person knows what was physically staged.

Two related boundaries are worth building around rather than gating separately. Manage Order also cancels a pickup order, which is the recovery path when a validate went early, but it withdraws the courier request for that location rather than for one shipment, so it is as wide as the action it undoes. And Create Waybill takes the recipient as an address object while the sender is an existing LocationId, meaning a mistake on the sender side is impossible and a mistake on the recipient side is entirely possible. Put the address resolution work, Get Localities and Get Streets, in front of Create Waybill rather than in front of the human. The person should be checking the count, not the spelling.

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

21 actions

Geography

Get Countries Lists the countries supported by the Cargus system with their IDs, names, and country codes. The first step of the address chain, and the source of the CountryId that Get Counties needs.
Get Counties Lists the counties within a country with their IDs, names, and abbreviations. The county ID is required both to look up localities and to address a shipment.
Get Localities Lists the localities within a county with their IDs, postal codes, and network availability. Network availability is the useful field here: it tells you whether Cargus actually serves the locality before a waybill is created.
Get Streets Lists streets from the Cargus nomenclature for a locality. Reach for it when a delivery address needs an exact street match rather than a free text line the courier has to interpret.

Pickup Points

Get Pickup Points Lists the pick up points, meaning sender warehouses, that are active for the authenticated user, with their location IDs, addresses, and contact details. The LocationId returned here is the sender on every waybill.

Rates

Get Price Tables Lists the contracted price tables on the account with their IDs and names. The PriceTableId feeds both price calculation and waybill creation, so a flow that ships under several contracts picks the right one here.
Calculate Shipping Price Calculates the estimated cost of a shipment between two localities, returning base cost, weight cost, insurance, taxes, and grand total. The read behind quoting delivery at checkout or checking a lane before committing to it.

Waybills

Create Waybill Creates an AWB and registers the shipment with Cargus, returning the generated barcode. The sender is an existing pick up point LocationId and the recipient is supplied as an address object. This is where a shipment enters the network.
Get Shipment Details Retrieves full details for one or more waybills by barcode, or every AWB attached to an order by order ID. Supply exactly one of the two, never both.
List Shipments By Date Lists the waybills created in a date range, with pagination. Dates here use the mm-dd-yyyy format this endpoint requires.
Delete Waybill Deletes a waybill that has not yet been scanned. Returns true on success and false when the waybill does not exist or already has a checkpoint, which makes the first scan the hard deadline on any correction.
Print Waybills Generates a printable PDF or HTML document for one or more waybills and uploads it to FlowRunner file storage, returning a downloadable URL. Choose A4 for a sheet or 10x14 for a thermal label.
Get Routing By Address Returns the Cargus routing details, meaning transit priority, transit route, and delivery route codes, for a sender and recipient address pair. The cheapest way to check serviceability before creating anything.

Tracking

Track Shipments Tracks one or more AWBs by barcode, returning current status and the full list of scan events including returns and redirected AWBs. Accepts a list, so a batch of parcels is one call.
Get Delta Events Returns the latest tracking events for every AWB updated within a date interval. The right shape for a scheduled sync loop, since it reports what changed instead of restating what did not.

Pickup Orders

Manage Order Validates or cancels the courier pickup order for a pick up point, returning the order number. Validating sends the pickup request to Cargus for every open waybill at that location, so the scope of one call is a whole dock rather than one parcel.
List Orders For Pickup Point Lists courier pickup orders for a specific pick up point, filtered to current (open) or validated (closed), with pagination. Each order carries parcel and envelope counts, weight, AWB count, and dates. The read to put in front of a person before validating.
List Orders By Date Lists courier pickup orders created in a date range, with pagination and the same counts. Dates here use yyyy-mm-dd.
Get Order By ID Retrieves one courier pickup order by its number, including the pickup window, parcel and AWB counts, weight, and status.

Money

List Cash On Delivery Lists the cash on delivery repayment records collected in the collector account for a date range, with barcode, sender, receiver, repayment amount, and payment order details. The source for reconciling collected cash against the orders that generated it.
List Invoices Lists the Cargus invoices issued in a date range with ID, series, number, value, total, balance, and closed status. Freight spend, matched to a period, without a portal export.

Frequently Asked Questions

What can FlowRunner do with Cargus?

FlowRunner agents can run Get Countries, Get Counties, and Get Localities in Cargus, plus 18 more actions.

Does connecting Cargus to FlowRunner require OAuth?

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

Can Cargus trigger a FlowRunner workflow automatically?

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

Start building with Cargus

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

Start Building Free Talk to us