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

When someone submits your Fluent Forms sign-up form, FlowMattic adds them to Pabbly Subscriptions as a customer and then puts that customer on the subscription plan you pick.

Fluent Forms

Pabbly Subscriptions

Download this workflow Browse more workflows

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

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

What this workflow does

Fluent Forms is a quick way to take sign-ups on your own WordPress site, but the recurring billing still has to be set up in Pabbly Subscriptions. This workflow links the two, so a completed form leads straight to a Pabbly customer with a subscription, and nobody copies details between tabs.

The Fluent Forms trigger fires when a form submission is received. Fluent Forms also stores the entry on your site, and FlowMattic passes its fields, such as names, email and any plan question, to Pabbly.

Two Pabbly Subscriptions steps follow. Create Customer adds the person. Create Subscription then adds a plan, and FlowMattic notes that it works on an existing customer, which here is the one created a moment earlier. Both steps arrive without mapping. After import, map the Fluent Forms fields into the customer step, then point the subscription step at that customer and select the plan.

Each entry runs both steps, including repeat entries from the same email. Submit a test entry and look at Task History to confirm what Pabbly created. Any payment or invoice for the plan is handled by Pabbly according to the plan's own settings.

Online course with a monthly plan

A language tutor takes enrolments on a Fluent Forms page. Each enrolment becomes a Pabbly customer with the monthly lesson subscription attached.

Local delivery subscriptions

A farm shop collects veg box sign-ups with Fluent Forms, including the delivery address, and creates the weekly box subscription in Pabbly for each one.

Support plans for website clients

A web agency puts a care-plan form on its client portal, and each request sets up the client on the matching Pabbly support plan.

How this workflow runs

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

Step 1Trigger
Fluent Forms New Form Submission
Fires when a Fluent Forms form receives a submission. The entry's fields, such as name, email and address, become available to map into both Pabbly Subscriptions steps.
Step 2Action
Pabbly Subscriptions Create Customer
Adds the submitter to Pabbly Subscriptions as a customer. This step has no mapping yet, so connect Pabbly and choose the Fluent Forms fields for the email and the first and last name.
Step 3Action
Pabbly Subscriptions Create Subscription
Puts the customer from step 2 on a subscription plan. After import, map the customer from step 2's result and choose the plan; check a test run to see which customer value Pabbly sends back.

What you need

FlowMatticCore
Fluent Forms 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.

Use Fluent Forms' email field type and make it required, so Pabbly always gets a valid address for the new customer.
Put a Filter between the Fluent Forms trigger and the Create Customer step on the form ID, if other Fluent Forms on your site could also start this workflow.
If the form offers more than one plan, add a Router between Create Customer and Create Subscription, give each route its own Create Subscription step for one plan answer, and remove the original step. Set the route conditions so no entry matches two plans.
This workflow sends nothing to the subscriber, so set up a Fluent Forms email notification on the form if you want them to get a confirmation.

Questions about this workflow

Which Fluent Forms fields does Pabbly Subscriptions need?

At least an email and a name for the customer, which you map in Create Customer. The plan is chosen in the Create Subscription step, or from a form answer if you add a Router between Create Customer and Create Subscription.

Is the subscription linked to the right Pabbly customer?

Yes, once you map it. The Create Subscription step should take the customer from step 2's result, so map that value after import and confirm it with a test entry.

What if the same email fills in the Fluent Forms form again?

A second entry runs both steps again, because the workflow doesn't look up existing Pabbly customers first. Try it with a test email and read the response in Task History.