When a new WordPress user is created, create a new lead in MailBluster

When someone registers as a user on your WordPress site, this workflow creates a lead for them in MailBluster, so your email list grows with your membership and you can send them campaigns from there.

WordPress

Mailbluster

Download this workflow Browse more workflows

2 steps Setup ~5 min Used on 2.1k sites Free to import

The When a new WordPress user is created, create a new lead in MailBluster workflow on the FlowMattic canvas, with 2 steps across WordPress, Mailbluster — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

New site members are often the people most interested in hearing from you, yet a WordPress account and a mailing list are two separate places. Exporting users and importing them into MailBluster every few weeks leaves gaps and stale data. This workflow adds each registration to MailBluster as it happens.

The WordPress trigger, New User, fires when a new user is registered on the site where FlowMattic runs. The new user's details pass to MailBluster, where Create a New Lead adds them to your account using the values you map, such as the email address.

Every new account triggers it, whether the person signs up themselves or an admin creates the user, because there is no Filter as imported. Think about consent before you turn it on: if your registration form doesn't ask about marketing email, add that question and a Filter for it. Task History records each run and what MailBluster sent back.

Membership site welcome series

Members register for your course or community site. Each new account becomes a MailBluster lead, so they can receive the onboarding emails you send from there.

Store customers who create accounts

Shoppers who register on your WordPress shop are added to MailBluster, giving you one list for product news and offers to account holders.

Community forum sign-ups

People who join your forum get a WordPress account. Adding them to MailBluster lets you send a weekly digest to the whole community.

How this workflow runs

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

Step 1Trigger
WordPress New User
Runs for each account added to WordPress, by sign-up or by an admin. The new account's details, such as email, username and name, become available to map into MailBluster.
Step 2Action
Mailbluster Create a New Lead
Adds the new user to MailBluster as a lead. Connect your MailBluster account and map the WordPress user's email, plus any name details your site stores. A test registration shows what the step accepts.

What you need

FlowMatticCore
Mailbluster 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.

Add a Filter after the trigger that checks the user's role, which arrives with the user's meta data, so only subscribers or customers reach MailBluster and staff accounts stay off your list.
If your registration form stores a marketing consent answer as user meta, add a Filter on it. Confirm in a test run that the answer arrives with the new user.
Register a test account with an address you control after import, then check the new lead in MailBluster and the run in Task History.

Questions about this workflow

Will WordPress users created by an admin also go to MailBluster?

Yes. The trigger fires on any new registration, so accounts an admin adds are included unless you add a Filter, for example on the user role.

What happens if the email is already a MailBluster lead?

The step creates a lead, and MailBluster decides how to handle an address it already holds. Test with a known address and read its response in Task History.

Are my existing WordPress users added to MailBluster?

No. Only users registered after the workflow is on are sent. Import your current users into MailBluster separately.

Does it need a registration plugin?

No. It listens for new WordPress users however they are created, including the default registration page and plugins that create standard WordPress users.