When new form submission is received in Beaver Builder, add a new contact in FluentCRM

Each Beaver Builder contact form submission is sent to FluentCRM, which creates a contact from the email address or updates the contact that already has it.

Beaver Builder Forms

FluentCRM

Download this workflow Browse more workflows

2 steps Setup ~5 min Used on 2.3k sites Free to import

The When new form submission is received in Beaver Builder, add a new contact in FluentCRM workflow on the FlowMattic canvas, with 2 steps across Beaver Builder Forms, FluentCRM — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

A Beaver Builder contact form emails you the message, but the sender's details stay in your inbox. If you run your email marketing in FluentCRM, you want those people in the CRM where you can tag them, segment them and follow up. This workflow moves every contact form submission there without copying by hand.

The Beaver Builder Forms trigger fires when a new contact form submission is received on your site. FlowMattic passes the submitted values, such as the name, email and message, to FluentCRM.

The FluentCRM step creates a new contact or, if one already uses that email address, updates it. That means a visitor who writes in twice keeps one contact record. The step ships unmapped: after import, map the form's email field and any name or phone values into the contact, then run a test to see what FluentCRM saved.

Both plugins run on your own WordPress site, so no outside accounts are needed. Send a test message through the form and check Task History, then open the contact in FluentCRM to confirm the fields landed where you expected.

Service enquiries into the CRM

A web design studio's Beaver Builder contact page adds each enquirer to FluentCRM, so the team can track who asked about a quote and send a follow-up email series.

One record for repeat visitors

A coach whose clients often write in more than once keeps a single FluentCRM contact per email address instead of a new record for every message.

Local business newsletter growth

A bakery's site collects catering questions through a Beaver Builder form. Every sender becomes a FluentCRM contact the owner can later invite to seasonal offers, with their consent.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
Beaver Builder Forms New Contact Form Submission
Starts the workflow when a Beaver Builder contact form on your site receives a new submission. The values the visitor entered are passed to FluentCRM for mapping.
Step 2Action
FluentCRM Create or Update Contact
Creates a contact in FluentCRM from the submission, or updates the existing contact with the same email address. The step comes unmapped, so map the form's email, name and other fields after import.

What you need

FlowMatticCore
Beaver Builder Forms PluginPlugin
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.

Map the form's email field first. FluentCRM matches contacts on email address, so a submission without one can't be matched or created reliably.
Running several Beaver Builder forms? Check a test run for a value that tells them apart, then use it in a Filter between the trigger and the FluentCRM step so only the right form adds contacts.
Use a FluentCRM automation that starts when a contact gets a specific tag or list, so the people this workflow adds receive your follow-up emails.

Questions about this workflow

What if the Beaver Builder visitor is already a FluentCRM contact?

The Create or Update Contact step matches on email address. If a contact already has that email, FluentCRM updates it with the values you map instead of adding a second contact.

Does this work with Beaver Builder subscription forms?

This template listens to contact form submissions. FlowMattic's Beaver Builder Forms integration has a separate New Subscription Form Submission trigger you can use in another workflow.

Which form fields reach FluentCRM?

Only the fields you map in the FluentCRM step after import. Submit a test entry first so the form's values appear in FlowMattic, then match them to contact fields.

Is consent handled for marketing emails?

Not by the workflow itself. If you plan to email these contacts, add a consent checkbox to your Beaver Builder form and send marketing only to the people who ticked it.