When new form submission is received in WSForms, create a new subscription in Pabbly Subscriptions

Each WS Form submission creates a customer in Pabbly Subscriptions and then starts a subscription for that customer on the plan you pick, from one form on your WordPress site.

WSForms

Pabbly Subscriptions

Download this workflow Browse more workflows

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

The When new form submission is received in WSForms, create a new subscription in Pabbly Subscriptions workflow on the FlowMattic canvas, with 3 steps across WSForms, Pabbly Subscriptions — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

If you sell a membership, a retainer or a service plan, a WordPress form is often where people sign up. This workflow takes the details from a WS Form submission and sets the person up in Pabbly Subscriptions, so the billing record exists without you copying names and emails across.

The trigger fires when your form receives a new submission. The Pabbly Subscriptions Create Customer step then adds a new customer from the form data. The Create Subscription step follows and starts a subscription for an existing customer, which here is the one step 2 just created.

Neither Pabbly step comes mapped. After import you map the form's name, email and any billing fields into Create Customer. In Create Subscription you map the customer returned by step 2 and choose the plan. Run a test submission and look at what Pabbly returned in Task History before you take real sign-ups.

Both Pabbly steps run for each form entry. If the same person fills in the form twice, Create Customer is asked for a new customer each time, so decide how you want repeat sign-ups handled before going live. Payment collection and plan rules stay in Pabbly Subscriptions.

Membership sign-up form

A club takes membership applications through WS Form, and each applicant becomes a Pabbly customer with a subscription on the membership plan.

Monthly service plans

A web agency offers a care plan on its site; the WS Form order form sets the client up in Pabbly Subscriptions on that plan.

Trial accounts from a lead form

A software company's trial form starts each sign-up on a Pabbly plan that the company has set up with a trial period.

How this workflow runs

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

Step 1Trigger
WSForms New Form Submission
Starts a run each time your WS Form form receives a new submission. The fields people filled in are passed on for the Pabbly customer and subscription.
Step 2Action
Pabbly Subscriptions Create Customer
Adds the person who filled in the WS Form form as a Pabbly Subscriptions customer. Nothing comes mapped: after import, map the submitter's name, email and any billing details from the form.
Step 3Action
Pabbly Subscriptions Create Subscription
Starts a subscription for the customer created in step 2. Map that customer from the previous step and choose the plan; check a test run to confirm Pabbly accepted it.

What you need

FlowMatticCore
WSForms PluginPlugin
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 one form offers several plans, put a Router between the Create Customer step and the Create Subscription step with one route per plan choice. Give each route its own Create Subscription step and use conditions that can't overlap.
Make the email field required in WS Form, so every submission gives Pabbly an address for the customer.
Add an Email step after the subscription step to send the new customer a confirmation with their plan name.

Questions about this workflow

Which Pabbly Subscriptions plan does the WS Form sign-up get?

You select it yourself when setting up Create Subscription. The template doesn't preset a plan, so pick it or map it from a form field.

What if someone who is already a Pabbly customer submits the form?

Create Customer always asks Pabbly for a new customer, and Pabbly decides how to treat a repeat email. Test with an existing customer's address and check Task History.

Does this take a payment from the customer?

The workflow only creates the customer and the subscription. How and when Pabbly Subscriptions collects payment depends on how the plan is set up there.