When a new submission is received in Typeform, check if the email is valid with Mailboxlayer, and create a new customer in Pabbly Subscription
Each new Typeform response has its email checked by Mailboxlayer, and only addresses whose SMTP check passes go on to become a new customer in Pabbly Subscriptions.
Typeform
Mailboxlayer
Filter
Pabbly Subscriptions4 steps Setup ~8 min Used on 3.0k sites Free to import
What this workflow does
A billing system full of mistyped or dead email addresses means invoices and receipts that never arrive. This workflow puts a check in front of Pabbly Subscriptions: a Typeform answer has to pass an email verification before FlowMattic creates a customer from it.
The Typeform trigger starts a run for each new submission. The Mailboxlayer step verifies the email address from the response and returns its results, including an SMTP check that tells you whether the mail server accepts the address.
Next comes a Filter that is already set: it continues only when Mailboxlayer's SMTP check is true. Responses that fail it, or come back without a result, stop there. Those that pass reach Pabbly Subscriptions, where the Create Customer step adds them as a new customer.
The Typeform, Mailboxlayer and Pabbly steps ship without mapping. After import you link your form, map its email answer into Mailboxlayer, and map the name and email into the Pabbly customer. Send a test response with a real address and another with a fake one, then compare both runs in Task History.
Sign-up forms for a paid service
A software company collects account requests in Typeform and only creates Pabbly Subscriptions customers for addresses that a mail server accepts, so billing emails reach a real inbox.
Pre-orders for a subscription box
A subscription box brand takes pre-orders through a Typeform quiz and keeps fake addresses out of Pabbly before the first box ships.
Membership applications
A professional association uses Typeform for applications and sets up the Pabbly customer record only when the applicant's address passes Mailboxlayer's check.
How this workflow runs
What happens at each step once the workflow is on, and what you need before you import it.
Typeform New Form SubmissionStarts the workflow for each new response to your Typeform form. Link the trigger to the form during setup, then submit a test response so its answers are ready to map.
- Mailboxlayer Verify Single Email
Verifies the email from the Typeform response with Mailboxlayer and returns the results, including the SMTP check the Filter reads. Map the email answer into this step after import.
- Filter Continue If Condition Meet
Lets the run continue only when Mailboxlayer's SMTP check is true. Responses with a failed or missing check stop here and no Pabbly customer is created for them.
- Pabbly Subscriptions Create Customer
Creates a new customer in Pabbly Subscriptions for responses that passed the Filter. Connect your Pabbly account and map the name and email from the Typeform answers.
What you need
- FlowMatticCore
- Typeform AccountAccount
- Mailboxlayer 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.
- To review addresses that fail, add a Router between the Mailboxlayer step and the Filter instead: one route keeps the Filter and the Pabbly step, the other logs failed addresses in Google Sheets. Make the conditions exclusive, such as SMTP check true and false.
- Mailboxlayer returns other results besides the SMTP check. Look at a test run in Task History and add a second condition to the existing Filter, between the Mailboxlayer step and the Pabbly step, if you also want to reject other kinds of address.
- Make the email question required in Typeform, so every response gives Mailboxlayer something to check.
Questions about this workflow
What happens to Typeform responses whose email fails Mailboxlayer?
The run stops at the Filter, so Pabbly Subscriptions never sees them. Task History still lists those runs with Mailboxlayer's result, which lets you look the addresses up later.
Do I need a Mailboxlayer account to use this?
Yes. The verification step connects to your Mailboxlayer account and runs a check on each email. Connect it after import before you turn the workflow on.
Does this create a Pabbly subscription too?
No. The Pabbly side stops at a customer record. FlowMattic's Pabbly Subscriptions integration also has a Create Subscription action, which you can add after the Create Customer step and map that new customer into.
What if the email already belongs to a Pabbly customer?
Create Customer runs again for that address. Pabbly decides whether to accept it, so try a known customer's email and read Pabbly's response in Task History.
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