When a form submission is received in Fluent Forms, create a contact in FluentCRM with certain tags

Each Fluent Forms submission creates or updates a FluentCRM contact from the form’s email address, then adds the tags you choose to that contact so you can segment and email them.

Fluent Forms

FluentCRM

Download this workflow Browse more workflows

3 steps Setup ~5 min Used on 2.0k sites Free to import

The When a form submission is received in Fluent Forms, create a contact in FluentCRM with certain tags workflow on the FlowMattic canvas, with 3 steps across Fluent Forms, FluentCRM — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Fluent Forms and FluentCRM both run inside WordPress, but a form entry doesn't become a tagged contact on its own. When you want everyone who fills in a particular form to land in your CRM with a label that says where they came from, this workflow does it in two FluentCRM steps.

The Fluent Forms trigger fires when a new submission is received and passes the entry's fields to FlowMattic. The first FluentCRM step, Create or Update Contact, looks for a contact with the submitted email address. It updates that contact if one exists, or creates a new one if not.

The second FluentCRM step, Add Tags to Contact, adds tags to an existing contact. Since step 2 has just created or found the contact, the person already exists in FluentCRM when tagging runs. Both FluentCRM steps ship unmapped: after import you map the email and name fields into step 2, choose the tags in step 3 and point it at the contact from step 2. Check a test submission to see which contact value step 2 returns for that.

Every submission of the chosen form gets the same tags. Someone who submits twice is matched by email, so they keep one contact and the tags are simply added again. Task History shows what each FluentCRM step returned.

Tag leads by the form they used

A coaching site has separate Fluent Forms for a free call and for a price quote. Each form's copy of this workflow tags contacts with free-call or quote-request, so follow-up emails match the request.

Event registrations in the CRM

A workshop sign-up form creates FluentCRM contacts tagged with the workshop name, so the organiser can email only that group with joining details.

Newsletter opt-ins from a sidebar form

A blog's short email form adds readers to FluentCRM with a newsletter tag that an existing FluentCRM automation uses to send a welcome email.

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 when a new submission is received in Fluent Forms. The entry's field values, such as email and name, are passed on to FluentCRM. Submit the form you plan to use once to see which fields arrive.
Step 2Action
FluentCRM Create or Update Contact
Creates a FluentCRM contact, or updates the existing one with the same email address. The step ships unmapped: map the form's email field, plus the name and any other fields you want stored.
Step 3Action
FluentCRM Add Tags to Contact
Adds one or more tags to the contact from step 2. Pick the tags after import and map the contact from step 2's output; a test submission shows which value to use.

What you need

FlowMatticCore
Fluent 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.

Create the tags in FluentCRM before setting up step 3, so they are ready to pick in the Add Tags to Contact step.
To tag by an answer, such as an interest dropdown, put a Router between the Create or Update Contact step and the Add Tags step. Give each route its own Add Tags step for that answer and remove the shared one. Use values that can't both match.
If the form has a consent checkbox, put a Filter between the Fluent Forms trigger and the Create or Update Contact step that continues only when it is ticked. Entries without consent then create no contact and get no tags. Use whichever consent field your form has.

Questions about this workflow

Does the Fluent Forms submission need an email field?

Yes. FluentCRM's Create or Update Contact step matches and creates contacts by email address, so map a required email field from your form into it.

What if the form's email already belongs to a FluentCRM contact?

Step 2 updates that contact with the mapped values instead of creating a second one, and step 3 adds the tags to it. Tags the contact already had stay on it.

Can I add the contact to a FluentCRM list as well as tags?

Yes. Add FluentCRM's Add Lists to Contact action after step 3 and map the same contact. It works because the contact already exists by then.

Are Fluent Forms entries from before the import sent to FluentCRM?

No. Entries already stored in Fluent Forms don't start a run. Only submissions received while the workflow is active create or update contacts and get tagged.