Client Portal: User Login Trigger Supports New Experience

TL;DR

HighLevel updated the 'User login' workflow trigger to support the new Client Portal logins. No action is required from agency owners.

Who this affects

This affects anyone using or planning to use workflows tied to client logins within HighLevel. If your agency utilizes the new Client Portal, this update ensures login activity can now reliably trigger automations. HighLevel has not confirmed who is specifically affected by this change in terms of plan level or specific sub-account setups.

What changed

The 'User login' trigger now fires correctly when users log into the new Client Portal. Previously, it only worked for legacy membership logins. HighLevel has also introduced a dedicated 'Client Portal' category for workflow triggers. This new category now houses all Client Portal-related triggers, improving organization. The 'User login' trigger itself has moved from the 'Courses' category into this new 'Client Portal' category. Similarly, the 'Client portal file uploaded' trigger has been relocated from the 'Membership' category to the new 'Client Portal' category. The helper text for the 'User login' trigger was updated to clarify that it now covers both legacy membership logins and the new Client Portal logins. HighLevel has not confirmed any limits, plan gating, or rollout status for this update.

Where to find it

Access this update by navigating to Workflows > Create New Workflow > Add trigger. Within the trigger selection menu, you will now see the new 'Client Portal' category listed. The 'User login' trigger and the 'Client portal file uploaded' trigger are located inside this new category.

How agencies will use this

Agencies can now reliably automate processes based on when a client accesses their dedicated portal. For example, an agency could set up a workflow that triggers immediately after a client logs into their portal for the first time. The workflow could then check if the client has completed their initial onboarding tasks. If not, the workflow could automatically send a reminder email or an SMS message with a link to the next steps. Another use case involves tracking engagement; if a client logs in after a period of inactivity, the workflow could notify an account manager via an internal HighLevel notification. This allows for proactive client re-engagement strategies, all based on the client's direct interaction with their portal.

Our take

This is a standard technical correction. The new Client Portal is a core feature, and it is logical that its login events should be triggerable in workflows. HighLevel simply closed a gap here. It's a minor update for most agencies unless you were specifically waiting for this functionality to automate Client Portal interactions.