Swell logo

Swell + Memtro

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.

In Memtro

What you can do with Swell in Memtro

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.

What it does

  1. 01See orders by status, customer, date or text, with totals and paid, delivered, refunded and cancelled flags.
  2. 02Read one order's line items, coupon, payment, delivery and refund state.
  3. 03List customers with order counts and lifetime value, and products with price, stock and visibility.
  4. 04Check payments with refundable amounts, subscriptions with their period end, and shipments with tracking.
  5. 05When asked and granted, add an internal note the customer never sees, hold, cancel or ship an order, which may email the customer, or refund a payment.
  6. 06With events on, an order paid, a payment failed or a cart abandoned in Swell can start a job.

Acts when asked

When you ask it to

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.

  1. 01Add an internal note to an order, subscription or invoice
  2. 02Hold, close or mark an order delivered
  3. 03Cancel an order
  4. 04Delete an order
  5. 05Create a shipment for an order
  6. 06Update a shipment's tracking
  7. 07Refund a payment
  8. 08Create a return for an order
  9. 09Cancel a subscription, now or at a scheduled date
  10. 10Reinstate a canceled subscription
  11. 11Pause a subscription
  12. 12Resume a paused subscription
  13. 13Adjust a product's stock
  14. 14Update a product's name, price, SKU or visibility

Events

When it happens

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 webhooks
  • 01Order created
  • 02Order submitted
  • 03Order paid
  • 04Order payment failed
  • 05Order canceled
  • 06Order delivered
  • 07Order fully refunded
  • 08Order updated
  • 09Payment succeeded
  • 10Payment failed
  • 11Refund succeeded
  • 12Refund failed
  • 13Shipment created
  • 14Shipment updated
  • 15Shipment canceled
  • 16Return created
  • 17Return received
  • 18Subscription created
  • 19Subscription paid
  • 20Subscription canceled
  • 21Subscription paused
  • 22Subscription resumed
  • 23Customer account created
  • 24Product stock adjusted
  • 25Cart abandoned
In practice

Ask it like you would a colleague

Once 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.

Swell logoSwell + Memtro
  • 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.

01

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.

02

Failed payment follow-up

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.

Teams

Where it fits

The teams that lean on Swell most, a question each of them asks, and what they connect beside it.

Better together

Works with

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.

Setup

How to connect

Connect withStore ID and Secret key
  1. 1

    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.

  2. 2

    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.

  3. 3

    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.

  4. 4

    Ask which orders are still awaiting payment. Events are turned on from the connection's Events tab.

Also works from

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.

FAQ

Questions

Can Memtro change anything in Swell?+

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.

Who can use a Swell connection?+

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.

Does Memtro store my Swell data?+

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.

How do I connect Swell?+

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.

Can Swell start a job?+

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.

Connect Swell in a few minutes

Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.

Where agents remember your company

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