We’re looking for insight from companies that manage multiple subscriptions per customer in Stripe.
In our case, each account has three separate subscriptions:
Base plan
Email plan
Teams plan
Each of these also has multiple plan levels, and every customer technically has all three subscriptions (either free or paid).
Right now, the Stripe integration appears to pull only one random subscription, which makes it difficult to reliably identify a customer’s actual plan levels across all products.
How are you configuring your Stripe integration to correctly identify all subscription plans for a customer, rather than just one? Are you using specific metadata, workarounds, or a particular integration setup to handle this?
For context, we are looking to use Procedures to perform account actions inside Stripe, but need to be able to accurately make changes to all plans.
Best answer by Christopher Boerger
Hi @Katee Saffer, Haven't tested this exact scenario myself, but a few things worth exploring:
For the "pulls one random subscription" issue:
The native Stripe app does seem limited here. Have you tried the Stripe Data Connector template ("Get subscription details")? The docs say it pulls "all subscription information" — curious if that includes multiple subs or just details about one.
If that doesn't work, a custom Data connector calling Stripe's List Subscriptions endpoint directly (/v1/customers/{customer_id}/subscriptions) would return all subscriptions. You'd have full control over the response mapping.
Hi @Katee Saffer, Haven't tested this exact scenario myself, but a few things worth exploring:
For the "pulls one random subscription" issue:
The native Stripe app does seem limited here. Have you tried the Stripe Data Connector template ("Get subscription details")? The docs say it pulls "all subscription information" — curious if that includes multiple subs or just details about one.
If that doesn't work, a custom Data connector calling Stripe's List Subscriptions endpoint directly (/v1/customers/{customer_id}/subscriptions) would return all subscriptions. You'd have full control over the response mapping.
The Get Charges data connector ended up doing wonders for us, @Christopher Boerger ! Thank you so much for the suggestion!
Originally when I had tested this option, I was pretty new to using data connectors so it seemed like it wasn’t a good match for what we needed. But after you suggested it again, I gave it another go. With the help of ChatGPT, I did some significant data transformation and now Fin was able to turn the data into something meaningful for our users.
While I haven’t turned these into actions just yet, we’ve been able to pull in the data for our users in a read-only way. I’m going to continue down this path and see what actions we can automate next. 👍
