Connect Recharge to Parabola

Pull Recharge subscriptions, charges, customers, and orders into Parabola to automate churn analysis, revenue reconciliation, and subscription reporting.

Recharge is a subscription management platform that powers recurring billing for Shopify, BigCommerce, and other e-commerce stores. Connecting Recharge to Parabola lets subscription, finance, and CX teams pull customers, subscriptions, charges, and orders into the same flows used for churn analysis, revenue reconciliation, and lifecycle reporting, without manual exports or engineering work.

Pull from Recharge

The Pull from Recharge step pulls live data from your Recharge merchant portal via the Recharge API. You select a resource (Customers, Subscriptions, Charges, Orders, etc.) and Parabola brings the records into your flow for cleaning, joining, and routing.

How to authenticate

Recharge uses API token authentication. See the Recharge API token docs for full details.

Generate your API token in Recharge

1. Log in to your Recharge merchant portal.

2. In the left navigation, click Tools & apps.

3. Click API tokens.

4. Click Create an API token.

5. Fill in the required fields:

   • Name — give your token a descriptive label, like “Parabola Integration.”
   • Contact email — the address that should receive notifications about this token.
6. Set the permission scopes. Configure each resource you plan to pull with at least Read access. Parabola only needs Read for reporting and analysis. Add Write scopes only if you plan to push data back via the Send to an API step.

7. Click Save to generate your token.

8. Copy the token immediately and store it somewhere secure. You won’t be able to view it again.

Only store owners can create and view API tokens by default. Store owners can grant additional staff access to the API Tokens page if needed.

Connect in Parabola

1. Add a Pull from Recharge step to your flow.

2. Click Authorize in the step settings.

3. Paste your Recharge API token when prompted.

Parabola stores the token securely and uses it to authenticate each request to Recharge.

Available data

• Customers — customer records including name, email, Shopify customer ID, account creation date, and lifetime stats.
• Subscriptions — active, cancelled, and expired subscriptions with billing frequency, next charge date, order interval, customer association, product variant, and status.
• Orders — subscription orders with status (success, queued, error, cancelled), processing details, scheduled date, and subscription ID.
• Charges — payment transactions with amount, currency, status (success, error, refunded, pending), and links to orders and subscriptions.
• Products — product catalog with title, external product ID (such as a Shopify product ID), and creation timestamp.
• Plans — subscription plans and pricing including billing interval, plan name, and price points.
• Addresses — customer shipping addresses with full location details, country, and customer ID.
• Payment methods — payment method records linked to customers, with type and creation date.

For resources not exposed by the native step (discounts, bundles, retention strategies, webhooks), use Pull from an API against the Recharge API reference with the same token.

Common use cases

• Track churn and at-risk subscribers: Pull Subscriptions filtered by status (active, cancelled, expired), join to Charges for failed payments, and post a weekly cohort retention report into Google Drive or Slack.
• Reconcile subscription revenue: Join Recharge Charges with Shopify orders and Stripe payouts, then post the cleaned revenue summary to NetSuite or QuickBooks Online for a clean monthly close.
• Recover failed payments: Filter Charges to error or pending status, join to Customers for contact info, and trigger a personalized email through SendGrid, Klaviyo, or a Slack alert to your CX team.
• Forecast revenue and demand: Pull Subscriptions with next charge dates, group by plan and billing interval, and project upcoming MRR plus shipping volume so finance and ops can plan inventory and cash flow.
• Sync subscriber data to marketing: Push active Recharge subscribers into Klaviyo, Mailchimp, HubSpot, or Salesforce so retention and winback campaigns target the right segments.
• Compare plan and SKU performance: Pull Plans, Subscriptions, and Products to see retention, ARPU, and lifetime value by billing interval or product, then drop the result into a dashboard in Looker or Metabase via your warehouse.

Tips for using Parabola with Recharge

• Filter by updated_at where possible. Pulling “all subscriptions ever” gets slow on stores with millions of records. Pull subscriptions updated in the last 7 days and let downstream logic handle aggregation.
• Join Charges with Subscriptions on subscription_id. Most reporting questions (churn, recovery, MRR) need both endpoints joined together, since Charges hold the money and Subscriptions hold the lifecycle state.
• Watch for cancelled subscriptions with future charges. Recharge can hold queued charges on subscriptions that were cancelled. Filter on subscription status before forecasting revenue.
• Pair Recharge with Shopify. Recharge’s external_product_id and external_customer_id map to Shopify IDs. Join the two to combine subscription and one-time order revenue in a single report.
• Match cadence to use case. Hourly for failed-payment recovery, daily for revenue reconciliation, weekly for cohort and retention analysis.
• Use Pull from an API for unsupported resources. For discounts, bundles, retention plans, or webhooks, hit the Recharge API directly with the same token.

FAQ

Can I push data back into Recharge?

The native step is read-only. To update subscriptions, customers, or addresses (for example, swapping a product or changing a billing date), use a Send to an API step pointed at the relevant Recharge API endpoint with a token that has Write scopes.

Does Parabola support Recharge webhooks?

The native step is API-pull only. For event-driven flows (subscription created, charge failed, address updated), point a Recharge webhook at Parabola’s webhook trigger on a separate flow.

How do I pull historical subscription changes?

Recharge’s API exposes a subscription’s current state, not its full audit history. For historical change tracking, snapshot Subscriptions on a daily schedule into Snowflake, BigQuery, or Redshift so you can diff over time.

Which Recharge plan do I need?

Any Recharge plan with API access works. If your token can’t see a resource you expect, check the scopes on the token and confirm your plan tier in the Recharge admin.

Can I combine multiple Recharge stores in one flow?

Yes. Add multiple Pull from Recharge steps and authorize each one with a different store’s API token, then union the results downstream.

---

With Recharge and Parabola connected, the spreadsheets your subscription team rebuilds every Monday — churn cohorts, failed-payment recovery lists, revenue reconciliation — run on a schedule, with clean data flowing into the tools where finance, CX, and marketing actually work.