EasyCargo
LogisticsConnect AI agents to EasyCargo, a 3D truck and container load planning tool. Agents create shipments and cargo spaces, retrieve calculated load plans and item placements, and share public links so load planning results feed dispatch decisions automatically.
What This Integration Enables
EasyCargo does not ship anything. It answers a question every shipper asks and most systems cannot: does this actually fit, and where does each piece go. This connector moves cargo lists into that answer and structured results back out. Create Shipment delivers an order's items, with their dimensions, weights, and stacking and rotation rules, into the account as a shipment. Get Shipment Report returns the calculated plan with total weight, total volume, free distance, axle shift figures, rendered load images, and the grouped list of loaded items. Get Shipment Placements goes further and returns the exact 3D coordinates of every loaded item, position and dimensions per piece, which is enough to build loading instructions for a crew or a custom visualization for a customer.
There is one design fact that has to be stated plainly, because a flow built without it will not work: the load plan calculation cannot be triggered through the API. After Create Shipment lands the data, a person opens the shipment in the EasyCargo application and runs the calculation there. Get Shipment Report and Get Shipment Placements return results only after that has happened. This is not a limitation to route around. It is the shape of the tool, and it makes EasyCargo an unusually honest fit for FlowRunner. The vendor has already drawn the line that Orchestration as a Service argues should exist: the machine prepares and reports, and the judgment call about how a real truck gets packed stays with the planner.
The supporting surface is about reuse. List Cargo Spaces, Get Cargo Space, and Create Cargo Space maintain the containers and trucks the account plans against, each with interior dimensions, maximum load, and measurement system. List Cargo Item Templates, Create Cargo Item Templates, and Delete Cargo Item Template maintain the frequently loaded items so a flow references a template instead of restating a pallet's dimensions on every order. List Shipments and Get Shipment read the book of work, including report and public link URLs where a plan has already been calculated. Measurement system is selectable as Metric or Imperial on the create actions and defaults to Metric. The API is rate limited to 60 requests per hour and 480 per 24 hours, which is generous for planning work and worth knowing before designing a polling loop. There are no triggers: EasyCargo exposes no webhooks or change feed, so a flow polls Get Shipment or Get Shipment Report on a schedule to notice that a calculation has completed.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Proving the order fits before anyone books a truck
A large order is confirmed in Acumatica or NetSuite. The agent builds the cargo list from the order lines, referencing existing entries from List Cargo Item Templates where the product is one the company ships often and creating new ones with Create Cargo Item Templates where it is not. Then it calls Create Shipment against the cargo space the planner expects to use. It posts to Slack that a shipment is ready to calculate, with a direct reference. The planner runs the calculation. On the next poll the agent sees a report exists, pulls Get Shipment Report, and writes total weight, total volume, and free distance back onto the order. If it does not fit, that is now known while there is still time to split the shipment, upgrade the trailer, or move a line to the next load.
Load plan to booked freight without a handoff email
Once the plan is calculated and the space it needs is known, the freight itself can be booked in the same flow. The agent takes the total weight and the grouped item list from Get Shipment Report and uses them to price the move with Cargoboard, which quotes Groupage, LTL, and FTL against the same load. The plan decides the product, the quote decides the price, and the two decisions sit next to each other in one record rather than in two people's inboxes. Get Shipment Placements gives the crew the piece by piece order to load in, which is the difference between a plan that was calculated and a plan that was followed.
Sharing the plan with the party who has to accept it
Partners, customers, and carriers frequently need to see the plan without being licensed for the tool. Create Public Link generates a URL that shows the load plan and its report to anyone who has it. The agent uses that to attach a shareable plan to the shipment confirmation it emails through Gmail, and logs the URL against the shipment in Google Sheets so it can be found again. The link is a convenience, and as the human-in-loop section below argues, it is also the one thing on this connector that reaches outside the account and does not come back.
Human-in-Loop Highlight
There are two human moments on this connector and they are different in kind. The first is structural and unavoidable: the calculation runs in the application, so a planner has to open the shipment and press the button. FlowRunner did not invent that pause and cannot skip it, so the right design is to make the wait productive. The agent stages everything, tells the planner exactly what is waiting and why, and polls for the report rather than asking anyone to come back and say it is ready.
The second is the one that needs a gate. Create Public Link generates a URL that displays the load plan and its report to anybody holding it, with no EasyCargo account required, and there is no action on this connector that revokes one. Look at what the report actually contains: total weight, total volume, axle shift figures, rendered images of the loaded space, and the grouped list of every cargo item on board. For a customer's confidential shipment, that is an itemized description of what they are moving and how much of it, published to an address that cannot be recalled from here. So the agent prepares the link request and stops: "Shipment 4412 for Novanta is calculated: 21,400 kg over 32 items, axle shift within limits. You asked to share the plan with the receiving warehouse. The public link shows the full item list and load images to anyone with the URL and cannot be revoked through the API. Publish?"
That is human-in-the-loop applied to a disclosure rather than to a spend, which is the shape it takes on any connector whose most consequential action is publishing rather than purchasing. Two other actions here are permanent in the ordinary way and deserve the same restraint: Delete Shipment removes a shipment and its calculated plan from the account with no undo, and Delete Cargo Item Template removes a saved item other flows may still reference. Neither reaches outside the account, which is why they are a smaller matter than the link, but a cleanup routine that runs on a schedule against either should be reporting what it intends to remove before it removes it.
Agent Capabilities
13 actionsShipments
4- List Shipments Lists shipments in the connected account, most recent first, with pagination and filters for archive status and creation date. Each entry carries report and public link URLs where a plan has already been calculated, which makes this the read behind noticing that a planner has finished.
- Get Shipment Retrieves a single shipment by identifier with its name, creation date, associated cargo space, and any report or public link URLs generated after calculation.
- Create Shipment Creates a shipment input from a cargo list and an optional cargo space, delivering the data into the account so a planner can open it and calculate the 3D load plan. The calculation itself cannot be started through the API, so this action stages work rather than completing it.
- Delete Shipment Permanently deletes a shipment from the account by identifier. This cannot be undone, and it takes the calculated plan with it.
Reports and Sharing
3- Create Public Link Generates a shareable link so a shipment's load plan and report can be viewed without an EasyCargo account. The plan must already be calculated for the shared report to show results. Nothing on this connector revokes a link once it exists.
- Get Shipment Report Retrieves the calculated load plan report: total weight, total volume, free distance, axle shift figures, rendered load images, and the grouped list of loaded cargo items. Available only after the calculation has been run in the application.
- Get Shipment Placements Retrieves the precise 3D placement coordinates of every loaded item along with the cargo space used, each item carrying its position and dimensions. The source for custom visualizations and for loading instructions a crew can follow in order.
Cargo Spaces
3- List Cargo Spaces Lists the saved cargo spaces, meaning containers and trucks, with interior dimensions, maximum load, and measurement system. The set a shipment can be planned against.
- Get Cargo Space Retrieves one saved cargo space by identifier with its interior width, height, length, maximum load, measurement system, and type.
- Create Cargo Space Creates a saved cargo space in the account from interior dimensions and a maximum load in the chosen measurement system, so it can be reused across shipments instead of described again.
Cargo Item Templates
3- List Cargo Item Templates Lists the reusable cargo item templates on the account, each storing dimensions, weight, and stacking or rotation constraints for a frequently loaded item.
- Create Cargo Item Templates Creates one or more reusable cargo item templates in a single call, each with dimensions, weight, and stacking or rotation constraints in the chosen measurement system. The action that turns a product catalog into a planning catalog.
- Delete Cargo Item Template Permanently deletes a saved cargo item template by identifier. This cannot be undone, and other flows may still reference the template being removed.
Frequently Asked Questions
What can FlowRunner do with EasyCargo?
FlowRunner agents can run List Shipments, Get Shipment, and Create Shipment in EasyCargo, plus 10 more actions.
Does connecting EasyCargo to FlowRunner require OAuth?
No. EasyCargo connects to FlowRunner with session-based authentication, no OAuth flow required.
Can EasyCargo trigger a FlowRunner workflow automatically?
EasyCargo doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with EasyCargo
$100 in credits. No card required. Connect in minutes.