Where is my order
A customer emails support asking about order 4821. The agent asks Memtro where it is. Memtro reads the shipment for that order number and answers with the carrier, the parcel's status, its tracking number and link.
Ask Sendcloud where an order's parcel is, what shipped and which returns came back.
Connect Sendcloud with an API integration's public and secret keys, and Memtro reads shipments with carrier, recipient and each parcel's status, tracking number and link, shop orders imported from your stores with status, total and payment status, and customer returns with reason, status, label cost and return fee. It reads on demand and there is no hourly sync. When you ask, and once an administrator has granted the action by name, it can announce shipments and create labels, charged to your carrier contract, create customer returns, update an order, and cancel a shipment, return or pickup. Cancellations cannot be undone.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Sendcloud tool, reads what it needs, and answers with the source cited.
These tools change something in Sendcloud. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Sendcloud, choosing the same kinds; the tab shows Sendcloud's own steps. Each event can start a job, with the event as its input. Sendcloud signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Sendcloud is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Where is the parcel for order 1234?
What shipped yesterday, and with which carrier?
Which returns came in this month, and why?
Ship order 4821 with the standard DPD option
Create a return for Priya Sharma's order and email her the tracking
A customer emails support asking about order 4821. The agent asks Memtro where it is. Memtro reads the shipment for that order number and answers with the carrier, the parcel's status, its tracking number and link.
A parcel to Northwind arrived damaged, and support lead Jonas Weber asks Memtro to ship the replacement order. Memtro finds the imported order, announces the shipment to the carrier with the option he chose, and the label is charged to the carrier contract. The carrier is booked to collect it.
The teams that lean on Sendcloud most, a question each of them asks, and what they connect beside it.
A record in Sendcloud is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In the Sendcloud panel open Integrations → Sendcloud API → Connect, name the integration and save
Copy the public key and the secret key it shows
In Memtro open Connections → Sendcloud, paste the Public key and the Secret key, and connect
Ask where the parcel for an order is
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Sendcloud tools are the same everywhere.
Only when you ask, and only what it has been granted: announce a shipment to a carrier and buy its label (spends money); buy a label for an imported shop order (spends money); cancel an announced shipment; create a customer return, with tracking emails only if asked; request cancellation of a return; update an order's status, notes, tags or shipping address; cancel a booked carrier pickup. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
Public key and Secret key. In the Sendcloud panel open Integrations → Sendcloud API → Connect, name the integration and save.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Sendcloud, choosing the same kinds; the tab shows Sendcloud's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time