GoHighLevel Pipelines Tutorial: How to Build a Sales Pipeline That Actually Moves Deals Forward

GoHighLevel pipelines are one of the platform's most powerful features and one of the most commonly underbuilt. Most GHL users create a pipeline, add a few stages, and then use it like a visual spreadsheet — manually dragging cards between columns and hoping deals do not fall through the cracks. A properly configured pipeline does much more than track where deals are. It drives the next action automatically the moment a deal moves.

This tutorial covers how to build a GoHighLevel pipeline from scratch, how to connect it to automation workflows, and what the difference looks like between a pipeline that just displays information and one that runs your sales process. If you're still getting oriented in GHL generally, GoHighLevel Review 2025 is a good starting point.

What a GHL Pipeline Is and What It Is Not

A pipeline in GoHighLevel is a visual representation of your sales or operational process. Each pipeline has stages, and each contact or deal sits in one stage at a time. Moving a contact from one stage to the next signals progress through the process.

The pipeline view shows you where everything stands at a glance: how many leads are at each stage, which ones have been sitting too long, which ones need immediate attention. That visibility is valuable on its own.

But the pipeline view is not what makes GHL pipelines powerful. What makes them powerful is that stage changes can trigger automated workflows. Every time a deal moves, something happens — a message goes out, a task is created, a notification fires, a sequence starts. The pipeline becomes the control panel for your sales automation, not just a scoreboard. This is the foundation that GoHighLevel Automation for Agencies builds its five core workflows on top of.

Designing Your Pipeline Stages

Before touching GHL, map the stages on paper. The most common mistake in pipeline design is building stages around internal process steps rather than the contact's actual position in the buying journey.

Instead of stages named things like Assigned to Rep, Waiting on Proposal, Internal Review — which reflect what your team is doing — name stages around what the contact has done or what the relationship status is:

• New Lead
• Contacted
• Qualified
• Appointment Scheduled
• Appointment Completed
• Proposal Sent
• Negotiation
• Won
• Lost
• Nurture

This naming convention makes the pipeline readable to anyone who opens it and maps cleanly to automation triggers. "When stage changes to Appointment Scheduled" is a clear event with an obvious next automated action: send the confirmation sequence.

Keep the stage count manageable. Eight to twelve stages is the practical range for most service businesses. Fewer and you lose visibility. More and people stop updating it because the friction of picking the right stage gets too high.

Building the Pipeline in GHL

In GoHighLevel, navigate to Opportunities in the left sidebar. If you have not created a pipeline yet, you will be prompted to create one.

Give the pipeline a name that identifies it clearly — Sales Pipeline, Client Acquisition, Real Estate Leads, and so on. You can have multiple pipelines for different business lines or client types.

Add your stages in order. GHL lets you drag stages to reorder them after creation, so do not worry about getting the order perfect immediately. Set a win probability percentage for each stage if you want forecasting data — this is optional but useful for sales teams tracking expected revenue.

Create a test opportunity by clicking the plus button in any stage. Fill in the contact name, the associated contact record, the opportunity value, and the expected close date. Walk the test opportunity through each stage manually to confirm the pipeline is set up as intended before connecting automation.

Connecting Workflows to Pipeline Stages

This is where the pipeline goes from static display to active sales process driver.

In GHL Workflows, create a new workflow and set the trigger to Opportunity Stage Change. Select the pipeline and the specific stage the opportunity needs to enter for this workflow to fire.

Here are the most valuable stage-triggered automations to build:

New Lead stage: Trigger the speed-to-lead follow-up sequence. An SMS within two minutes, a follow-up email at five minutes, a rep notification with full contact details. AI Follow-Up System for Sales covers designing this sequence properly.

Appointment Scheduled stage: Send the appointment confirmation sequence. Confirmation SMS and email immediately. Reminder 24 hours before. Reminder two hours before. A pre-appointment preparation email if relevant to your service. GoHighLevel SMS Automation covers building this in GHL specifically.

Appointment Completed stage: If the appointment was a no-show, trigger the rebooking sequence. If the appointment ran, send the next step — a proposal follow-up, a document request, a link to book the next call.

Proposal Sent stage: Start the proposal follow-up sequence. A check-in at 48 hours asking if they have questions. A follow-up at Day 5. A value-add email at Day 7. A final nudge at Day 14.

Won stage: Stop all sales sequences immediately. Trigger the onboarding sequence: welcome email, intake form, kickoff call booking link. Notify the delivery team. Create a task for the account manager. How to Automate Client Onboarding covers this sequence in full.

Lost stage: Stop all active sequences. Add the contact to a 90-day re-engagement campaign. Tag appropriately for future reference.

Nurture stage: Start a long-term nurture sequence for leads who are not ready now. Monthly contact with relevant value. A re-qualification check at 90 days.

Using Opportunity Values for Revenue Forecasting

GHL pipelines support opportunity values — the expected deal size for each contact in the pipeline. When combined with win probabilities per stage, this gives you weighted pipeline forecasting: the sum of all opportunity values multiplied by their stage probability.

To get value from this, you need two things: consistent opportunity values entered when the opportunity is created, and realistic stage probabilities set during pipeline setup.

GHL displays the pipeline total and stage totals in the pipeline view. For a more detailed breakdown, you can pull this data via the GHL API into a Google Sheet or a reporting dashboard for regular revenue reviews.

Managing Stale Deals

Deals that sit in a stage too long without moving are a sign that something has broken — either the deal is dead and needs to be marked Lost, or the follow-up has stopped and the contact needs attention.

GHL Workflows can automate stale deal detection. Create a workflow triggered by Opportunity Stage Change that sets a wait step for a defined number of days (say, seven days for a Proposal Sent deal), then checks whether the opportunity is still in the same stage. If it is, fire a rep notification: "Opportunity [Name] has been in Proposal Sent for 7 days without movement. Review and update."

This runs automatically and surfaces stalled deals before they get lost entirely. The rep gets a specific, actionable alert rather than having to manually audit the pipeline.

Multiple Pipelines for Different Business Lines

If your business handles more than one type of client or service, separate pipelines keep things organised and allow for different stage-triggered automations per business line.

A marketing agency might have: one pipeline for new client acquisition, a separate one for ongoing client project management, and a third for referral partner relationships. Each has different stages, different automation workflows, and different win criteria.

The contact can appear in multiple pipelines simultaneously. This is useful when the same person is both a prospect and an existing client in a different capacity.

Keeping the Pipeline Clean

A pipeline that is not maintained stops being useful within weeks. Two practices that prevent pipeline decay:

Required fields on opportunity creation. In GHL, you can make certain fields required when an opportunity is created — opportunity value, expected close date, source tag. Requiring these at creation means your reporting data is always complete.

Regular pipeline reviews. A weekly 15-minute review of every deal that has not moved in more than five days catches problems early. With stage-triggered stale deal notifications running, this review becomes a confirmation rather than a discovery process.

The Sales Process Analyzer is useful before you start building — it helps identify the specific bottlenecks in your current sales process that the pipeline design and automations should address.

From Pipeline to Automated Sales Process

A GoHighLevel pipeline that is connected to the right workflows does not just show you where deals are. It actively moves deals forward, sends the right message at the right moment, alerts your team when human attention is needed, and keeps the process consistent regardless of which rep is handling which deal.

Building this properly takes an afternoon for a basic setup and more for complex multi-pipeline organisations. The return — faster lead response, consistent follow-up, fewer stalled deals, visible revenue forecasting — shows up within the first few weeks. Designing the stage-to-workflow mapping correctly is usually the single biggest lever in a GHL rebuild, and it's a core part of the agency automation work I take on.

If you want help designing and building your GHL pipeline and automation stack, book a free 30-minute call. Bring your current sales process, even if it is just a description of how deals move through your business, and we will build the pipeline architecture together.