When subscription created in Stripe, add user to membership plan in ARmember
When a customer signs up for a new Stripe subscription, FlowMattic creates their WordPress user, or reuses an existing one with that email, and adds them to the ARMember membership plan you pick.
Stripe
WordPress
ARMember3 steps Setup ~5 min Used on 2.7k sites Free to import
What this workflow does
Plenty of membership sites take payment through a Stripe checkout link or pricing table rather than ARMember's own forms. The subscription is real, but nothing on the WordPress side knows about it. This workflow creates the subscriber's account and puts it on your ARMember plan when Stripe records the sign-up.
The Stripe New Subscription trigger starts a run each time a customer is put on a new plan. The WordPress New User step follows and makes the site account. FlowMattic checks the email before creating anyone: when that address is already registered, the step returns the existing user's ID and adds no second account.
The ARMember step adds that user to a membership plan, with the user ID already mapped from New User. You pick the plan after import and map the account details into New User, which ships empty.
Stripe subscription events may identify the buyer only by a customer ID, with no email or name. Check a test subscription to see what arrives. If the email is missing, add Stripe's Find Customer by ID between the trigger and New User and map the email from its result. Task History shows each step's response.
Stripe Payment Links for a members area
A coach sells a monthly plan through a Stripe Payment Link and has each subscriber land on the ARMember plan that opens the coaching library.
Moving billing to Stripe
A site switching from manual invoices to Stripe subscriptions gives each new subscriber the same ARMember plan their predecessors were placed on by hand.
Existing readers who upgrade
A newsletter site's free users subscribe in Stripe with the email they registered with, and their existing login is added to the paid plan.
How this workflow runs
What happens at each step once the workflow is on, and what you need before you import it.
Stripe New SubscriptionFires whenever a customer is signed up for a new Stripe plan. The subscription data is passed on; check a test run, since it may name the customer only by ID.
- WordPress New User
Creates a WordPress account for the subscriber, or returns the existing user's ID when the email is already registered. The step ships unmapped: map the email and name from Stripe or a lookup step.
- ARMember Add User to Membership Plan
Adds the user to an ARMember membership plan, using the user ID from New User that the template already maps. Choose the plan that matches the Stripe price before going live.
What you need
- FlowMatticCore
- Stripe AccountAccount
- ARMember PluginPlugin
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 trigger shows only a customer ID, put Stripe's Find Customer by ID between the New Subscription trigger and New User, then map the email and name from it.
- Put a Filter between the Stripe trigger and New User on the subscription's price or product, so subscriptions for unrelated products don't create site accounts.
- Add an Email step after the ARMember step with your login page link, so new members know where to sign in.
Questions about this workflow
Does the Stripe subscriber need a WordPress account first?
No. New User creates one. If an account with the same email already exists, it reuses that user's ID, so the ARMember plan is added to the login they have.
Why might the WordPress step have no email to work with?
Stripe subscription events can carry only a customer ID. Look at a test run. If the email isn't there, add Find Customer by ID from FlowMattic's Stripe integration before New User.
Can each Stripe price go to its own ARMember plan?
Yes, with a Router between New User and the ARMember step. Give each route a condition on the price that can't match another route, and its own Add User to Membership Plan step.
Is the plan removed when the Stripe subscription is cancelled?
Not by this workflow. It only handles new subscriptions. Removing access needs a separate workflow on Stripe's Subscription Deleted trigger that finds the user by email and then runs ARMember's Cancel User Membership Plan.
More E-Commerce workflows
Other ready-to-import templates from the same category.
Import this workflow into your WordPress site
Download the JSON, import it from the Workflows screen and connect your accounts. Every run stays on your server, with no per-task fees.
30-day money-back guarantee Unlimited workflows and runs Self-hosted