Did they pay
Support has a customer saying their card was charged twice. Memtro finds them in Chargebee by email, reads their last invoices with paid dates and amounts, and the payment events, so the reply is grounded in the ledger.
Subscriptions, invoices and MRR from Chargebee, and the billing changes you ask for.
Connect Chargebee with your site name and an API key and Memtro reads customers, subscriptions with plan and MRR, invoices by status, plans and prices, and a snapshot of MRR, renewals and cancellations. Every hour the sync writes each new subscription, cancellation and payment into memory. When you ask, and once an administrator has granted each action by name, it can update customers, start, change, pause or cancel subscriptions, charge or record payments, void invoices and refund credit notes. These move real money: a subscription change can charge the customer at once, and a refund cannot be undone.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Chargebee tool, reads what it needs, and answers with the source cited.
These tools change something in Chargebee. 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 Chargebee, choosing the same kinds; the tab shows Chargebee's own steps. Each event can start a job, with the event as its input, and can be remembered where you choose. Chargebee sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce Chargebee 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 subscriptions renew in the next 7 days, and on what plans?
Did Brightwave Ltd pay its October invoice?
Which invoices over £1,000 are still unpaid?
Who cancelled this month, and what reason did they give?
Refund the credit note on Brightwave Ltd's account to their card
Support has a customer saying their card was charged twice. Memtro finds them in Chargebee by email, reads their last invoices with paid dates and amounts, and the payment events, so the reply is grounded in the ledger.
Ellie Moran in finance confirms Brightwave Ltd was charged twice and asks Memtro to refund the credit note raised for the duplicate. Memtro reads the credit note and refunds its full amount to the customer's original card in Chargebee, so the money goes back to Brightwave. The refund cannot be undone.
The teams that lean on Chargebee most, a question each of them asks, and what they connect beside it.
A record in Chargebee 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 Chargebee open Settings → Configure Chargebee → API Keys and Webhooks → API Keys and add a key. A Read-Only Key with Transactional data and Product catalog covers every read, and the actions need a full-access key or a restricted key with write permission. The key is shown once
In Memtro open Connections → Chargebee, enter the Site name (acme for acme.chargebee.com) and the API key, and connect. A test site is usually acme-test and has its own keys
With a read-only key the actions are refused. With a write key Memtro still acts only once an administrator grants an action by name
Ask which subscriptions renew next week
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Chargebee tools are the same everywhere.
Only when you ask, and only what it has been granted: create a customer, or change one's name, contact details, currency, auto-collection or payment terms; start a subscription for a customer on chosen plans and addons (starts billing); change a subscription's plan, addons, quantities or coupons (may invoice a prorated charge); cancel a subscription now, at term end or on a date; pause a subscription, or resume a paused one; reactivate a cancelled subscription; record an offline payment against an invoice; charge the customer's payment method for an unpaid invoice; void an invoice, or write one off as uncollectable; refund a credit note to the customer's payment method, or void a credit note. 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 Chargebee records into memory as entities.
Site name and API key. In Chargebee open Settings → Configure Chargebee → API Keys and Webhooks → API Keys and add a key. A Read-Only Key with Transactional data and Product catalog covers every read, and the actions need a full-access key or a restricted key with write permission. The key is shown once.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Chargebee, choosing the same kinds; the tab shows Chargebee'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