HomeRunner
LogisticsConnect AI agents to HomeRunner, a Nordic multi-carrier shipping platform. Agents look up carrier products, find nearby servicepoints, create shipments with labels, and track parcels so Nordic and international deliveries get booked from one flow.
What This Integration Enables
Nordic delivery is parcel shop delivery for a large share of orders, and HomeRunner is built around that reality rather than treating it as an option bolted onto home delivery. Find Servicepoints takes a destination country, postal code, and optionally a city and street, and returns the closest carrier parcel shops with their ID, name, distance, address, coordinates, and opening hours. Get Servicepoint reads back a single one by ID. Those two actions carry more weight on this connector than they would on a carrier whose default is a doorstep, because the pickup point is a place a customer physically walks to, and choosing it well is a customer experience decision that happens to be expressed as an API parameter.
Get Products is the other action worth understanding early. It lists the carriers and products available when sending from a given origin country, each with size and weight limits, prices, and the additional services it supports, and it returns the carrier code, product code, and service code that Create Shipment expects. Those values are dynamic per origin country, so a flow that ships from Denmark and Sweden should read them per origin rather than hard coding a product that exists in one country and not the other. Create Shipment then books the label with the selected carrier, taking full sender and receiver contact details, package dimensions, and weight in grams, and returns the shipment with its package number and links to the label and tracking.
After booking the surface stays deliberately small. Get Shipment reads a shipment back by package number with sender and receiver details, dimensions, carrier and product, price, and label and tracking links. Get Shipment Label retrieves the label itself in the format requested at creation, with the default LabelPrint returning a printable PDF. Track Shipment returns the ordered tracking events with timestamps, status events, and details. Authentication is HTTP Basic using the account email and API token together. The servicepoint lookups, including the picker on Create Shipment, support the GLS, DAO, and PostNord carriers. There are no triggers, so a flow starts from an order event in the store or from a schedule.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Letting the customer pick the shop, with the facts in front of them
An order comes in from Shopify or WooCommerce with parcel shop delivery selected. The agent calls Find Servicepoints for the destination postal code and the relevant carrier, and gets back the nearby shops with distance and opening hours attached. Rather than picking the nearest, it presents the shortlist to the customer with the hours shown, because a shop 400 meters away that closes at 16:00 is worse for someone who works until 17:30 than one a kilometer away that opens late. The customer's choice becomes the Servicepoint ID on Create Shipment. Parcels sent to a point the customer chose get collected; parcels sent to a point an algorithm chose come back, and a returned parcel costs two legs of freight plus a refund conversation.
Choosing carrier and product per origin instead of per habit
A merchant shipping from more than one Nordic country cannot assume the same product exists everywhere. Before booking, the agent calls Get Products for the actual origin country and reads back the carriers, products, size and weight limits, and prices available from there. It filters to the products whose limits the parcel actually fits inside, applies the business rules about which carriers are approved for which destination, and picks from what is left. The chosen carrier, product, and service codes go into Create Shipment. When nothing fits, meaning an oversized item or a destination with no approved product, the order becomes an automation exception in Slack with the limits that excluded each option, which is a far more useful message than a rejected booking.
Delivery status the customer hears about first
Track Shipment returns an ordered list of tracking events for a package number. On a schedule the agent walks the open shipments, diffs the latest event against the last one it recorded, and acts on changes. Arrival at the parcel shop triggers a message through Gmail telling the customer which shop, at which address, with which opening hours, taken from the Get Servicepoint record rather than from a generic template. A parcel sitting at the shop uncollected for several days triggers a reminder, because unclaimed parcels return automatically and nobody wins when that happens. Delivered shipments close the loop and the order is updated in Airtable or the store.
Human-in-Loop Highlight
The gate on HomeRunner is about where a person has to walk. Create Shipment accepts a Servicepoint ID only for parcel shop products, and leaving it empty means home delivery, which makes the last mile a function of two fields agreeing with each other. Get them wrong in one direction and a customer who asked for a parcel shop gets a delivery attempt at an empty apartment. Get them wrong in the other and a customer expecting a doorstep delivery gets a slip telling them to collect from a shop across town. Neither produces an API error. Both produce a support ticket, and often a return, because a parcel at the wrong shop is a parcel nobody collects.
So the agent gathers the evidence and puts the choice where it belongs. It runs Find Servicepoints for the destination and reads back distance, address, and opening hours for each candidate, then routes the decision to the customer at checkout where that is possible. Where it is not, meaning a phone order, a corrected address, or a reshipment after a failed delivery, it asks the person who owns the customer relationship in Slack: "Order 2287, Aarhus C. Customer asked for parcel shop. Closest is Netto Frederiksgade at 380 m, open until 16:00 weekdays and closed Sundays. Next is Shell Randersvej at 1.2 km, open until 22:00 daily. Which point should I book?" The answer takes seconds and the person answering knows things the distance field does not.
That is human-in-the-loop on a last mile decision, which is where it earns the most on a shipping connector: the agent has already done the lookup, the filtering, and the formatting, and the only thing left is the judgment about a specific person's day. One design note in the same spirit. Get Products returns dynamic values per origin country, so a product code cached from one country's response and reused for another is a booking that either fails or silently books something different. Read products per origin, and treat an empty result for a destination as an exception a person sees rather than a fallback the flow picks quietly.
Agent Capabilities
7 actionsServicepoints
2- Find Servicepoints Finds the closest carrier parcel shops and pickup points for a delivery address, taking the carrier plus destination country and postal code, with city and street improving accuracy. Returns each point with its ID, name, distance, address, coordinates, and opening hours. Supported for GLS, DAO, and PostNord.
- Get Servicepoint Retrieves a single servicepoint by ID with its name, address, coordinates, and opening hours. The read behind telling a customer exactly where and when to collect, rather than repeating a shop name.
Products
1- Get Products Lists the shipping carriers and products available from a given origin country, each with its carrier, title, size and weight limits, prices, and supported additional services. Returns the carrier, product, and service codes that Create Shipment needs. Values are dynamic per origin country, so read them per origin.
Shipments
3- Create Shipment Creates a shipment and books a label with the selected carrier, taking sender and receiver contact details, package dimensions, weight, and the carrier, product, and service codes from Get Products. Include a Servicepoint ID for parcel shop delivery and leave it empty for home delivery. Returns the shipment with its package number and links to the label and tracking.
- Get Shipment Retrieves a previously created shipment by package number with sender and receiver details, package dimensions, carrier and product, price, and label and tracking links. The read to confirm a booking or to recover a label URL later.
- Get Shipment Label Retrieves the shipping label for a shipment by package number, in the format requested when the shipment was created. The default LabelPrint returns a printable PDF for the packing bench.
Tracking
1- Track Shipment Retrieves the tracking history for a shipment by package number, returning the carrier and an ordered list of events with timestamps, status events, and details. The source for proactive delivery updates and for noticing a parcel sitting uncollected at a shop.
Frequently Asked Questions
What can FlowRunner do with HomeRunner?
FlowRunner agents can run Find Servicepoints, Get Servicepoint, and Get Products in HomeRunner, plus 4 more actions.
Does connecting HomeRunner to FlowRunner require OAuth?
No. HomeRunner connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.
Can HomeRunner trigger a FlowRunner workflow automatically?
HomeRunner doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with HomeRunner
$100 in credits. No card required. Connect in minutes.