Unpaid orders this week
Sarah Chen, e-commerce lead at Acme Ltd, asked which orders were still awaiting payment. Memtro listed the unpaid orders with number, total, customer account and date.
Which Swell orders are still awaiting payment, and what is low on stock?
Swell shows what your headless store is doing. You see orders with totals and payment, delivery and refund state, an order's line items, customers with order counts and lifetime value, products with price and stock, payments, subscriptions and shipments. When asked and granted, Memtro can add notes, hold, close, cancel or delete orders, create and update shipments, refund payments, open returns, manage subscriptions, adjust stock and update products. Swell can tell Memtro when an order is paid, a payment fails or a cart is abandoned, and a job can start on it. Customer contact details are never read.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Swell tool, reads what it needs, and answers with the source cited.
These tools change something in Swell. 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, choose the kinds you want, and Memtro registers its address with Swell for you. Each event can start a job, with the event as its input. Swell signs nothing, so the long random address is the only check: treat it as a password.
Events and webhooksOnce Swell 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.
Which orders are still awaiting payment?
Who are our top customers by lifetime value?
Which products are low on stock?
Which subscriptions reach the end of their period this week?
Add a note to order 1042 saying the customer called about delivery.
Sarah Chen, e-commerce lead at Acme Ltd, asked which orders were still awaiting payment. Memtro listed the unpaid orders with number, total, customer account and date.
At Northwind, a job starts when Swell reports an order payment failed. Memtro reads the order and its payments, then, as granted, adds an internal note with the payment status for Maya Okafor, the store manager. The customer never sees it.
The teams that lean on Swell most, a question each of them asks, and what they connect beside it.
A record in Swell 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 Swell dashboard, go to Developer, then API keys. Copy the ID at the top, and reveal or add a secret key just for Memtro.
In Memtro, open Connections → Swell and enter the Store ID and the Secret key. A key starting sk_live_ reads the live store, sk_test_ the test environment.
Swell keys have no scopes, so an administrator grants the actions by name, such as Refund payment, only to the teams that may use them.
Ask which orders are still awaiting payment. Events are turned on from the connection's Events tab.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Swell tools are the same everywhere.
Only when you ask, and only what it has been granted: add an internal note to an order, subscription or invoice; hold, close or mark an order delivered; cancel an order; delete an order; create a shipment for an order; update a shipment's tracking; refund a payment; create a return for an order; cancel a subscription, now or at a scheduled date; reinstate a canceled subscription; pause a subscription; resume a paused subscription; adjust a product's stock; update a product's name, price, SKU or visibility. 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. An hourly sync anchors recently changed Swell records into memory as entities.
Store ID and Secret key. In the Swell dashboard, go to Developer, then API keys. Copy the ID at the top, and reveal or add a secret key just for Memtro.
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Swell for you. 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