FlowRunner
PricingContact
Theme
Start Free

Sameday

Logistics

Connect AI agents to Sameday, a Romanian courier with an EasyBox locker network. Agents estimate shipping costs, create and track AWBs, look up lockers and cities, and download printable labels so Romanian parcel dispatch runs hands free.

Verified 10 actions Session available
Sameday website ↗ Platform Documentation ↗ Capability data verified 2026-08-10
An order is ready to ship to a Romanian address or to an EasyBox locker
The recipient's county and town are read off the order as the free text a customer typed
Get Counties and Get Cities resolve that text to the numeric geolocation IDs Sameday expects
Estimate Shipping Cost prices the service and returns the delivery time before anything is created
Where locker delivery was chosen, Get Lockers confirms the selected EasyBox is available for that leg
Any town that did not resolve to exactly one city goes to a person with the candidates listed
They pick the right locality, and only then does Create AWB register a shipment that can be deleted only before it enters the delivery flow

What This Integration Enables

Sameday built a locker network and then built a courier business around it, and this connector reflects that order of events. Get Lockers lists the EasyBox lockers available for locker to door and door to locker shipments, each with an ID and address that becomes the last mile destination on a locker AWB. Get Services lists the delivery services actually enabled on your account, which in practice means options like next day, same day, and the locker services, each with the numeric ID that Create AWB and Estimate Shipping Cost require. A Romanian shop deciding between a doorstep and a locker is making a real choice about cost, delivery certainty, and what the customer prefers, and both sides of it are reachable from one flow.

Underneath that, the connector is careful about Romanian geography for a good reason. Get Counties looks up counties by name and returns their numeric IDs, and Get Cities looks up localities within a county by name or postal code and returns theirs. Sameday addresses shipments by those IDs, not by strings, so the resolution step is not a convenience layer. It is the address. Get Pickup Points lists the pickup points configured on the account with their contact persons, and both the pickup point ID and the contact person ID are required when creating an AWB, which keeps the sender side firmly defined.

The shipping loop itself is short and complete. Estimate Shipping Cost returns amount, currency, and delivery time for a shipment without creating one. Create AWB creates the waybill and returns the AWB number and cost, with support for cash on delivery, insured value, and multiple parcels on one shipment. Track AWB returns the full status history with each scan event, its status, timestamp, and location, plus a delivery summary. Delete AWB voids a shipment that has not yet entered the delivery flow. Download AWB PDF writes the printable label into FlowRunner file storage and returns a URL, in A4 for a page or A6 for a thermal printer. There are no triggers, so status arrives by polling Track AWB on a schedule and dispatch starts from an order event elsewhere.

Without FlowRunner

Localities matched by eye A town name from a checkout field is matched to a dropdown entry by whoever is packing
Cost known after the fact The delivery charge shows up on the invoice rather than before the AWB is created
Locker delivery handled manually Someone looks up an EasyBox and pastes its details into the carrier screen

With FlowRunner

Localities resolved to carrier IDs County and city are resolved against Sameday's own data and ambiguity is surfaced, not guessed
Cost estimated before committing The estimate and the delivery time are known while the shipment can still be changed
Locker delivery handled in the flow Available EasyBox lockers are read and the chosen one becomes the last mile on the AWB

Use Case Scenarios

Order to AWB with the address resolved rather than assumed

An order is paid in WooCommerce or Magento. The agent takes the county text from the order and calls Get Counties, then calls Get Cities within that county filtered by the town name or the postal code. Where exactly one city comes back, it has a geolocation ID it can trust. It then calls Estimate Shipping Cost to get the amount and the delivery time, creates the shipment with Create AWB against the configured pickup point and contact person, and calls Download AWB PDF for an A6 label into FlowRunner file storage. The AWB number and the estimated delivery time go back onto the order, so customer service and the customer see the same two facts.

Locker delivery that the customer actually uses

For orders where locker delivery was chosen, the agent calls Get Lockers and offers the customer nearby EasyBox locations over WhatsApp or in the storefront. The chosen locker becomes the last mile on an AWB created against the locker service ID from Get Services. Once Track AWB reports the parcel is in the locker, the flow sends the collection notice and starts a quiet countdown, because a parcel left in a locker eventually returns and the return leg costs more than the reminder. A second nudge goes out before the window closes. None of this needs a person unless the parcel is still sitting there at the end, and then it should reach one.

Cost known before the shipment, not after the invoice

Estimate Shipping Cost prices a shipment without creating it, which makes it useful well before dispatch. The agent runs it at order confirmation for the actual parcel and destination, writes the projected cost into the order record, and logs it to Google Sheets alongside the shipping fee that was charged to the customer. Over a month that becomes a straightforward read on which destinations, weights, and services are being shipped below cost, which is a pricing conversation rather than a logistics one. Orders where the estimate exceeds the collected shipping fee by more than a threshold become an automation exception in Slack before they ship, not after.

Human-in-Loop Highlight

The gate on Sameday is address resolution, and it exists because of a specific and quiet failure mode. Recipient county and city are numeric geolocation IDs, not text. The agent turns a customer's typed town into one of those IDs by calling Get Counties and Get Cities. Romanian locality names repeat across the country, and the same commune name appears in several counties, which is precisely why the API makes you resolve county first. When the lookup returns more than one plausible match and a flow silently takes the first, the result is not an error. It is a valid AWB, a correctly printed label, a real barcode, and a parcel routed to a town several hundred kilometers from the customer. Nothing in the response says anything is wrong.

The recovery window is short and known. Delete AWB only works on a shipment that has not yet entered the delivery flow, so the correction is available between label creation and the courier scan, which on a busy dispatch day is under an hour. That is why the pause belongs before Create AWB rather than after it. The agent resolves what it can and stops on what it cannot: "Order 6031, recipient wrote Bucov. Get Cities returns two matches: Bucov in Prahova and Bucov in Timis. Postal code on the order is blank. Which locality should I address the AWB to?" The person answering can look at the street name, the phone prefix, or simply ask the customer, all of which are outside the API and none of which take long.

That is human-in-the-loop placed on ambiguity rather than on risk appetite, which is the right shape whenever a connector requires an identifier and the source data offers a name. The agent is not asking permission to ship. It is asking the one question it cannot answer, and shipping everything else on its own. Two other boundaries here are worth handling in code rather than in a message. Create AWB supports cash on delivery and insured value, so the collection figure should be derived from the order total rather than from a separately maintained field. And Create AWB and Estimate Shipping Cost both require a pickup point and contact person ID, so an operation running several warehouses should resolve those from Get Pickup Points per shipment instead of pinning one.

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

10 actions

Services and Pickup Points

2
  • Get Services Lists the delivery services enabled on your Sameday account, for example next day, same day, and the locker services, each with the numeric ID that Create AWB and Estimate Shipping Cost need. Results are paginated. The read that tells a flow what it is actually allowed to book.
  • Get Pickup Points Lists the pickup points configured on the account along with each point's contact persons. Both the pickup point ID and the contact person ID are required when creating an AWB, which makes this the sender side of every shipment.

Geography

3
  • Get Counties Looks up Romanian counties by name and returns each county's numeric ID, which Get Cities and the shipment recipient both need. Leave the name empty to list them all.
  • Get Cities Looks up localities within a county and returns each city's numeric ID, filtered by county ID, name, or postal code. This is where an ambiguous town name should be caught, because the ID is what actually addresses the parcel.
  • Get Lockers Lists the Sameday EasyBox lockers available for locker to door and door to locker shipments, each with an ID and address usable as the last mile destination on a locker AWB.

Pricing

1
  • Estimate Shipping Cost Estimates delivery cost and time for a shipment without creating an AWB, taking the pickup point, service, package details, and recipient location. Returns amount, currency, and delivery time. Free to call, which makes it the right thing to run before every commitment and useful for margin analysis long before dispatch.

Shipments

4
  • Create AWB Creates the AWB for a new shipment and returns the AWB number and cost. Requires a pickup point, delivery service, package details, and full recipient information, and supports cash on delivery, insured value, and multiple parcels. The point at which a parcel becomes real.
  • Track AWB Retrieves the full status history of an AWB by tracking number, with each scan event's status, timestamp, and location plus a delivery summary. The source for proactive customer updates and for noticing a parcel that has stalled.
  • Delete AWB Cancels and deletes an AWB by tracking number. Only shipments that have not yet entered the delivery flow can be deleted, so this is a short window rather than a general undo.
  • Download AWB PDF Downloads the printable AWB label as a PDF into FlowRunner file storage and returns a URL. A4 for a standard page, A6 for a thermal label printer.

Frequently Asked Questions

What can FlowRunner do with Sameday?

FlowRunner agents can run Get Services, Get Pickup Points, and Get Counties in Sameday, plus 7 more actions.

Does connecting Sameday to FlowRunner require OAuth?

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

Can Sameday trigger a FlowRunner workflow automatically?

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

Start building with Sameday

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