Validate the email with Email List Validation, then create a FluentCRM contact from a Fluent Form

Each Fluent Forms entry has its email checked by Email List Validation, and only addresses that come back “ok” are saved as FluentCRM contacts, created new or updated by email.

Fluent Forms

Email List Validation

Filter

FluentCRM

Download this workflow Browse more workflows

4 steps 35 downloads Setup ~8 min Used on 2.6k sites Growth Free to import

The Validate the email with Email List Validation, then create a FluentCRM contact from a Fluent Form workflow on the FlowMattic canvas, with 4 steps across Fluent Forms, Email List Validation, Filter, FluentCRM — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Fluent Forms and FluentCRM already sit side by side in WordPress, but a lead form also collects typos and throwaway addresses, and every one of them ends up in your CRM and your email sends. This workflow puts an address check between the two, so FluentCRM receives only the leads whose email passes.

The Fluent Forms trigger starts a run when a new submission is received. The Email List Validation step then checks the value of the form's email field. That mapping is already set, so it works as long as your form's email field uses the name email.

A Filter reads the response and continues only when it is exactly "ok". Submissions with any other response end at the Filter, so they never reach the CRM. The last step creates or updates the person in FluentCRM, matched by email address, with the same email mapped in. Map any other details you collect, such as the name, into that step after import.

Because the Filter accepts one exact value, test with a working address and a made-up one before you go live. Task History shows the response for each submission, so you can see why someone didn't reach FluentCRM.

Clean newsletter sign-ups

A blog's Fluent Forms sign-up box sends only addresses that pass the check into FluentCRM, so the weekly newsletter isn't sent to mistyped or fake emails.

Lead magnet downloads

A consultant offers a checklist through a Fluent Forms form, and only people with a working address are added as contacts for the follow-up emails.

Returning visitors kept up to date

When an existing contact fills in another Fluent Forms form, FluentCRM updates their record by email instead of adding a second contact.

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
Starts the workflow when a new Fluent Forms submission is received. The entry's fields, including the email field, are passed to the next steps.
Step 2Action
Email List Validation Verify Single Email
Checks the address from the form's email field with Email List Validation. This mapping ships set; if your email field has a different name, remap it after import.
Step 3Logic
Filter Continue If Condition Meet
Lets the run continue only when Email List Validation's response is exactly "ok". Every other response stops the run, so that submission never reaches FluentCRM.
Step 4Action
FluentCRM Create or Update Contact
Creates a new contact in FluentCRM, or updates the existing one with the same email address. The email is mapped from the form; add the name and any other fields you collect.

What you need

FlowMatticCore
Fluent Forms PluginPlugin
Email List Validation 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 FluentCRM's Add Tags to Contact action after the Create or Update Contact step, so every lead that passed the check carries a tag you can start a sequence from.
To keep a record of the addresses that failed, add a Google Sheets step between the Email List Validation step and the Filter. Every entry gets logged with its result before the Filter decides.
Make the email field required in Fluent Forms, so no entry reaches the check without an address.
Send a test entry with a mistyped address before going live, so you see the Filter stop it and know the condition matches.

Questions about this workflow

What happens to a Fluent Forms entry whose email fails the check?

The Filter stops that run, so no FluentCRM contact is created or updated. Fluent Forms still stores the entry itself, so you can review what the person sent.

Will an existing FluentCRM contact be duplicated?

No. The Create or Update Contact action matches by email address, so a person already in FluentCRM is updated instead of added again.

My Fluent Forms email field isn't called email. Will this still work?

Not until you remap it. Both the check and the FluentCRM step read the field named email, so pick your own email field in each of those two steps after import.

Can I let Email List Validation results other than "ok" through?

Yes. In the Filter step between Email List Validation and FluentCRM, add an OR condition for each other response you want to accept. Run a few test submissions first so you match the exact text the service sends back.