Send an Email When a Fluent Forms Form Is Submitted

You want an email sent automatically whenever someone submits a Fluent Forms form — a new enquiry to your support team, a copy to the site owner, no manual checking. Zapify does this with a free automation: the A form is submitted trigger starts the run when your Fluent Forms form is submitted, and the Send an email action sends the message with the submitted fields mapped in.

This automation is fully free. Fluent Forms is a free Zapify integration, and the field tokens are exposed by the trigger at no cost.

What this automation does

The automation is one trigger plus one action:

• Trigger: A form is submitted (FLUENTFORMS_FORM_SUBMITTED)
• Action: Send an email (WP_SEND_EMAIL)

When a visitor submits the Fluent Forms form you choose, Zapify fills the email's tokens with the submitted values and sends it.

Zapify listens on Fluent Forms' fluentform/submission_inserted signal, which fires after the entry has been stored — so the automation runs on saved submissions.

Before you start

• Fluent Forms must be installed and active. Zapify reads your forms directly from it; if it is missing, the form-submitted trigger has no forms to offer and can prompt you to install it.
• You need at least one published Fluent Forms form.

How to build the automation

Step 1: Create a new automation

1. In the WordPress admin, go to Zapify → Automations.
2. Click Add New to open the builder.
3. Give the automation a clear name, such as Notify team on Fluent Forms submission.

Step 2: Add the "A form is submitted" trigger

1. Click Add Trigger.
2. Choose Fluent Forms as the app.
3. Select the trigger A form is submitted.
4. In the trigger's Form field, pick the specific form that should start the automation — for example, Contact Us.

Choosing a specific form is what exposes one token per field on that form (see Form-field tokens below). If you leave the form set to Any form, the automation runs for every Fluent Forms form but only the four general tokens are available, because the fields are not known until a submission arrives.

Step 3: Add the "Send an email" action

1. Click Add Action.

2. Choose WordPress as the app.

3. Select Send an email.

Step 4: Configure the email

Fill in the email fields. Use the {} token button beside any field to insert values from the submission.

Field	Required	What it does
To	Yes	Recipient address. Comma-separate several. You can insert a token here — for example the submitter's email field.
Subject	Yes	The subject line.
Format	Yes	HTML (default) or Plain text.
Body	Yes	The message. Insert tokens to include submitted values.
Cc / Bcc	No	Extra recipients.
From name / From email	No	Override the sender.
Reply to	No	Set where replies go — often the submitter's email.

For example:

• To: support@example.com
• Subject: New Fluent Forms submission
• Body: A new submission has been received: followed by the All fields token, or individual field tokens.

Step 5: Set the steps Live and save

1. Set both the trigger and the action to Live using their per-step switch. A new automation starts as Draft and will not run until its steps are Live.
2. Click Save.

Form-field tokens you can use

Once you select a specific Fluent Forms form, the trigger exposes these tokens. Insert them anywhere in the email with the {} button.

Token	What it holds
Form ID	The numeric ID of the submitted form.
Form title	The form's name.
Submitted at	The date and time of the submission.
All fields	Every submitted field rendered as one labelled block — handy when you just want the whole submission in the email.
One token per field	The value the visitor entered in that field, labelled with the field's Fluent Forms label. Fields inside multi-column layouts are included.

Multi-value fields such as checkbox groups are joined into a readable, comma-separated list.

How to test it

1. Open the page that contains your Fluent Forms form.
2. Fill it in with test details and submit it.
3. Check the recipient inbox for the email.
4. If nothing arrives, open Zapify → Logs to see whether the run fired and what the action reported.

The Send an email action is queued and sent in the background, so the message can arrive a moment after the submission rather than instantly.

Conclusion

With the A form is submitted trigger and the Send an email action, Zapify emails you every time a Fluent Forms form is submitted, with the submitted values mapped straight into the message — all on the free plan. Next, explore triggers and actions to chain more steps, or send the same notification for Contact Form 7, WPForms, or Gravity Forms.

FAQs

Can Zapify send an email when a Fluent Forms form is submitted?

Yes. Use the free A form is submitted trigger for Fluent Forms to start the automation, then add the Send an email action to send the message. Zapify fires once the entry is stored and sends the email you configured automatically to whichever recipient you set.

Is this feature free?

Yes. Fluent Forms is a free Zapify integration, and both the A form is submitted trigger and the Send an email action are included in the free plan. The form-field tokens are exposed by the trigger at no cost. Only automation Conditions — running the email only when a field matches a value — are a PRO feature.

Can I include the submitted form details in the email?

Yes. When you select a specific form, the trigger adds one token per field plus All fields, Form title, Form ID, and Submitted at. Click the {} button next to the subject, body, or any field and insert the tokens you want. Fields inside multi-column layouts are included, and multi-value fields such as checkboxes are inserted as a comma-separated list.

Can I send the notification to my team instead of the admin?

Yes. Enter any address in the To field of the Send an email action, and comma-separate several to notify a whole team. You can also use Cc and Bcc for additional recipients, and set Reply to to the submitter's email so replies reach the person who filled in the form.

Why didn't the email send?

First confirm both the trigger and action are set to Live and the automation is saved — a new automation stays in Draft until you switch its steps to Live. Then check Zapify → Logs for the run. If the run succeeded but no email arrived, the issue is usually the site's mail configuration; an SMTP plugin resolves most delivery problems.

Do I need to write any code?

No. The entire automation is built in the Zapify visual builder by picking the trigger, choosing your form, adding the Send an email action, and inserting tokens. No PHP, filters, or template edits are required.