> For the complete documentation index, see [llms.txt](https://docs.eesel.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eesel.ai/integrations/e-commerce/recharge.md). # Recharge Invite your AI teammate into Recharge and it handles the subscription requests your support team gets every day. A customer wants to skip next month, move a delivery to a new address, or cancel. Your agent finds them by email, reads their subscriptions and queued orders, and makes the change you have allowed it to make. You stay in control the whole way. Every write action asks you first until you change that. Reads run on their own. If Recharge is missing from your **Integrations** gallery, message us in the in-app chat or email and we will turn it on. ## Quick start {% stepper %} {% step %} ### Ask your agent to connect Recharge Open the chat in your dashboard and ask it to connect Recharge. It points you at your **Integrations** page and lists what it will be able to do once connected. Open **Integrations > Recharge** in the left sidebar. **Connect** is in the top right. If Recharge is not in the list, it has not been turned on for your workspace yet. Ask us first. {% endstep %} {% step %} ### Enter your Recharge API token **Connect** opens a window from Pipedream, the service that holds the connection. It asks for a Recharge API token. Create one in Recharge first, under **Apps > API tokens**, with read and write access to customers, subscriptions, addresses, charges and orders. Paste it into the Pipedream window. The token goes to Pipedream and never into the chat. A person does this step in the browser. {% endstep %} {% step %} ### Confirm the connection The window confirms the account is connected and returns you to the integration page. **Check it worked.** The integration page header reads **Connected**, and the left sidebar lists Recharge. From a terminal, `eesel status` lists Recharge as connected. {% endstep %} {% step %} ### Try it on a real subscriber Ask your agent in the chat to look up a customer by email and show their subscriptions and queued orders. It reads live from Recharge and shows what it found, with the ids it would act on. Then ask it to skip that customer's next charge. The action asks you first, so the request appears as an approval in the chat and on your **Activity** page. Approve it and the charge is skipped in Recharge. {% endstep %} {% step %} ### Put it to work Recharge has no event that wakes your agent on its own, so it does its Recharge work inside the conversations it already handles. Tell it in its [instructions](/instructions-and-memory/instructions-and-memory.md) how to handle subscription requests, and it uses these actions when a customer asks in your helpdesk, in Slack or on your site. For routine checks, a [schedule](/automations-and-schedules/automations-and-schedules.md) runs the same work on a clock. {% endstep %} {% endstepper %} {% hint style="info" %} **From Claude Code, Cursor or a terminal.** `eesel login`, then `eesel integrations connect recharge` prints the connect link for a person to open, and `eesel status` shows the connection. `eesel integrations recharge actions` lists every action available on your workspace with its approval setting. A held action returns an approval link that a person opens. Full command reference: [The eesel CLI](/apis-and-developer-resources/cli.md). From Claude Code or another MCP client: [Claude Code and MCP clients](/apis-and-developer-resources/claude-code-and-mcp-clients.md). {% endhint %} ## Sources, triggers and actions ### Sources Recharge adds no knowledge source. Your agent reads subscriptions, customers and orders live, at the moment it is asked, and answers from everything else you have connected. ### Triggers Recharge has no triggers. Nothing in Recharge wakes your agent. It acts on Recharge when a customer asks in a connected channel, or on a [schedule](/automations-and-schedules/automations-and-schedules.md). ### Actions Actions are what it can do. Each runs on its own, asks you first, or stays off. Read actions run on their own from the start. Write actions ask you first until you change that. | | Action | What it does | | ----------------- | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | | **Look up** | List customers | Finds a subscriber by email address, with their subscriptions, addresses and payment methods in the same call | | | List orders | Lists a customer's or a subscription's orders, with each order's id, status and scheduled date | | **Subscriptions** | Skip charge | Skips one upcoming charge on a month-to-month plan so the customer is not billed or shipped that cycle. The subscription stays active | | | Cancel subscription | Ends a subscription. The reason your agent records is what your retention team reads later | | | Create subscription | Starts a new subscription for a customer | | | Cancel order | Removes one queued, unshipped order of a prepaid plan | | **Customers** | Update address | Changes the shipping address future charges will use | | | Create customer | Creates a customer record | | | Update customer | Changes a customer's name, email or phone | Three things your agent has been taught about Recharge, because they are easy to get wrong: * **Skip is not cancel.** "Skip my next delivery" is a skipped charge. Your agent never cancels a subscription to approximate a skip, a pause or a date change. * **A prepaid plan is one charge covering several shipments.** Cancelling the subscription leaves the remaining shipments queued, so your agent lists them and cancels each queued order that should not ship. Each queued order has its own id. The Charge ID shown against every queued shipment is the same one for all of them, and cancelling it removes nothing. * **Address changes live on address records, not on the customer.** Updating a customer changes their contact details only. Shipping goes through Update address. ## Troubleshooting
Recharge is not in my Integrations gallery? Message us in the in-app chat or email and we will turn Recharge on for your workspace.
The action says it is waiting? Write actions ask you first on a fresh connection. The request is on your **Activity** page with Approve, Always allow and Deny. Choose **Always allow** to let that action run on its own from then on.
Your agent cannot find the customer? It looks subscribers up by the email address they wrote from. If the customer used a different email in Recharge, give your agent that address.
## FAQ
Can my agent pause a subscription or change its date? Not with these actions. It can skip one charge at a time, cancel, or create a new subscription. For a pause or a date change it tells you what it cannot do and hands the request to your team.
Is cancelling reversible? No. Creating a new subscription afterwards is a different subscription with a new start date and schedule, and possibly a different price. Your agent never presents recreating as undoing. A cancelled queued order cannot be restored either. A skipped charge is the one change you can undo, by unskipping it in Recharge.
How is this billed? Pay-as-you-go. A conversation your agent handles is one task, however many Recharge actions it takes in it. Chats you run yourself from the eesel dashboard are free. See [Pricing](/pricing/overview.md).
## Related pages * [E-commerce Sales Rep](/use-cases/e-commerce-sales-rep.md) for the job your teammate takes on in a store * [Shopify](/integrations/e-commerce/shopify.md) for the store Recharge usually sits beside * [Actions and Approvals](/instructions-and-memory/actions-and-approvals.md) for setting each action to run on its own, ask you first, or stay off * [Set up from Claude Code or the terminal](/getting-started/set-up-from-a-coding-agent.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.eesel.ai/integrations/e-commerce/recharge.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.