Premium Integrations
How to Add a Contact Form 7 Lead to FluentCRM
If FluentCRM runs on the same site, every form lead can become a contact there with no export. Zapify does this with the free A form is submitted trigger and the Add or update a contact action. FluentCRM is a Zapify PRO integration.
What this automation does
The automation is one trigger plus one action:
- Trigger: A form is submitted (
CF7_FORM_SUBMITTED, Contact Form 7) - Action: Add or update a contact (
FLUENTCRM_ADD_CONTACT, FluentCRM)
Each time the form is submitted, Zapify adds the visitor to FluentCRM, or updates the contact if the email is already there.
Before you start
- Contact Form 7 installed and active, with a published form that has an email field.
- FluentCRM installed and active.
PRO feature
FluentCRM is a Zapify PRO integration. The A form is submitted trigger itself is free.
How to build the automation
Step 1: Create a new automation
- In the WordPress admin, go to Zapify → Automations.
- Click Add New to open the builder.
- Name it clearly, such as Add form leads to FluentCRM.

Step 2: Add the "A form is submitted" trigger
- Click Add Trigger.

- Choose Contact Form 7 as the app.

- Select A form is submitted.

- In the Form field, pick the specific form. Choosing a form gives you one token per field on it.
Step 3: Add the "Add or update a contact" action
-
Click Add Action.
-
Choose FluentCRM as the app.
-
Select Add or update a contact.
Step 4: Configure the action
| Field | Required | What it does |
|---|---|---|
| Yes | Insert the token for the form's email field. | |
| First name / Last name | No | Insert the matching form-field tokens, if your form collects them. |
| Tags | No | Comma-separated tag IDs, not names — find a tag's ID in FluentCRM's own interface. |
| Lists | No | Comma-separated list IDs. |
| Mark as subscribed | No | Off by default, which adds the contact as Pending. Only tick this where you have actual consent to email them — adding people as subscribed without it is what gets a sending domain blocked. |
Step 5: Set the steps Live and save
Each trigger and action has its own Live / Off / Draft switch. A new automation starts as a Draft and does nothing until its steps are Live.
- Set the trigger and every action to Live.
- Click Save.

Step 6: Test it
Submit the form with an address you control. Check FluentCRM → Contacts, or open Zapify → Logs.
Tokens you can use
Once you select a specific Contact Form 7 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, named after the field's tag (for example a your-email tag becomes a your-email token). |
Multi-value fields such as checkbox groups are joined into a readable, comma-separated list.
Conclusion
With the free A form is submitted trigger and the Add or update a contact action, form leads land in FluentCRM as they arrive. For new accounts, see adding a new WordPress user to FluentCRM.
FAQs
Is this free in Zapify?
The trigger is free. The FluentCRM action needs an active Zapify PRO licence.
Does it need a Connection?
No. FluentCRM runs on your own site, so there is nothing to connect.
Do I need to write any code?
No. Everything is set up visually.