Sendle

Book carbon-neutral shipping through Sendle. Agents create pickup orders, quote routes before checkout, list available service levels and ETAs, track parcels through transit, and cancel bookings while they are still cancellable.

7 actions Basic auth available

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

A paid order arrives from the storefront with a deliverable address in Australia

Get Quote prices the route from the warehouse suburb to the customer's postcode at the parcel's weight

The agent compares the quote against the shipping charged at checkout and confirms the plan fits the promise

Create Order books the pickup with package details, sender, and receiver, capturing label URLs and the Sendle reference

The tracking URL posts to the order record, and the label queues for the next pickup batch

Orders where the booked price diverges from the quote, or the address failed checks, wait for the operations owner

Track Shipment polls the reference through transit, and delivery events flow to customer notifications

What This Integration Enables

Sendle is carrier-neutral, carbon-neutral shipping for small business in Australia and the United States, built around door-to-door pickup rather than carrier drop-off. That pickup model is what makes automation pay: a booking is not just a label, it is a scheduled collection, and the sooner it is made after payment, the sooner the parcel is on a route. FlowRunner agents quote routes before checkout, list available service levels with ETAs, book orders with full sender and receiver detail, poll tracking through transit, and cancel bookings inside the window where cancellation is still possible. The view this page takes: for a small team, shipping automation is margin protection as much as time savings. The quote-to-booked-price comparison that no human does per order is exactly the check an agent does every time. - Book pickups automatically the moment an order is paid - Quote routes live at checkout so customers see real shipping costs - Present service levels and delivery windows per route - Track parcels through transit and notify on state changes - Cancel bookings programmatically while the cancellable flag still allows it

Without FlowRunner

Booking happens in the dashboard Each order means logging in, retyping addresses, and picking a service by memory

Shipping cost is a guess at checkout The price charged to the customer and the price paid to ship drift apart unnoticed

"Where is my order" means research Tracking status lives behind a reference nobody looks up until a customer asks

With FlowRunner

Paid orders book their own pickup Quote, book, and label happen in sequence within moments of payment

Every route is priced before it is booked Live quotes reconcile against checkout charges, and divergence gets flagged, not absorbed

Transit events reach people first Status changes post to the team and the customer before anyone has to ask

Use Case Scenarios

Payment to pickup without a login

A paid order lands in [Shopify](/integrations/shopify). The agent calls Get Quote for the route and weight, confirms the plan matches what the customer paid for, and books with Create Order: pickup date, package description, both addresses. The response carries the label links, the booked price, and the Sendle reference. The label prints, the tracking URL writes back to the order, and the pickup is on tomorrow's schedule before the packing slip is out of the printer.

Tracking that talks so customers do not have to

After booking, the agent polls Track Shipment on the Sendle reference. When the state moves to In Transit, the customer gets their notification; when it hits Delivered, the order closes and the team's fulfilment channel in [Slack](/integrations/slack) logs the completion. A parcel that sits without a scan event past threshold gets surfaced to operations proactively. The support inbox loses its most common question because the answer now arrives before the question.

Service-level intelligence for the routes you actually ship

Weekly, the agent runs Get Products across the top shipping lanes: each product's plan name, price, and estimated delivery window logs to [Google Sheets](/integrations/google-sheets). Over a quarter, the sheet answers questions that used to be folklore: which lanes Express meaningfully beats Standard on, where ETAs are drifting, and what the real cost curve per weight band looks like. Carrier strategy becomes something the team decides from data it already has.

Human-in-Loop Highlight

Create Order commits money and a schedule in one call: Sendle returns a booked price and puts a driver on route to collect the parcel, and Cancel Order only works while the order's cancellable flag holds, a window that closes at pickup. The failure mode worth engineering against is quiet margin leak: the booked price coming back higher than the quote the customer was charged against, a weight entered in the wrong unit inflating the cost, an address that books cleanly but delivers nowhere. So FlowRunner agents run the reconciliation on every single booking, quote versus booked price versus checkout charge, and clean matches flow straight through at machine speed. A divergence beyond tolerance stops the flow before pickup while Cancel Order is still an option, and the operations owner decides: eat the difference, rebook the service level, or fix the record. The agent's job is to make sure that decision happens inside the cancellation window instead of after the van has come and gone.

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

Orders

Create Order Creates a shipping booking with pickup date, package description and weight, and full sender and receiver details. Returns the order ID, Sendle reference, tracking URL, label download links, and booked price. Country codes are ISO 3166-1 alpha-2.
Get Order Retrieves a created order's full details by order ID: current state, tracking URL, label links, scheduling information including the cancellable flag, and price. The check that precedes any cancellation.
Cancel Order Cancels an order by ID while it is still cancellable, before pickup. Returns the cancelled order with its updated state. The safety valve this page's reconciliation gate depends on.

Tracking

Track Shipment Retrieves tracking status and event history by Sendle reference: overall state, origin and destination, and a chronological list of scan events with descriptions and timestamps.

Quotes

Get Quote Returns a price quote for a route without booking: pickup and delivery suburb, postcode, and country, plus weight, in; available plans with gross, net, and tax pricing and delivery timeframes out. The pre-checkout and pre-booking read.

Products

Get Products Lists shipping products and service levels for a route with plan names, pricing, and estimated delivery windows. The service-comparison read behind checkout options and lane analysis.

Account

Ping Verifies the configured Sendle ID and API key against the ping endpoint, confirming credentials and the sandbox toggle before flows run live.

Frequently Asked Questions

What can FlowRunner do with Sendle?

FlowRunner agents can run Create Order, Get Order, and Cancel Order in Sendle, plus 4 more actions.

Does connecting Sendle to FlowRunner require OAuth?

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

Can Sendle trigger a FlowRunner workflow automatically?

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

Start building with Sendle

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

Start Building Free Talk to us