GoHighLevel Prospect Generated Trigger: Setup Guide

GoHighLevel’s Prospect Generated trigger fires a workflow the moment a new prospect lands in the Prospecting Tool, whether that prospect came from a manual search, an embedded widget, or the AI that runs in the background on paid plans. The trigger itself is simple to add. What trips up most agencies is everything around it: it does not exist on the free plan, and even on the paid plan it only runs inside a sub-account, never at the agency level where the free tool actually lives.

That single fact explains most of the “I built the workflow and nothing happened” reports agencies run into with this feature. Below is what the trigger actually does, the filters it exposes, the tier and account conditions that decide whether it fires at all, and three workflow builds worth setting up once it does.

Why This One Is Different From Every Other Trigger in Your Account

Every other trigger in a GoHighLevel workflow builder — Contact Tag, Opportunity Status Changed, Form Submitted — reacts to something happening to your client’s contacts, inside your client’s sub-account. Prospect Generated is the one native trigger built around your agency finding its own next client. It sits in the same picker, uses the same If/Else logic and action library as everything else, but the record it fires on is a business you are pitching, not a lead your client is trying to close. That distinction is worth keeping straight, because it changes who the workflow’s messages are written for: your agency’s own voice pitching a local business owner, not your client’s brand voice talking to a customer.

What Actually Creates a Prospect

A prospect record is not a contact submitting your own form. It is a business your agency finds through the Prospecting Tool, generated one of three ways:

• In-App — you or a team member run a manual search inside the Prospecting Tool by niche and zip code, and every result that gets pulled into a report counts.
• Widget — a prospecting widget embedded on your agency’s own site or funnel, where a visitor runs a self-service audit on their own business and becomes a prospect the moment the report generates.
• Prospect AI — on Premium Prospecting, HighLevel’s AI searches your configured niche and zip code on its own schedule and drops new prospects into your dashboard without you running a search.

All three route through the same Prospect Generated trigger. The Source filter (below) is what lets a workflow tell them apart.

The Filters: Source and Conversion Score

The trigger is filed under the Events category in the trigger picker, alongside things like Form Submitted and Trigger Link Clicked. Two filters are available once it is added:

• Source — In-App, Widget, or Prospect AI. Use this to route a widget-sourced prospect (someone who actively ran an audit on themselves, meaning warmer intent) differently from an AI-sourced one your team has not looked at yet.
• Prospect Conversion Score — a 1-100 score with standard comparison operators (greater than, less than, equal to, is empty, is not empty). HighLevel’s own example workflow splits on a 70% threshold for widget-sourced prospects to trigger immediate outreach, versus a slower nurture path for anything below it.

Both filters can sit on the same trigger, so a single workflow can isolate “widget-sourced, score above 70” as its own branch without a separate If/Else step.

Free Prospecting Cannot Automate Anything

This is the part that stops the trigger from firing before any filter matters. HighLevel’s own Free vs Premium Prospecting comparison draws a hard line between the two tiers, and automation sits entirely on one side of it.

Free Prospecting exists only at the agency level and ships with zero automation, full stop — not a lighter version of the trigger, not a limited filter set, none of it. If your agency has never paid for Prospecting, there is no Prospect Generated workflow to build yet, regardless of how the trigger looks in the picker.

Sub-Account Only, Even on Premium

Paying for Premium does not automatically mean the trigger fires wherever you build the workflow. HighLevel’s own changelog entry for this trigger describes it as “available only at the sub-account level” — the automation has to live inside a sub-account’s workflow builder, not the agency’s own automation area.

Practically, that means Premium Prospecting has to be linked to (or purchased directly for) the sub-account where you want the workflow to run. The exact mechanics of that linking step are not fully spelled out in HighLevel’s documentation, so confirm in your own account which sub-account a given Premium subscription is actually attached to before you spend time building the workflow around it — a subscription sitting at the agency level with no sub-account link is the most likely reason a correctly-filtered trigger still shows zero enrollments.

Workflow Builds Worth Setting Up

Once Premium is confirmed and linked to the right sub-account, these are the splits worth building first:

• Score-based routing. One workflow, one Prospect Generated trigger, filtered to Conversion Score greater than 70: auto-create the contact, tag it “hot-prospect,” and fire an immediate personalized email or SMS. A second workflow (or a branch off the same trigger with an If/Else on score) enrolls everything under that threshold into a slower nurture sequence instead of an immediate pitch.
• Source-based tone. A widget-sourced prospect actively ran an audit on their own business, so the opening message can reference the report they just saw. An AI-sourced prospect has not seen anything yet, so the same immediate-pitch message reads as a cold outreach with someone else’s data attached. Split on Source and write each opening line accordingly.
• Pipeline assignment on arrival. Chain an Add to Pipeline action straight off the trigger so every new prospect lands in a dedicated “Prospecting” pipeline stage automatically, instead of a team member manually dragging them over after the fact — the same manual step HighLevel’s own reach-out documentation still describes as the default without this trigger wired up.
• Data enrichment before the first message. The trigger’s own action library includes an enrichment step alongside contact creation and tagging. Run it before the outreach action in the same workflow so the first message sent to a prospect can reference specifics about their business rather than opening on a generic template — the difference between an audit-style pitch and a mail-merge one.

The Tag-Based Backup Route

HighLevel’s own guide to reaching out to generated prospects documents a second path to the same automation: every prospect record gets an automatic “_New Prospect Received_” tag on the contact, independent of the Prospect Generated trigger itself. A standard Contact Tag trigger filtered to that exact tag can drive the same welcome-sequence and pipeline-assignment actions described above.

That gives you a fallback while you are confirming tier and sub-account linkage: if the native trigger is not showing enrollments yet, a Contact Tag workflow on “_New Prospect Received_” will catch the same contacts through the CRM side rather than the Prospecting side, and costs nothing extra to build in parallel.

Where Agencies Get This Wrong

The recurring mistake is not a filter or a broken action — it is building the workflow in the wrong place. An agency owner tests Prospecting for free at the agency level, likes the reports, and later tries to wire up automation in a sub-account’s workflow builder assuming the trigger will simply be there. It will show up in the trigger picker either way, because the picker does not check your plan before listing it. It just never enrolls anyone, because the Premium subscription was never linked to that sub-account, or was never purchased at all. Before troubleshooting filters, confirm the plan and the linkage first — that single check resolves the majority of “this trigger doesn’t work” reports for a feature that, once correctly placed, works exactly as documented.

Frequently Asked Questions

Why doesn't my Prospect Generated trigger fire on any prospects?

The most common cause is running Prospecting on the free tier, which has no automation at all, or building the workflow at the agency level instead of inside the sub-account your Premium Prospecting subscription is linked to. Confirm the plan and the sub-account link before checking filters.

What does the Conversion Score filter on this trigger measure?

It is a 1-100 score HighLevel assigns to each generated prospect, usable with standard comparison operators like greater than or less than. HighLevel's own example uses a 70% threshold on widget-sourced prospects to separate immediate outreach from a slower nurture sequence.

Can I automate prospect outreach without paying for Premium Prospecting?

Not through the Prospect Generated trigger itself, since automation is excluded from the free tier entirely. A workaround is a standard Contact Tag trigger filtered to the automatic "_New Prospect Received_" tag HighLevel applies to every generated prospect's contact record, which does not depend on the Prospecting automation tier.

Does the Source filter tell me which prospects came from Prospect AI versus a manual search?

Yes. The Source filter on the Prospect Generated trigger distinguishes In-App (manual search), Widget (embedded website widget), and Prospect AI (automatic discovery on Premium), so a single trigger can route each source into a different workflow branch.

We build your GoHighLevel account for you

CRM, pipelines, funnels, SMS and automation — configured for your business, not left for you to figure out.

• Setup (one-time)$850
• Ongoing (per month)$38.80

Get my free setup quote

No obligation quote · reply within 1 business day

This site is independently operated and is not officially affiliated with, endorsed by, or sponsored by HighLevel LLC. We do not receive referral commissions — this is our own flat-fee implementation service.