When a new submission is received in Fluent Forms, check if the email is valid with Bounceless, and create a new contact in FluentCRM
Each Fluent Forms submission has its email address checked with Bounceless, then FlowMattic creates or updates the person in FluentCRM, with the verification result ready to store against the contact.
Fluent Forms
Bounceless
FluentCRM3 steps Setup ~5 min Used on 2.1k sites Free to import
What this workflow does
Bad addresses in your CRM cost you twice. Emails to them bounce, and they make your list look bigger than it is. Checking each address as the form comes in tells you which new contacts gave a working email before you start mailing them.
When a visitor submits a Fluent Forms form, FlowMattic passes the email field to Bounceless and its Verify Email action. The response comes back as data you can map. The last step, Create or Update Contact in FluentCRM, adds the person as a contact, or updates them if that email is already in your CRM.
As imported, the result of the check doesn't decide whether the contact is created. Every submission reaches FluentCRM, whatever Bounceless says, because there is no Filter between the two steps. To keep failed addresses out of the CRM, add a Filter on the Bounceless result between the Bounceless step and the FluentCRM step. You can also store the result in a custom field and segment on it later.
Newsletter sign-ups on a WordPress blog
Every sign-up becomes a FluentCRM contact, and the Bounceless result stored with it lets you leave failed addresses out of your next campaign.
Webinar registrations
Registrants go straight into FluentCRM for reminder emails, and the stored Bounceless result flags the addresses that may never receive them.
Lead forms on a service site
Quote requests land in FluentCRM, and sales can see which leads came with an address that passed before spending time on follow-up.
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 SubmissionRuns when a visitor submits your chosen Fluent Forms form. Submit one test entry after import so FlowMattic captures the email and the other fields you will map.
- Bounceless Verify Email
Sends the submitted address to Bounceless to verify it. Map the form's email field and connect your Bounceless account, then check a test run to see which result fields come back.
- FluentCRM Create or Update Contact
Creates a FluentCRM contact from the submission, or updates the existing one when that email is already there. Map the email and name fields, and the Bounceless result if you store it.
What you need
- FlowMatticCore
- Fluent Forms PluginPlugin
- Bounceless 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 Bounceless and FluentCRM that continues only when the result shows a valid address. Submissions that fail then stop before a contact is created.
- Create a custom field in FluentCRM for the verification result and map Bounceless's output into it, so you can build a segment of verified contacts.
- Make the Fluent Forms email field required, so Bounceless always has an address to check.
Questions about this workflow
Are contacts with invalid emails still added to FluentCRM?
Yes, as imported. Every submission reaches FluentCRM whatever the Bounceless result. Add a Filter on the result between the Bounceless step and the FluentCRM step to keep failed addresses out.
Will a Fluent Forms entry from an existing FluentCRM contact create a duplicate?
No. FluentCRM looks the person up by email address and refreshes the contact it finds with the new form data.
Does Bounceless block the Fluent Forms submission?
No. The check runs after the form is sent, so Fluent Forms saves the entry as usual. It only affects what you do in FluentCRM.
Is the Bounceless result saved on the FluentCRM contact?
Not unless you map it. Task History shows what Bounceless returned for each entry. To keep the result on the contact, create a custom field in FluentCRM and map the Bounceless output into it in the last step.
More Forms 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