Forms Integrations
Create a WordPress User When a Fluent Forms Form Is Submitted
Fluent Forms has its own registration option on its paid plans — but Zapify can create the WordPress account directly from any Fluent Forms submission with no addon required, using the A form is submitted trigger and the Create a user action. Both are free.
What this automation does
The automation is one trigger plus one action:
- Trigger: A form is submitted (
FLUENTFORMS_FORM_SUBMITTED, Fluent Forms) - Action: Create a user (
WP_CREATE_USER, WordPress)
When a visitor submits the Fluent Forms form you choose, Zapify takes the submitted email (and name, if collected) and creates a matching WordPress account.
Before you start
- Fluent Forms must be installed and active, with a form that collects at least an email address.
- Both the trigger and the action are 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 Create account from Fluent Forms signup.
Step 2: Add the "A form is submitted" trigger
- Click Add Trigger.
- Choose Fluent Forms as the app.
- Select the trigger A form is submitted.
- In the Form field, pick the specific signup form — this is what exposes one token per field.
Step 3: Add the "Create a user" action
- Click Add Action.
- Choose WordPress as the app.
- Select Create a user.
Step 4: Configure the action
| Field | Required | What it does |
|---|---|---|
| Yes | Insert the submitted email field token. | |
| Username | No | Insert a submitted name or username field, or leave empty to use the email address. |
| Password | No | Leave empty — Zapify generates a strong one. |
| First name / Last name | No | Insert the submitted Name field's first and last components. |
| Role | No | Leave empty for your site's default role, or pick a specific one. |
| Email the new user | No | On by default — sends WordPress's own welcome email with a password reset link. |
Duplicate emails fail
The action fails if a WordPress account with the submitted email (or chosen username) already exists. Consider what should happen for a repeat submitter before relying on this in production.
Step 5: Set the steps Live and save
- Set both the trigger and the action to Live.
- Click Save.
Tokens this action makes available
| Token | What it holds |
|---|---|
| Created user ID | The ID of the account that was created. |
| Created user email | The email address it was created with. |
| Created username | The username it was created with. |
How to test it
- Submit the form with an email address that doesn't already have an account.
- Check Users in the WordPress admin to confirm the account was created.
- If it wasn't, open Zapify → Logs for the reason.
Conclusion
With the A form is submitted trigger and the Create a user action, Zapify turns a Fluent Forms submission into a WordPress account without a separate registration addon. Next, build the same flow for Contact Form 7, WPForms or Gravity Forms.
FAQs
Do I still need a separate registration addon?
No. This automation creates the account entirely through Zapify's free Create a user action.
What happens if someone submits with an email that already has an account?
The action fails and reports why in Zapify → Logs; it doesn't overwrite the existing account.
Does Fluent Forms still save the entry?
Yes. The form-submitted trigger already creates the entry as normal Fluent Forms behaviour — add the Create a user action alongside any other action, such as Send an email, on the same automation.
Is this feature free?
Yes. Both the trigger and the Create a user action are free.
Do I need to write any code?
No. Everything is configured in the Zapify visual builder.