Sendcloud

Automate shipping through Sendcloud. Agents create and cancel parcels, buy carrier labels, look up shipping methods and sender addresses, and monitor return shipments to keep e-commerce fulfilment moving across European carriers.

7 actions Basic auth available

Sendcloud website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

A new order lands in the storefront with a shipping address in Germany

List Shipping Methods returns the carriers serving that destination from the warehouse's sender address

The agent validates the address, matches the parcel weight against each method's supported range, and picks the rate

Create Parcel writes the shipment with Request Label enabled, buying the label in the same call

The tracking number posts to the order record and the fulfilment channel, label URL attached

Orders the validation step could not clear, incomplete addresses, weight outside every method's range, wait for the fulfilment lead's fix

Corrected orders re-enter the flow, and the label prints at the packing station

What This Integration Enables

Sendcloud consolidates European carriers behind one API: one account, many carriers, one integration for the whole label-buying, tracking, and returns loop. This connector puts FlowRunner agents inside that loop. Agents create parcels and buy labels in a single call, choose shipping methods against live carrier options filtered by sender address and destination country, cancel parcels and void labels before the carrier collects, and monitor return shipments with reasons and refund details attached. The operating principle for fulfilment automation: speed wins until the address is wrong. An agent that buys labels in seconds is worth real money in throughput; the same agent shipping to an unverifiable address turns speed into cost. So validation is the heart of the flow, and the exceptions it catches are exactly what the fulfilment team should be looking at. - Turn storefront orders into purchased labels the moment they arrive - Select carrier and rate per shipment from live method, price, and weight-range data - Cancel and void labels automatically when orders change before dispatch - Track returns and their reasons into refunds and quality workflows

Without FlowRunner

Label buying is a screen job Every order means opening the panel, picking a carrier, and clicking through label purchase

Carrier choice is habit The default method ships everything, whether or not a cheaper rate served that lane

Returns surface at month end Return shipments and their reasons pile up unseen until someone runs the report

With FlowRunner

Orders become labeled parcels in seconds The storefront event carries address and weight straight into a purchased label

Every parcel gets the right method Method selection runs against live rates and weight ranges per destination, per shipment

Returns feed the workflow daily Return status and reasons flow into refunds handling and product-quality tracking

Use Case Scenarios

Order to label without a human minute

A [Shopify](/integrations/shopify) order fires. The agent validates the recipient address, selects the method from List Shipping Methods for the destination and weight, and calls Create Parcel with Request Label enabled. The label URL and tracking number come back in the response; the label queues at the packing station and the tracking number registers with [AfterShip](/integrations/aftership) for delivery monitoring. Orders placed at midnight are labeled by 12:01, and the morning shift starts with picking, not clicking.

The refund that beats the courier

A customer cancels twenty minutes after ordering. The refund event triggers the agent, which finds the parcel via List Parcels by order number, checks its status with Get Parcel, and calls Cancel Parcel while the shipment is still uncollected. The label voids where the carrier supports it, the shipping cost comes back, and the warehouse pulls the box from the outbound stack. The race between refund processing and carrier pickup is one an agent wins and a task queue loses.

Returns as a signal, not a surprise

Each morning, the agent pulls List Returns and appends every return's outbound reference, status, reason, and refund details to the returns log in [Google Sheets](/integrations/google-sheets). Reason patterns surface weekly: one SKU driving size-related returns, one carrier lane driving damage claims. The alert posts to [Slack](/integrations/slack) when a pattern crosses threshold. Returns stop being a cost line discovered at month end and become an early-warning feed for product and packaging decisions.

Human-in-Loop Highlight

Create Parcel with Request Label set to true spends money and commits a shipment in the same breath: the label is purchased from the carrier, and once the parcel is collected, no API call brings it back from the wrong address. Cancel Parcel is the safety valve, but it only works on parcels not yet collected, which makes the window between a bad label and an unrecoverable one a matter of hours. So FlowRunner agents buy labels autonomously only for orders that pass full validation: complete address, weight inside the chosen method's supported range, destination the method actually serves. Everything else, the apartment number that is missing, the address the validator cannot resolve, the parcel too heavy for every available method, stops short of the purchase and waits for the fulfilment lead, who fixes the record once instead of paying for the label, the void attempt, and the customer call. The label that ships in seconds and the label that waits for a human are decided by the same rule: whether the money being spent can still reach the right doorstep.

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

7 actions

Parcels

List Parcels Retrieves a paginated list of parcels with address, status, tracking number, and label availability. Filters by order number, tracking number, and cloud shipment ID. The lookup behind cancellations and stuck-shipment sweeps.
Get Parcel Retrieves one parcel's full details by ID: recipient address, current status, carrier, tracking number, shipment method, weight, and label URLs when generated.
Create Parcel Creates a shipment for a recipient address. With Request Label enabled and a shipping method ID supplied, buys the carrier label in the same call; without it, creates a draft announcement. The action this page's human gate conditions.
Cancel Parcel Cancels a parcel by ID, voiding the label where the carrier supports it, for parcels not yet collected or shipped. The response reports the cancellation status.

Shipping Methods

List Shipping Methods Retrieves the shipping methods available to the account, filtered by sender address and destination country, each with ID, name, carrier, price, and supported weight range. The rate-selection read before every label purchase.

Returns

List Returns Retrieves return shipments with the outbound parcel reference, return status, reason, and refund details. Paginated. The feed behind returns and quality workflows.

Sender Addresses

List Sender Addresses Retrieves the configured ship-from addresses with ID, company name, contact details, and postal address. Sender address IDs scope method lookups and shipment configuration.

Frequently Asked Questions

What can FlowRunner do with Sendcloud?

FlowRunner agents can run List Parcels, Get Parcel, and Create Parcel in Sendcloud, plus 4 more actions.

Does connecting Sendcloud to FlowRunner require OAuth?

No. Sendcloud connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.

Can Sendcloud trigger a FlowRunner workflow automatically?

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

Start building with Sendcloud

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

Start Building Free Talk to us