When a new subscription is created in Stripe, create a new subscription in Pabbly Subscriptions

Each time a customer signs up for a new plan in Stripe, FlowMattic creates that customer in Pabbly Subscriptions and then opens a matching subscription for them there.

Stripe

Pabbly Subscriptions

Download this workflow Browse more workflows

3 steps Setup ~5 min Used on 1.1k sites Free to import

What this workflow does

Some businesses take payments in Stripe but run reporting, invoices or customer portals from Pabbly Subscription Billing. Keeping the two in step by hand means re-entering every sign-up. This workflow copies each new Stripe subscription across, so the customer and their plan also exist in Pabbly.

A run begins when the Stripe New Subscription trigger reports a customer signing up for a plan. Stripe's subscription data may identify the buyer only by a customer ID, without an email or name, so look at a test run before you map anything.

The first Pabbly Subscriptions step creates a customer. The second creates a subscription for that customer, so map the customer returned by step 2 and the Pabbly plan that matches the Stripe plan. Both steps ship unmapped: after import you connect Pabbly and fill them from the Stripe data.

Plans have to line up. If you sell several Stripe plans, you need a matching plan in Pabbly for each one, and a way to pick the right one per run. Before going live, test with a real sign-up and check in Pabbly how the new subscription is set up, since the payment already happened in Stripe. Task History keeps the Stripe data and both Pabbly responses for every run.

Stripe checkout, Pabbly customer portal

A SaaS founder takes card payments with Stripe Checkout but gives customers Pabbly's portal to see their plan, so every Stripe sign-up must exist in Pabbly.

Moving billing tools without a gap

A membership business migrating to Pabbly keeps Stripe sign-ups flowing into Pabbly during the switch, so no new subscriber is missed.

One place for subscription reports

A small agency sells retainers through Stripe and reviews monthly subscriber counts in Pabbly alongside the plans it sells there directly.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
Stripe New Subscription
Starts each time Stripe signs a customer up to a new plan. The subscription details pass on; if the customer appears only as a Stripe ID, add a lookup before mapping the email (see tips).
Step 2Action
Pabbly Subscriptions Create Customer
Creates the customer in Pabbly Subscriptions. The step ships unmapped, so after import map the customer's email and name, from the trigger or from a Stripe customer lookup.
Step 3Action
Pabbly Subscriptions Create Subscription
Creates a subscription in Pabbly for the customer the previous step made. Map that customer from step 2's result and choose the Pabbly plan that matches the Stripe plan; a test run shows the values to use.

What you need

FlowMatticCore
Stripe AccountAccount
Pabbly Subscriptions AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

If the Stripe trigger data has no customer email, put Stripe's Find Customer by ID action between the Stripe trigger and the Create Customer step, and map the email and name from its result.
With several Stripe plans, put a Router between the Create Customer step and the Create Subscription step, with one route per Stripe plan ID set to an exact match. Give each route its own Create Subscription step for the matching Pabbly plan and remove the original one.
Create the matching plans in Pabbly before importing, using names that make the Stripe-to-Pabbly pairing obvious.

Questions about this workflow

Will Pabbly charge the customer again after Stripe?

The workflow only creates the customer and the subscription records. How Pabbly treats a new subscription depends on your plan and account setup there, so test with a real sign-up and check the subscription in Pabbly before you rely on it.

Where does the customer's email come from on a Stripe subscription?

The New Subscription event may carry only the Stripe customer ID. Check a test run; if no email is there, add Stripe's Find Customer by ID step after the trigger and map the email from it.

What if the Stripe customer already exists in Pabbly?

Create Customer makes a new customer, and Pabbly may return an error or a duplicate for an email it already holds. Test with a known customer and look at the response in Task History.

Do canceled Stripe subscriptions get canceled in Pabbly too?

No. Only sign-ups start this workflow. A separate workflow on Stripe's Subscription Deleted trigger could use Pabbly's Cancel Subscription action, but it would need a way to find the matching Pabbly subscription first.