When data received from n8n.io, create a customer in Pabbly Subscriptions
When an n8n.io workflow sends data to FlowMattic, a new customer is created in Pabbly Subscriptions from the details in that request, letting n8n hand billing setup to your WordPress site.
n8n.io
Pabbly Subscriptions2 steps Setup ~5 min Used on 2.5k sites Free to import

What this workflow does
If some of your automations already run in n8n.io, you may still want FlowMattic on your WordPress site to handle parts of the job. This workflow takes customer details that an n8n workflow sends and creates the customer in Pabbly Subscriptions.
The n8n.io Receive Data trigger gives you a URL for this workflow. In n8n, add a request step that sends the customer's details to that URL, then capture a test in FlowMattic so the fields show up for mapping. What arrives is whatever your n8n workflow builds, so include at least the email and name.
The Pabbly Subscriptions Create Customer step then creates a new customer. It ships unmapped: connect your Pabbly Subscriptions account and map the fields from the n8n data into the customer's details.
Each request from n8n starts one run and creates one customer. If n8n sends the same person twice, Pabbly Subscriptions decides how to handle the second request. Task History shows the data n8n sent and Pabbly's response.
CRM deals handed to billing
An n8n workflow watches a CRM for won deals and sends the client's details to FlowMattic, which sets them up as a Pabbly Subscriptions customer.
Sign-ups from a custom app
A SaaS team's n8n flow collects sign-ups from their own app and forwards each one, so billing records exist before the first invoice.
Splitting work between n8n and WordPress
An agency keeps data clean-up in n8n and lets FlowMattic on the client's WordPress site handle the Pabbly Subscriptions step.
How this workflow runs
What happens at each step once the workflow is on, and what you need before you import it.
n8n.io Receive DataReceives data sent from your n8n.io workflow to this workflow's URL. Send a test request from n8n after import so the incoming fields, such as email and name, are ready to map.
Pabbly Subscriptions Create CustomerAdds a customer to Pabbly Subscriptions using the details n8n sent. The step is unmapped: connect your account and map the email, name and other customer fields from the incoming data.
What you need
- FlowMatticCore
- n8n.io 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.
- Send the data from n8n as clear, flat fields such as email, first_name and last_name, so they are easy to pick when you map the Pabbly Subscriptions step.
- Put a Filter between the n8n.io trigger and the Create Customer step that continues only when the email is not empty, so incomplete requests don't reach Pabbly Subscriptions.
- To start a plan right away, add Pabbly Subscriptions' Create Subscription action after the Create Customer step and map the new customer from its result.
Questions about this workflow
How does n8n.io send data to this FlowMattic workflow?
Through the URL the Receive Data trigger gives you. Add a request step in your n8n workflow that posts the customer details to it, then capture the test in FlowMattic.
Which customer details reach Pabbly Subscriptions?
Only the ones n8n sends and you map. The template leaves the Create Customer step empty, so you choose which incoming fields fill which customer details.
Do I need an n8n.io account for this workflow?
Yes. The data has to come from an n8n workflow you build. FlowMattic only receives it and passes it to Pabbly Subscriptions.
More Payments 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