Action Triggers – WP Hooks Trigger User Levels

Action Triggers let you grant BricksMembers levels when WordPress action hooks fire. It’s the simplest way to automate on-site events like form submissions, role changes, or lesson completion—without a webhook loopback.

Use Action Triggers when the event happens inside WordPress. Use webhooks when the event comes from an external platform (Stripe, LemonSqueezy, etc.).

When to Use Action Triggers

• Add a level when a user registers
• Grant a level after a form submission
• Give access when a WordPress role changes
• Remove a level when a subscription expires
• Trigger rewards after a course milestone

Step 1: Enable the Module

1. Go to BricksMembers → Settings
2. Open the Modules tab
3. Enable Action Triggers

The Action Triggers page will now appear under BricksMembers (alongside Level Automation, Webhooks, and Webhook Mapping).

Step 2: Create Your First Trigger

1. Go to BricksMembers → Action Triggers
2. Enter the Hook Name (e.g., user_register)
3. Choose the Action: Add Level or Remove Level
4. Select the Level to add or remove
5. Choose who the user is (see below)
6. Click Save Trigger

Add Level vs Remove Level

Each trigger can either add or remove a level:

• Add Level (default) – Assigns the selected level to the user when the hook fires
• Remove Level – Removes the selected level from the user when the hook fires

This is useful for subscription or membership scenarios where you want to automatically revoke access when certain events occur (e.g., subscription cancelled, role changed, or custom plugin hooks).

User Selection: Current User vs Hook Arguments

Action Triggers can add or remove a level from:

• Current logged-in user (default) – best for frontend actions like forms or buttons
• User from hook arguments – best for background actions that pass a user ID or WP_User object

If you choose “User from hook arguments,” BricksMembers tries to detect the user automatically from the hook arguments. If no user is found, the trigger won’t assign a level.

Example Hook Names to Test

These are safe, common WordPress actions you can test quickly:

• user_register – fires when a new user is created
• profile_update – fires when a user profile is updated
• set_user_role – fires when a user role is changed
• wp_login – fires when a user logs in

Tip: Use a test level when experimenting so you can remove it easily later.

Testing Your Trigger

1. Create a temporary level (e.g., “Trigger Test”)
2. Set your trigger to assign that level
3. Perform the action (register a user, log in, update a profile, etc.)
4. Check the user’s profile to confirm the level was added

Advanced: Hook Priority

Each trigger has a Priority field (default: 10). Only change this if you need your trigger to run before or after another plugin on the same hook.

Troubleshooting

Trigger didn’t assign a level?

• Make sure the Action Triggers module is enabled
• Confirm the hook name is correct (spelling matters)
• If you selected “User from hook arguments,” verify the hook passes a user ID or WP_User object
• Try switching to “Current logged-in user” for frontend actions

Multiple triggers fire at once? Disable the duplicates and keep only one trigger per hook unless you want multiple level assignments.

Next Steps

Combine Action Triggers with Levels, Drip Content, and Bricks conditions to build complete automation workflows. For off-site purchases, continue with the Webhooks guide.