GoHighLevel Referral Request Workflow: Setup (2026)

By Dr Priya Jaganathan, GoHighLevel Certified Admin · HL Growth Partner, Australia · Updated 14 September 2026 · 8 min read

Some links below are affiliate links — if you sign up through them, HL Growth Partner may earn a commission at no extra cost to you. It never changes what we recommend. Full disclosure.

A GoHighLevel referral request workflow is the highest-margin automation you can build for a service client, and almost nobody builds it properly. Most agencies fire the ask the moment money lands.

That is the mistake. Payment is not an outcome — it is the start of one. This guide shows you how to build the ask so it fires only after the customer has actually had a good experience, and how to track every referral back to the person who sent it.

Why your referral ask should fire on outcome, not on payment

A customer who has paid you has taken a risk. A customer who has received a good result has evidence.

Only the second one will put their own name behind you. Asking before the outcome converts poorly and quietly damages the relationship, because you are requesting a favour before you have delivered the thing they bought.

So the whole build hinges on one question: what event inside the sub-account reliably proves the customer is happy? Answer that and the rest of the workflow is plumbing.

Choosing the right trigger for a GoHighLevel referral request workflow

HighLevel gives you several honest proxies for a good outcome. Pick the one your client actually maintains — a trigger that depends on a pipeline nobody updates is a workflow that never runs.

Building the Won trigger

Create a new blank Workflow named Referral Request — Post Win. Add the Opportunity Status Changed trigger and set two filters: In Pipeline = your delivery pipeline, and Moved To Status = Won.

HighLevel's own documentation for this trigger lists filters for Assigned To, Has Tag, In Pipeline, Lead Value, Moved From Status, Moved To Status and Pipeline Stage — see the official Opportunity Status Changed article. Add a Has Tag filter to exclude anyone already tagged as a referrer.

The review-based variation

If your client's review request automation is already running, a fresh 4 or 5 star review is the best possible proof of a happy customer.

The catch is that HighLevel's Review Received trigger is contactless — the docs confirm reviews from Google and Facebook are not linked to a specific contact. So use it to notify staff to tag the matching contact, and let Tag Added do the sending.

Wait steps and Goal events: timing the ask so it lands

Straight after the trigger, add a Wait step. Our default across client builds is two to three days — long enough for the result to sink in, short enough that you are still front of mind.

Then send the SMS, add a second Wait of five to seven days, and send the email follow-up only if the first ask went unanswered.

This is where a Goal event earns its keep. Point the Goal at your referral trigger link click, so the moment the customer engages they skip straight to the thank-you branch instead of being nagged. If you are new to that pattern, our guide to Wait steps and Goal events covers the mechanics.

Wrap the branching in a clean If/Else so the workflow reads top to bottom. If/Else conditions in HighLevel let you split on tag, custom field or contact source without duplicating the whole sequence.

Writing the ask for SMS and email without breaking ACMA rules

Two channels, two jobs. SMS gets the reply; email carries the explanation and the shareable link.

The compliance layer

A referral request is a commercial electronic message, which means the Spam Act 2003 applies in full. Consent for one channel is not consent for another — the ACMA is explicit that an email opt-in does not permit you to send SMS.

Every message needs three things: consent, clear sender identification, and a functional unsubscribe. The ACMA's guidance on avoiding spam confirms unsubscribe facilities must remain working for at least 30 days and cannot demand a login or extra personal details.

Store the opt-out wording in a custom value so you can update it once across every client Workflow. Our deeper walkthrough of Australian SMS compliance in GoHighLevel covers sender IDs, quiet hours and LC Phone registration.

Not on HighLevel yet? Start with a free 30-day trial here — long enough to build everything in this guide before you pay a cent.

Trigger links: tracking who actually referred someone

Without tracking, a referral programme is a vibe. Trigger links turn it into data.

Go to Marketing > Trigger Links, add a link named Referral — Client Name, and point it at a simple referral form on the client's funnel. Drop that link into both the SMS and the email.

When it is clicked, HighLevel records the click on the contact timeline. A second Workflow using the Trigger Link Clicked trigger then tags the contact referrer-active and stamps a custom field with the click date. Our setup guide on trigger links and click tracking walks through the reporting side.

Keep the tag vocabulary boring and consistent — referrer-asked, referrer-clicked, referrer-converted. A disciplined tag naming structure is what makes the reporting readable twelve months later.

Attributing the referred contact back to the source

The referral form needs one extra field: Who referred you? Map it to a custom field called Referred By on the new contact.

Then build a third Workflow on the Form Submitted trigger that tags the new contact source-referral, notifies the owner, and creates an opportunity in the sales pipeline.

That single custom field is what lets you answer the only question the client cares about at review time: how much revenue came from referrals this quarter, and which customers generated it.

Rewarding the referral without running a commission programme

Reward on conversion, not on introduction. Fire the reward step only when the referred opportunity moves to Won.

This is not the Affiliate Manager — and that is deliberate

HighLevel's Affiliate Manager exists for structured commission programmes: recruiting affiliates, tracking sales, running payouts and managing tiers. It is a proper accounting tool.

A referral request Workflow is the lightweight version — no affiliate portal, no payout ledger, just a tag, a trigger link and a manual reward. According to NetPartners' 2026 pricing breakdown, the Affiliate Manager sits on the Unlimited plan at US$297 per month, while Workflows are available from Starter at US$97.

Build the Workflow first. If the client later needs commission tracking at scale, move them across using our guide to the GHL Affiliate Manager referral programme.

Testing and shipping the HighLevel referral workflow as a snapshot

Before you hand it over, run a real test contact through the whole path: move the opportunity to Won, receive the SMS, click the trigger link, submit the form, then move the referred opportunity to Won.

Check that the tags applied, the custom fields populated and the internal notification fired. If any step is silent, fix it now — a broken workflow trigger and action chain fails quietly, not loudly.

Once it passes, save the sub-account as a snapshot. A tested HighLevel referral workflow is one of the fastest pieces of value you can drop into a new client account on day one.

Common mistakes to avoid

• Triggering on payment instead of on delivery, so the ask lands before the customer has any result to talk about.
• Sending SMS without SMS-specific consent, which the ACMA treats as non-compliant regardless of an existing email opt-in.
• Using a raw URL instead of a trigger link, leaving you unable to tell who engaged with the ask.
• Skipping the Goal event, so customers who already referred someone still receive the follow-up chase.
• Rewarding the introduction rather than the conversion, which invites low-quality names and blows the budget.
• Reaching for the Affiliate Manager when a tag, a trigger link and a manual reward would have solved it in an afternoon.

If you want this referral engine built and tested inside your sub-accounts rather than half-finished in a draft Workflow, book a strategy call with the HL Growth Partner team.

Book Your Strategy Call →

Or if you just need the software first: grab the 30-day HighLevel trial and book us when you're ready to scale it.

Frequently asked questions

What triggers a referral request workflow in GoHighLevel?

The cleanest trigger is Opportunity Status Changed with the Moved To Status filter set to Won, so the ask only fires once the job is actually delivered. HighLevel's help documentation confirms this trigger supports filters including In Pipeline, Pipeline Stage, Moved From Status and Moved To Status. Appointment Status and Tag Added work as alternates for businesses that do not run opportunities.

How long should I wait before asking for a referral?

Our default across client builds is a Wait step of two to three days after the Won status, then a second touch about a week later if there is no click. Waiting lets the customer experience the result before you ask them to stake their reputation on you. There is no universally correct window, so test it per client rather than copying a number from a blog post.

Can I send referral request SMS to Australian customers?

Only if you hold consent for SMS specifically. The ACMA states that consent for one type of electronic message does not extend to another, so an email opt-in is not permission to text. Every message also needs clear sender identification and a working unsubscribe that stays functional for at least 30 days.

How do I track who actually referred someone?

Use a trigger link as the referral URL inside both the SMS and the email. The click is recorded on the contact timeline and can start a second workflow that tags the contact as an active referrer. Then capture a Referred By field on the referral form so the new contact is attributed back to the source.

What is the difference between this and the Affiliate Manager?

Affiliate Manager is HighLevel's structured programme for recruiting affiliates, tracking commissions and running payouts. A referral request workflow is far lighter: it asks happy customers for an introduction and rewards them manually with a tag and a task. Use the Workflow for service businesses and the Affiliate Manager only when you genuinely need commission accounting.

Which HighLevel plan do I need to build this?

Workflows, trigger links, tags and custom fields are available from the Starter plan at US$97 per month, so the referral request workflow itself needs no upgrade. The Affiliate Manager is the feature gated to the Unlimited plan at US$297 per month, according to 2026 pricing breakdowns. Build the Workflow version first and upgrade only if the client outgrows it.

Should I use Conversation AI to handle referral replies?

Conversation AI can handle the first reply and qualify the referred person, but only after the workflow has proven it produces replies at all. Start with a human handling responses so you can see the real objections and wording. Then train the bot on those, and always build a clean handover when the reply is not a referral.

Related Articles on HL Growth Partner

Workflow foundations

• Workflow builder fundamentals in GoHighLevel
• Stopping silent automation failures

Referral and affiliate programmes

• Affiliate Manager setup and payouts
• Running a structured commission programme in HighLevel

Getting more from the existing database

• Database reactivation campaign setup
• Automating review requests that customers answer