Workflow Examples
GoHighLevel Lead Nurturing Workflow Examples
Not the instant-response sequence that fires the moment a lead comes in, and not the win-back sequence for leads that already went cold — this is the middle: five full, worked GoHighLevel workflows for leads who are still engaged but genuinely not ready to buy yet. Each one below is broken down trigger by trigger, Wait step by Wait step, so you can see exactly how it's built, not just what it's called.
On This Page
The Five Pieces Every Example Below Is Built From
For the full platform overview — what GoHighLevel is, what it costs, how it compares to other CRMs — see the complete GoHighLevel workflow automation guide. This section covers just the five workflow-builder mechanics that make nurture sequences work, so the examples below make sense without re-explaining each one every time.
The trigger
Every example below starts with a Contact Tag trigger (fires when a specific tag is added or removed) or a Pipeline Stage / Opportunity Changed trigger (fires when a deal moves stage). Nurture almost never starts from a fresh form submission — it starts from a signal that a lead is real but not yet ready.
The Wait step
GoHighLevel's Wait action can pause a contact for a fixed duration, until a specific date, or until a condition is met — a reply, a tag, a click. Nurture leans hard on the fixed-duration and wait-until-condition modes: the spacing between touches is the entire point of a nurture cadence.
The If/Else branch
The If/Else action splits a workflow into separate paths based on contact data or behavior at the moment it's reached — tag present or not, a custom field value, whether an email was opened. Every example below uses at least one If/Else to stop treating every lead in the sequence identically.
Tag-based branching
Add Tag and Remove Tag actions are how a nurture workflow talks to the rest of the account — tagging a lead "Sales Ready" so a separate workflow (or a rep's view) picks it up, or removing "Active Follow-Up" so two sequences don't message the same lead at once.
The Goal Event
A Goal Event lets a contact skip ahead — or exit — the moment they do the thing the sequence was actually chasing (a reply, a booked call, a clicked link), regardless of where they are in the Wait steps. It's what stops a nurture sequence from still emailing someone who already said yes.
Read the full platform picture on the complete GoHighLevel workflow automation guide.
Five Real Lead Nurturing Workflows, Step by Step
Each example names the entry trigger, walks through the actual sequence of steps using GoHighLevel's own workflow-builder terms, and explains why that specific cadence and content mix fits that scenario.
The Wealth Management Trust-Building Drip
A prospect has had a real conversation with a Dubai-based financial advisory firm — an intro call, a portfolio review, a detailed reply — but a decision like moving an advisor or committing to a financial plan genuinely takes weeks or months, and continuing an urgent-response cadence at this point just reads as pushy.
Entry Trigger
Contact Tag (Added) — "Nurture – Evaluating Advisor"
- Trigger
Contact Tag added: "Nurture – Evaluating Advisor"
Applied by an advisor after an intro call, or automatically by an If/Else branch inside the main follow-up workflow when a reply signals "still deciding on an advisor."
- Action
Add Tag "In Nurture" / Remove Tag "Active Follow-Up"
Pulls the lead out of the fast-response cadence so the two sequences never message the same person on the same day.
- Wait
Wait 2 days
A short pause before the first nurture touch so it doesn't land the same day as the tag change.
- Action
Send Email — financial-planning education content
No pitch, no CTA to sign an advisory agreement — a piece that's genuinely useful on the planning problem they're facing (structuring a portfolio, retirement planning, wealth transfer), not a sales pitch for the firm.
- Wait
Wait 5 days
- Action
Send SMS — one-line check-in
A single, easy-to-answer question, not a status update. Something like: "Still thinking through your investment plan? Happy to send more on X if useful."
- If/Else
Did they reply to the SMS?
Yes → Goal Event fires, tag swaps back to "Active Follow-Up," advisor gets notified. No → continue the drip.
- Wait
Wait 5 days
- Action
Send Email — relevant client outcome story
Matched to their financial goal or life stage where the CRM has that field populated — retirement planning vs. wealth transfer, for example.
- Wait
Wait 7 days
- Action
Send Email — planning approach / comparison content
The first email in the sequence that includes a real, low-pressure link to book a consultation.
- If/Else
Did they open or click any of the last three emails?
Engaged → continue on the normal cadence. Not engaged → Add Tag "Cold – Low Engagement," drop to a monthly-only check-in instead of a weekly one.
- Goal Event
Trigger Link Clicked on the booking link
Jumps the contact straight to Add Tag "Consultation Ready" + notify assigned advisor, skipping any remaining Wait steps.
Why this cadence works: Long financial-advisory decisions punish both extremes: message too often and it reads as pressure they've already told you they're not ready for; go quiet for a month and a competitor fills the silence. Spacing touches five to ten days apart, alternating pure education with proof, gives the sequence enough data points — opens, clicks, a reply — for the If/Else branches to actually tell warm from cold, instead of guessing after one unanswered email.
The Real Estate Buyer Nurture
A buyer inquired, has clear criteria on file — budget, area, bedrooms — but isn't ready to view or make an offer yet. The job is to stay useful for as long as it takes without turning into noise.
Entry Trigger
Contact Tag (Added) "Buyer – Not Ready", or Opportunity/Pipeline Stage Changed to "Nurture" on the buyer pipeline
- Trigger
Contact Tag added: "Buyer – Not Ready"
Also fires when a rep manually drags the deal card to the "Nurture" stage — both routes land the contact in the same workflow.
- Action
Add Tag "Nurture Active"
- Wait
Wait 3 days
- Action
Send Email — new-listing digest
Merged from the custom fields captured on the inquiry form: budget range, preferred community, bedrooms.
- Wait
Wait 10 days
- Action
Send Email — area market update
Price trends and days-on-market for their specific community, not a generic citywide report.
- If/Else
Custom field check — did they click into a listing?
Clicked → Goal Event fires: notify the assigned agent, Add Tag "Warm – Viewed Listing," Wait 1 day, then send an SMS offering to set up a viewing. Didn't click → continue the drip.
- Wait
Wait 14 days, then loop back to the new-listing digest step
The cycle repeats — new listings, then a market update, then the click check — for as long as the lead stays in nurture.
- If/Else
Wait Until condition: 90 days with no engagement
No engagement in 90 days → Add Tag "Long-Term Nurture," cadence drops to monthly only. Tag "Ready to View" added at any point → exits nurture immediately into the active pipeline.
Why this cadence works: Real estate buyers commonly shop for months before committing, so the content itself has to be worth getting — new listings and market data are genuinely useful on their own, not a wrapper around a sales pitch. A click on one specific listing is a far stronger signal than an opened email, which is why that's the branch that actually pulls someone out of nurture and onto an agent's desk, not just a scheduled check-in.
The Insurance "Not Ready Yet" Renewal-Timed Branch
A lead requested a quote from a Dubai insurance agency — medical, life, or business cover — is actively engaged in the standard, fast-response follow-up sequence, and replies with some version of "not right now, I want to see out my current policy first." Continuing the same urgent cadence at that point is the fastest way to make automation look tone-deaf.
Entry Trigger
Contact Tag (Added) — "Not Ready Yet"
- Trigger
Contact Tag added: "Not Ready Yet"
Applied by an agent, or automatically inside the main follow-up workflow's own If/Else branch when a reply matches a "not now / comparing quotes / waiting on renewal" pattern — see the lead follow-up guide and the AI qualification guide for how that detection gets built.
- Action
Remove from the active follow-up workflow
Stops the fast cadence outright so the lead isn't getting a same-day nudge and a nurture email at once.
- Action
Remove Tag "Active Follow-Up" / Add Tag "In Nurture"
- Wait
Wait 7 days
- Action
Send Email — coverage-education resource, no sales CTA
What a policy actually covers and where cover gaps commonly show up — genuinely useful on its own, not a quote pitch.
- Wait
Wait 10 days
- Action
Send SMS — soft, single-question check-in
Easy to answer with one word. Something like: "Still weighing up your options on cover? Happy to send more info if useful."
- If/Else
Did they reply?
Yes → Goal Event fires: Remove Tag "Not Ready Yet," Add Tag "Active Follow-Up," agent notified, lead re-enters active follow-up. No → continue.
- Wait
Wait 14 days
- Action
Send Email — third value piece, different angle
A client outcome story about a claim handled well, rather than another coverage explainer, to test whether the angle (not just the timing) was the issue.
- If/Else
Tag "Not Ready Yet" still present after 60 days total?
Still present → branch into a slower, monthly long-term cadence timed loosely toward their current policy's renewal window. Removed at any point (by an agent, or by a reply) → exit into active follow-up immediately.
Why this cadence works: This is the clearest example of nurture as a designed exit ramp rather than a bolt-on afterthought — the tag is the handoff mechanism between two workflows with genuinely different personalities (urgent vs. patient). Insurance decisions in particular often just wait on a current policy's renewal date rather than never happening, so the sequence keeps watching for the one signal (the tag being removed, or a reply) that means it's time to hand the lead back rather than assuming "not ready" is permanent.
The Course Enrollment Nurture
Someone at a Dubai training institute opted in for a specific course brochure or a webinar seat — they've told you exactly which course or program interests them via what they downloaded, well before they've told you they're ready to enroll and pay.
Entry Trigger
Form Submitted (course brochure / webinar opt-in)
- Trigger
Form Submitted — course brochure / webinar opt-in form
- Action
Add Tag "Downloaded – [Course Name]" / Add Tag "Nurture – Top of Funnel"
The specific-course tag is what makes every later email topic-matched instead of generic.
- Action
Send Email — deliver the brochure or webinar recording immediately
- Wait
Wait 3 days
- Action
Send Email — related course content, same program
Curriculum detail, instructor background, or a related free lesson tied to the same course.
- Wait
Wait 4 days
- If/Else
Email Event — opened both of the previous emails?
Opened both → Wait 5 days, then send a third email with a genuine, low-pressure CTA to book a course consultation or enroll, with a Goal Event on the Trigger Link Clicked action. Opened neither → switch the next touch to SMS instead of a third email.
- Action
SMS touch (unengaged branch only)
A channel switch, not a repeat of the same unopened format — the point is to find out if the course still matters, not to just send more email.
- Wait
Wait 7 days, then drop into a monthly value-email cadence
Continues indefinitely until the Goal Event fires or the contact unsubscribes.
Why this cadence works: A course brochure or webinar download is a stronger topic signal than almost any other entry point, so matching every follow-up email to that specific course tag consistently outperforms a generic drip. Checking engagement after just two emails is deliberately cheap and early — it lets the workflow find out who's actually reading before investing in higher-effort content, and switching channels for the unengaged branch is what actually has a shot at rescuing attention instead of adding a third unopened email to the pile.
The Interior Design Cooling-Off Adjustment (Not Win-Back)
A lead considering a renovation or fit-out project with a Dubai interior design firm is still inside an active nurture sequence (like examples 1 or 2 above) but has stopped opening the last few sends. They haven't gone fully cold — the initial follow-up and re-engagement layers haven't even run yet — engagement is just fading, and the nurture cadence needs to adjust before it becomes worth abandoning.
Entry Trigger
If/Else action inside an existing nurture workflow, checking recent Email Events
- If/Else
Email Event check — no "opened" event across the last 3 sends?
This branch lives inside an existing nurture workflow, evaluated at each send rather than as a standalone trigger.
- Action
Add Tag "Cooling – Reduce Frequency"
- Wait
Wait 21 days
Stretches the interval instead of continuing the normal weekly or biweekly cadence.
- Action
Send Email — one different-angle message
A fresh project-inspiration piece or a genuine check-in question about the space they're planning, not a repeat of prior content on a longer delay.
- If/Else
Did engagement return — opened, clicked, or replied?
Yes → Remove Tag "Cooling," back onto the normal nurture cadence. No → Wait 30 more days, send one final light touch, then Add Tag "Dead – Needs Win-Back."
Why this cadence works: Keeping this brief on purpose: the difference between a nurture losing steam and a genuinely cold lead is a matter of degree, so it's worth stretching the interval and changing the angle once inside the nurture itself before writing the lead off. Once that also goes unanswered, the lead has effectively finished nurture — at that point it belongs in a dedicated win-back sequence with its own cool-down window and breakup message, not an ever-slower version of the same nurture. That full sequence — and when to finally mark a lead dead — is covered in how to recover leads that stopped responding, which this workflow hands off to.
Frequently Asked Questions
Follow-up is the fast, front-loaded sequence that runs in the minutes, hours, and first couple of weeks after a lead comes in — the goal is to get a response before the lead goes cold. Nurture is what a lead moves into once they've clearly said, directly or through inaction, that they're not deciding yet — the goal shifts from getting a quick reply to staying useful and top-of-mind over weeks or months. See the lead follow-up automation guide for the first layer this page's examples branch off from.
- Source: HighLevel Support — Workflow Trigger: Contact Tag
- Source: HighLevel Support — Workflow Action: Wait
- Source: HighLevel Support — Workflow Action: If/Else
- Source: HighLevel Support — Workflow Action: Goal Event
- Source: HighLevel Support — Workflow Trigger: Opportunity Changed
- Source: HighLevel Support — A List of Workflow Actions
Want This Built Inside Your GoHighLevel Account?
Every example above is genuinely buildable yourself inside GoHighLevel's native workflow builder — I'd rather you actually ship it than not. If you'd rather not spend the afternoons on tag logic, custom fields, and testing every If/Else branch, this is exactly what I build for clients as part of GoHighLevel automation — nurture sequences connected to instant follow-up and win-back on one side, and a fully automated sales pipeline on the other, so every tag and Goal Event is doing real work instead of sitting unused in an account nobody has time to finish configuring.
- 7+ years building CRM and follow-up automation for businesses worldwide
- 100,000+ leads delivered through systems built the same way this guide describes
- One real estate automation system alone responsible for 50,000+ of those leads
Ready to Build a Nurture Sequence That Actually Works?
Fastest way to start: message me directly on WhatsApp with what your leads actually look like once they're not ready to buy yet. Or send the details below and I'll get back to you.