How To Add Subscribe Newsletter Form In Elementor for Free with Fluent Forms & FluentCRM 2026

This workflow depends on three separate plugins working together: Elementor for the page layout, Fluent Forms for the form itself, and FluentCRM for storing subscribers. Check Plugins in your WordPress admin and confirm all three show as active — it's easy to install Fluent Forms and forget FluentCRM, since Fluent Forms works standalone without it and won't complain about the missing connection until you go looking for the integration option.

In Fluent Forms, click to create a new form and you'll get a choice between a blank form, a pre-made template, or a conversational form that asks one question at a time. For a straightforward newsletter signup, a blank form with just an email field (optionally a name field) is usually faster to configure than adapting a template built for something else. Give the form a clear internal name — you'll need to find it again in a dropdown list when you embed it in Elementor, and a vague name like "Form 1" gets confusing once you have several.

Open the form's settings and go to Configure Integrations, then add a new FluentCRM Integration Feed. Name the feed something recognizable, pick the FluentCRM list the subscriber should join, and map each form field to its FluentCRM counterpart — Email Address is required, while First Name, Last Name, and Full Name are optional but worth mapping if your form collects them. This mapping step is what actually moves a submission out of Fluent Forms' own entries table and into FluentCRM as a real contact; skipping it means the form works but nobody ends up on your list.

Open the page in Elementor and drag a Fluent Forms widget into the container where you want the signup form to appear. In the widget's settings, select the form you built by name from the dropdown — this is the moment a vague form name becomes a real problem, so double-check you're picking the right one if you've built more than one form. The form renders live in the editor immediately, letting you see the actual field and button styling before you publish.

Elementor's own container and widget styling controls the space around the form — background, padding, and alignment — while the form's own fields, colors, and button styling are set inside Fluent Forms itself, either in the form editor's Style tab or the widget's own settings panel. Keep the two separate in your head: resizing the container won't change how wide the email field looks if the field's own width setting is fixed, and changing Fluent Forms' theme won't fix a container that's too narrow around it. Adjust both and preview the page at desktop and mobile sizes before publishing.

If the widget is on the page in the editor but the form is blank or missing on the live site, caching is the most common cause — clear any caching plugin and your host's server-side cache, then reload the page in a private browser window. The next most common cause is the form actually being unpublished or deleted in Fluent Forms while the Elementor widget still references its old ID, which shows as an empty space where the form should be; re-selecting the form in the widget's dropdown resolves it. If neither fixes it, check the browser console for a JavaScript error, since a conflicting plugin script can occasionally block Fluent Forms' own scripts from loading.