Docs: System guides

Read Recharge into Maplith

The shop's subscriptions, subscribers, scheduled and processed charges and the orders they create, which tie recurring revenue back to Shopify orders, products and customers.

Recurring orders · Also known as ReCharge, Recharge Subscriptions, Recharge Payments · Checked 2026-10-08

On this page

Best path

Recommended: export files. Recharge's own MCP connector is in an early adopter program and returns only aggregate analytics, not lists of subscriptions or charges. The Export Builder gives the subscription, customer, charge and order files with the Shopify ids that join them to the shop.

Try the paths in this order:

Your agent fetches it, with the access you already gave it. No named connector is confirmed: check the tools your agent already has. The agent checks whether it already has a read-only Recharge tool; if the store uses the Recharge Analytics MCP, the agent can only read totals such as subscriber counts and churn, not rows.
Maplith reads an MCP server you already run. Recharge runs Recharge Analytics MCP. Its address comes from Recharge’s own setup instructions. Documentation: support.getrecharge.com. There is no token to copy: each person signs in with their own Recharge login, and the user needs the Analytics permission in Recharge. Recharge must first enable the store through its early adopter request. Early adopter access only; the connection address comes with Recharge's access instructions. It is read-only and answers aggregate questions (counts, sums, rates, averages) across Recharge's analytics metrics, so it cannot list individual subscribers, subscriptions or charges, and it needs a person's own sign-in. Maplith cannot read this server itself, because it offers tools or a personal sign-in to an agent. Connect it to your agent instead, as the first path.
Export files, the fallback that always works. See the export steps below.

Datasets that make a good map

Dataset	One row is	Key columns	Joins to
Subscriptions	One subscription: the product variant, quantity, schedule, status and next charge date.	subscription id, Recharge customer id, address id, external product id (Shopify product id), external variant id (Shopify variant id), SKU override, status, next charge date	Shopify products and variants by Shopify variant id; Recharge customers by Recharge customer id.
Customers	One subscriber with active subscription count, total orders and payment method status.	Recharge customer id, external customer id (Shopify customer id), customer email (Maplith tries to mask it), number of active subscriptions	Shopify customers by Shopify customer id; email marketing and CRM contacts by customer email.
Charges	One scheduled or processed charge with its line items and status (queued, skipped, error, processed).	charge id, Recharge customer id, external order id (Shopify order id), payment processor transaction id, line item SKU, status, scheduled date	Shopify orders by Shopify order id; Stripe, Braintree or other payment provider charges by transaction id.
Orders	One processed order that a charge created and sent to the shop.	Recharge order id, charge id, external order id (Shopify order id), Recharge customer id, processed date	Shopify orders by Shopify order id; Recharge charges by charge id.

Columns are named, never their values. Maplith tries to mask personal data such as email addresses, but that is best effort: you decide what goes in.

The access to give

Who usually has the rights: The store owner; by default only store owners see the API tokens page, but they can give staff access to it.

Choose the narrowest access that covers the data:

read_subscriptions
read_customers
read_orders
read_products
read_plans
read_store

Where to click:

Log in to the Recharge merchant portal
Go to Tools & apps, then API tokens
Click Create an API Token
Type a name and a contact address in Details
Set each permission to Read access (never Read and Write access)
Click Save

A key or token made here stays in the tool that reads the system, never in a chat. Maplith asks for one only under Data sources › Systems in the app.

Export steps

Format: CSV Date range: Processed charges and orders for the last three months; all subscriptions and customers

In the Recharge merchant portal, go to Tools & apps, then Exports
Click Create export and choose the export type, starting with Subscriptions - All
Tick Include line item columns when you want SKUs and product lines
Enter the address that should receive the file and click Create export
Repeat for Customers, Charges - Processed and Orders - Processed
Open the emailed file when it is ready

How much data

About 100–2,000 charges a month (an estimate). Estimate for a small company, not a measured figure: a small subscription shop has a few hundred to a couple of thousand subscribers billed about once a month.

An agent that reads rows through a chat reads every one of them, about one token per four characters. Above a few thousand rows a dataset, or for a daily refresh, an MCP server or an export is the better path.

Always

Read-only, and never a credential sent to Maplith through a chat.
The same recent period, a few months, from every system.
You decide what goes in.

Sources

Written from public documentation, last checked 2026-10-08:

← All system guides · Markdown version · What your agents do with Recharge