When new form submission is received in Elementor Pro Form, create a new subscription in Pabbly Subscriptions

Each Elementor Pro form submission creates a customer in Pabbly Subscriptions and then starts a subscription for that customer on the plan you choose after import.

Elementor

Pabbly Subscriptions

Download this workflow Browse more workflows

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

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

What this workflow does

If people sign up for a membership, a service package or a recurring box through an Elementor form, someone usually has to rebuild each sign-up in Pabbly Subscriptions by hand. This workflow does that from the form itself: the person becomes a Pabbly customer and gets a subscription in the same run.

The Elementor trigger starts when a form built with Elementor Pro's Form widget is submitted. The answers, such as name, email and any plan choice you ask for, are passed to the two Pabbly steps.

The first Pabbly Subscriptions step creates the customer from the form's email and name. The second step creates a subscription, which FlowMattic describes as being for an existing customer, so it relies on the customer the first step just made. Neither step is mapped as imported: you map the form fields into Create Customer, then map the customer from that step's result and choose the plan in Create Subscription.

Every submission runs both steps, so test with your own entry first. Task History shows what Pabbly returned for the customer and the subscription. How Pabbly collects payment for the plan depends on the plan and your Pabbly setup, not on this workflow.

Membership sign-up on a landing page

A fitness studio's Elementor landing page has a join form. Each sign-up becomes a Pabbly customer on the monthly membership plan.

Service retainers from an enquiry form

A bookkeeping firm lets clients pick a monthly package on an Elementor form, then uses the answer to start the matching Pabbly subscription.

Trial accounts for a software tool

A small SaaS team collects trial sign-ups through an Elementor form and puts each person on the Pabbly plan set up for trials.

How this workflow runs

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

Step 1Trigger
Elementor New Form Submission
Starts when an Elementor Pro form is submitted. The submitted fields, such as the person's name and email, are passed on for both Pabbly Subscriptions steps to use.
Step 2Action
Pabbly Subscriptions Create Customer
Creates the person as a Pabbly Subscriptions customer. As imported it has no mapping: connect Pabbly and map the email, first name and last name from the Elementor form.
Step 3Action
Pabbly Subscriptions Create Subscription
Starts a subscription for the customer made in step 2. Map that customer from step 2's result and pick the plan. A test run shows which identifier Pabbly returns for the new customer.

What you need

FlowMatticCore
Elementor 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 your Elementor form lets people choose between plans, add a Router between the Create Customer step and the Create Subscription step, with one route per plan answer, each with its own Create Subscription step, and conditions that can't both match. Delete the original step.
Mark the email field as required in the Elementor form, so every submission reaches Pabbly with an address for the customer.
Put a Filter between the Elementor trigger and Create Customer that checks the form name or ID, if more than one Elementor form on your site could start this workflow.
Send yourself a test submission and confirm in Pabbly Subscriptions that both the customer and the subscription appear before sharing the form.

Questions about this workflow

Does the Elementor form need Elementor Pro?

Yes. The Form widget that sends submissions to FlowMattic is part of Elementor Pro, and this template's trigger listens for those submissions.

How does Create Subscription know which Pabbly customer to use?

You map it from the Create Customer step's result after import. Run a test submission to see the customer details Pabbly returns, then select the right one in Create Subscription.

What if someone submits the Elementor form twice?

Each submission runs both steps again. The workflow doesn't check Pabbly for an existing customer first, so test with a repeat email and read Task History to see what Pabbly does.

Does this collect payment from the subscriber?

The workflow only creates the customer and subscription records. Payment collection follows your Pabbly Subscriptions plan and settings, so check them in Pabbly before you go live.