When a submission is received in Contact Form 7, Create a new user in WordPress and send data with form submission and user id to Zapier

Each Contact Form 7 submission creates a WordPress user account, then FlowMattic sends the submitted fields and the new user’s ID to Zapier so a Zap can carry on from there.

Contact Form 7

WordPress

Zapier

Download this workflow Browse more workflows

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

The When a submission is received in Contact Form 7, Create a new user in WordPress and send data with form submission and user id to Zapier workflow on the FlowMattic canvas, with 3 steps across Contact Form 7, WordPress, Zapier — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Some sites turn a simple form into an account: a membership request, a client sign-up, a course enquiry that should come with a login. Doing that by hand means reading each entry, adding the user in the dashboard, then telling your other tools about it. This workflow does the account part on your own site and hands the result to Zapier for the rest.

The Contact Form 7 trigger fires when a visitor sends the form. The next step uses the WordPress New User action, and you map the submitted name and email into it. The last step, Submit Data in Zapier, passes the form answers plus the user ID from the WordPress step's response to Zapier, where a Zap of yours picks them up.

The user is created inside WordPress by FlowMattic, so that part never leaves your site. Only the last step sends data out. Use it when a tool you rely on is easier to reach from Zapier, and keep the rest of the work in the workflow.

Client portal sign-ups

A prospective client fills in a Contact Form 7 request form. They get a WordPress account for your portal, and your Zap adds the same person, with their user ID, to the project tool your team uses.

Member applications on a community site

Each application becomes a WordPress user straight away. Zapier receives the answers and the ID, so a Zap can post the new member to a team chat channel or a tracking sheet.

Course enquiries that need a login

Students asking to join get an account on submit. The user ID sent to Zapier lets a Zap tie later records in another app back to that WordPress user.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
Contact Form 7 New Form Submission
Runs each time a visitor submits your Contact Form 7 form. The submitted fields become data you can map into the WordPress and Zapier steps.
Step 2Action
WordPress New User
Creates a new WordPress user from the submission. Map the form's email and name fields into it, then run a test so you can see which values the step returns, including the new user's ID.
Step 3Action
Zapier Submit Data
Sends data to Zapier. Map the form answers and the user ID from the WordPress step into it, then test the workflow and confirm in Zapier that your Zap receives every value you mapped.

What you need

FlowMatticCore
Contact Form 7 PluginPlugin
Zapier AccountAccount

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.

Make the email field required in the Contact Form 7 form tag (email*) so the WordPress step always has an address to create the user with.
Put a Filter between the Contact Form 7 trigger and the WordPress step that continues only when a terms or consent checkbox is ticked. Visitors who didn't tick it stop there, so they get no account and nothing is sent to Zapier.
If all you need in Zapier is something FlowMattic already connects to, you can replace the Zapier step with that app's action and keep the whole run inside your workflow.

Questions about this workflow

What happens if the email from Contact Form 7 already belongs to a WordPress user?

No second WordPress account is made for an address the site already knows. The New User step returns the existing account's user ID instead, so that is the ID your Zapier mapping picks up. Task History shows which user ID the step returned for each submission.

Is a Zapier account required for the last step?

Yes. The last step sends data to Zapier, so you need a Zapier account and a Zap set up to receive it. Without the Zapier step, the workflow still creates users from Contact Form 7.

Does Contact Form 7 still send its own notification email?

Yes. The trigger only listens for new submissions. Your form's mail settings stay as they are, so you keep getting the usual email for each entry.

Which WordPress role does the new user get?

Open the New User step after import to see what it offers, then submit the form once with your own details and look at the new account under Users. Confirm the role there before you turn the workflow on.