> ## Documentation Index > Fetch the complete documentation index at: https://docs.remark.ai/llms.txt > Use this file to discover all available pages before exploring further. # Recharge > Connect Recharge to Remark so agents can help shoppers manage subscriptions. Remark's Recharge integration lets agents look up subscription details and perform supported subscription actions during shopper conversations. ## What the integration does Once connected, Remark can use Recharge to: * Find a shopper's subscriptions * Find upcoming queued charges * Skip an upcoming charge * Cancel a subscription * Reschedule the next charge date * Change a subscription shipping address * Change a subscription delivery frequency Remark uses Recharge as the system of record. Subscription changes are made in Recharge, and Recharge's rules still determine whether a subscription, charge, address, or schedule change is valid. ## Before you start You need: * Access to **Settings > Integrations** in the Remark dashboard * Your Recharge admin domain * A Recharge API token with read and write access for customers, addresses, subscriptions, and charges Your Recharge admin domain should look like: ```txt theme={null} my-domain.admin.rechargeapps.com ``` You can create a Recharge API token from the Recharge merchant portal under **Tools & apps > API tokens**. Recharge notes that storeowners can view API tokens by default, and storeowners can grant API token page access to other staff accounts. See Recharge's [API token guide](https://docs.getrecharge.com/docs/recharge-api-key) for current Recharge-side steps. ## Connect Recharge 1. Open **Settings > Integrations** in the Remark dashboard. 2. Find **Recharge**. 3. Select **Connect**. 4. Enter your Recharge **Domain**. 5. Enter your Recharge **API token**. 6. Submit the connection form. Remark tests the credentials before saving the integration. If the test fails, the integration is not installed. ## Add Recharge actions to an intent Connecting Recharge makes Recharge actions available to your workspace. To let agents use those actions in conversations, add them to the relevant [intent](/dashboard/intents), such as a subscription management or recurring order playbook. In that intent: 1. Add the Recharge actions the agent should be allowed to use. 2. Write matching criteria for shoppers asking about subscriptions, upcoming charges, skips, cancellations, address changes, or delivery cadence. 3. Tell the agent which shopper details to collect before using Recharge. 4. Test the intent in the [Playground](/dashboard/playground) before enabling it for live conversations. ## Customer verification Recharge actions require the shopper's email address plus either: * Last name * Shipping ZIP or postal code Remark verifies the shopper against Recharge before returning subscription data or making changes. If last name is provided, it must match the Recharge customer record. If ZIP or postal code is provided, it must match a shipping address attached to one of the shopper's Recharge subscriptions. For actions that modify a subscription or charge, Remark also verifies that the subscription ID or charge ID belongs to the verified customer. ## Supported actions | Action | What it does | Required details | | ----------------------------- | --------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | | Get subscription information | Lists the shopper's subscriptions, including product, status, quantity, frequency, next charge date, and price. | Email and last name or ZIP. | | Get upcoming charges | Lists queued upcoming charges for the shopper. | Email and last name or ZIP. | | Skip next charge | Skips the next queued charge, or a specific queued charge if the agent has a charge ID. | Email, last name or ZIP, and optionally a charge ID. | | Cancel subscription | Cancels a subscription in Recharge. | Email, last name or ZIP, subscription ID, and cancellation reason. | | Reschedule next charge | Sets a new next charge date for a subscription. | Email, last name or ZIP, subscription ID, and a future date in `YYYY-MM-DD` format. | | Change subscription address | Creates a new Recharge address and assigns the subscription to it. | Email, last name or ZIP, subscription ID, full shipping address, and phone number. | | Change subscription frequency | Updates the delivery interval for a subscription. | Email, last name or ZIP, subscription ID, interval number, and interval unit: day, week, or month. | Use **Get subscription information** before actions that need a subscription ID. Use **Get upcoming charges** before skipping a specific charge. ## Playground behavior Read-only actions can return Recharge data in the Playground. Actions that change Recharge data are no-ops in the Playground. The Playground shows what would have happened without cancelling, skipping, rescheduling, or updating a live subscription. ## Troubleshooting ### Domain validation fails Confirm that the domain ends in `.admin.rechargeapps.com`. Use the Recharge admin domain, not your public storefront domain. ### API token is rejected Confirm that the token came from **Tools & apps > API tokens** in Recharge and has not been revoked or rotated. If your team recently created a new token, update the integration with the new token. ### Customer cannot be verified Confirm that the shopper email exists in Recharge and that the provided last name or shipping ZIP matches Recharge. For ZIP verification, the shopper must have at least one subscription address in Recharge. ### Subscription action fails Use **Get subscription information** to confirm the subscription ID belongs to the verified customer. For charge skips, use **Get upcoming charges** to confirm the charge is queued and belongs to the shopper. ### Recharge rejects the change Recharge can reject changes because of subscription status, charge timing, address requirements, product rules, or store configuration. Review the subscription directly in Recharge, then retry once the Recharge-side issue is resolved. Need help connecting Recharge or testing subscription actions? Contact `support@remark.ai`.