How to Add a WordPress User Role When a Subscriber Joins a MailPoet List

If joining a list means "this person is a member", your site should agree. Zapify can give a WordPress user a role as soon as MailPoet adds them to a list, using the A subscriber is added to a list trigger and the free Add a role to a user action. MailPoet is a Zapify PRO integration.

What this automation does

The automation is one trigger plus one action:

• Trigger: A subscriber is added to a list (MAILPOET_SUBSCRIBER_ADDED_TO_LIST, MailPoet)
• Action: Add a role to a user (WP_ADD_USER_ROLE, WordPress)

When somebody is added to the list you choose and their email matches a WordPress account, Zapify adds the role to that account.

Before you start

• MailPoet installed and active, with the list already created.
• The role you want to grant, such as a custom Member role.
• Subscribers who also have a WordPress account with the same email address.

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. Name it clearly, such as Give list members their role.

Step 2: Add the "A subscriber is added to a list" trigger

1. Click Add Trigger.

2. Choose MailPoet as the app.

3. Select the trigger A subscriber is added to a list.

Configure the trigger:

Field	Required	What it does
List	Yes	Pick the list that means "member".

Step 3: Add the "Add a role to a user" action

1. Click Add Action.

2. Choose WordPress as the app.

3. Select Add a role to a user.

Step 4: Configure the action

Field	Required	What it does
User	No	Leave empty. The action then uses the WordPress account whose email matches the subscriber.
Role	Yes	Pick the role to grant — the list shows the roles that exist on your site.
Replace existing roles	No	Off by default, so the user keeps their current roles. Turn it on only if this role should replace all others.

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.

1. Set the trigger and every action to Live.
2. Click Save.

Step 6: Test it

Add a test subscriber who has a WordPress account to the list. Check the user's Role in Users → All Users, or open Zapify → Logs to confirm the run.

Tokens you can use

The A subscriber is added to a list trigger exposes Subscriber ID, Email, First name, Last name, List ID and List name. The action itself needs none of them, because it finds the user from the subscriber's email.

Conclusion

With the A subscriber is added to a list trigger and the free Add a role to a user action, a MailPoet list decides who gets access on your site. To email the new member as well, see sending an email when a subscriber is added to a list.

FAQs

Is this free in Zapify?

The Add a role to a user action is free, but the MailPoet trigger is part of the MailPoet PRO integration and needs an active Zapify PRO licence.

Why was the run skipped?

Nobody on the site has the subscriber's email address. Open Zapify → Logs to see the message. Roles can only be added to users.

Does the user lose their other roles?

Not unless you turn on Replace existing roles.

Can different lists grant different roles?

Yes. Build one automation per list, each with its own List and Role.

Does Zapify's own MailPoet action start this automation again?

No, not by default. Zapify ignores events caused by its own actions, so an automation that changes a MailPoet list does not trigger a MailPoet automation in the same request. This is what stops an automation looping back on itself. Subscribers added by a MailPoet form, by you in MailPoet, or by another plugin do start it.

Do I need to write any code?

No. Everything is configured visually.