When a new submission is received in Fluent Forms, check if the email is valid with Mailboxlayer, and create a new contact in FluentCRM
Each Fluent Forms submission has its email address checked with Mailboxlayer, then the person is created or updated as a FluentCRM contact, with the check result available to map alongside them.
Fluent Forms
Mailboxlayer
FluentCRM3 steps Setup ~5 min Used on 2.9k sites Free to import
What this workflow does
Contact lists built from website forms collect mistyped and made-up addresses over time. Checking each address as it arrives tells you which contacts you can trust before you email them. This workflow adds that check between your form and your CRM.
When someone submits a Fluent Forms form, FlowMattic sends the email address to Mailboxlayer with the Verify Single Email action. Mailboxlayer's response comes back as data you can map, the same way the form answers can.
The final step runs Create or Update Contact in FluentCRM. As imported there is no condition between the check and the CRM, so every submission reaches FluentCRM whatever Mailboxlayer says. To keep failed addresses out, add a Filter before the FluentCRM step. To keep everyone, run a test and see whether the FluentCRM step lets you store part of the Mailboxlayer response on the contact.
None of the steps come pre-mapped. Submit a test entry after import so you can see the form fields and the Mailboxlayer response, then map them.
Newsletter sign-ups with a clean list
A blog's Fluent Forms sign-up box sends addresses through Mailboxlayer, and a Filter you add lets only the ones that pass reach FluentCRM.
Reviewing failed addresses later
A B2B site keeps every enquiry in FluentCRM as imported. Task History shows Mailboxlayer's response for each run, so someone can look up a doubtful lead before calling.
Course waiting lists
An online course collects interest through Fluent Forms. Verified addresses become FluentCRM contacts you can email when enrolment opens.
How this workflow runs
What happens at each step once the workflow is on, and what you need before you import it.
Fluent Forms New Form SubmissionFires on each new Fluent Forms submission. The email field and the other answers are passed on to Mailboxlayer and FluentCRM for mapping.
- Mailboxlayer Verify Single Email
Sends the submitted email address to Mailboxlayer for verification. Connect your Mailboxlayer account and map the form's email field into this step.
- FluentCRM Create or Update Contact
Creates a FluentCRM contact from the submission, or updates the existing one with that email. Map the form's email and name answers into it after a test entry.
What you need
- FlowMatticCore
- Fluent Forms PluginPlugin
- Mailboxlayer AccountAccount
- FluentCRM PluginPlugin
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.
- Add a Filter between Mailboxlayer and FluentCRM that continues only when the response shows the address passed. Use a test submission to see which response field and value to check.
- Use a Router instead of a Filter if passed and failed addresses should be handled differently, for example a FluentCRM step on one route and an email to yourself on the other. Give the routes opposite conditions so they can't both run.
- Send two test entries after import, one with your real address and one made up, so you can compare Mailboxlayer's responses before setting conditions.
Questions about this workflow
Does the template stop invalid emails from reaching FluentCRM?
Not as imported. Mailboxlayer checks the address, but nothing acts on the result, so every submission goes to FluentCRM. Add a Filter before the FluentCRM step to change that.
What happens if the person is already a FluentCRM contact?
The step is Create or Update Contact, so the existing contact is updated instead of a duplicate being created.
Do I need a Mailboxlayer account?
Yes. The check runs through your Mailboxlayer account, which you connect in the second step. Look at your Mailboxlayer plan for how many checks it allows.
Is the Fluent Forms entry still saved if the email fails Mailboxlayer?
Yes. The workflow starts after the form is submitted, so Fluent Forms stores the entry as normal. The check only affects what you do in FluentCRM.
More CRM & Contacts 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