GoHighLevel Tutorial

workflowdynamicshero

GoHighLevel Tutorial

How to Set Up a Sales Pipeline in GoHighLevel

If you’re switching to GoHighLevel from a traditional CRM, the pipeline is the first thing worth getting right. It’s not just a Kanban board — it’s the structure that drives your follow-up automations, reporting, and team accountability. This tutorial walks through building a working pipeline from scratch, including the settings most new users overlook.

What this tutorial covers: creating a pipeline, defining stages that match a real sales process, connecting opportunities to contacts, and linking stages to automation triggers.

Prerequisites:

  • An active GoHighLevel account (any paid plan includes pipelines)
  • Admin or agency-level access to the sub-account you’re configuring
  • A rough outline of your actual sales process (even on paper) before you start

If you’re still deciding whether GoHighLevel is the right CRM for your business, see our full GoHighLevel review or our GoHighLevel vs. Pipedrive comparison for a side-by-side look at how the two platforms handle pipeline management.

Step 1: Navigate to Pipelines

From the main dashboard, go to Settings > Pipelines (in some accounts this appears under the Opportunities tab in the left-hand navigation, depending on your sub-account configuration). Click Add Pipeline to start a new one rather than editing the default “Pipeline” that GoHighLevel creates automatically — keeping the default intact gives you a fallback if something goes wrong during setup.

Step 2: Name the Pipeline and Plan Your Stages

Give the pipeline a name that reflects what it tracks (e.g., “New Business Sales” or “Inbound Leads”), not just “Sales Pipeline.” If you manage multiple lead sources or sales motions, you’ll likely want separate pipelines for each rather than cramming everything into one.

Before adding stages, map them to your actual process. A common structure for service businesses looks like:

  • New Lead
  • Contacted
  • Qualified
  • Proposal Sent
  • Negotiation
  • Won
  • Lost

Keep the list short. Every stage should represent a point where something changes — a different action, a different owner, or a different automation. A pipeline with 10+ stages usually means some of them should be tags or custom fields instead.

Step 3: Add and Order Your Stages

Inside the pipeline editor, click Add Stage for each step in your process. Drag stages into the order leads actually move through. GoHighLevel lets you reorder stages at any time, but changing the order after opportunities are already assigned can make historical reporting harder to read — so it’s worth getting the order right before you go live.

Each stage has a name field only at this point; automations and triggers are configured separately in Step 5.

Step 4: Connect Opportunities to Contacts

Pipelines track opportunities, which are separate records linked to contacts. When a new lead comes in through a form, calendar booking, or workflow, you’ll typically create an opportunity automatically and attach it to the contact record.

To set this up:

  1. Go to Automation > Workflows
  2. Create or edit the workflow that handles new lead intake
  3. Add the Create/Update Opportunity action
  4. Select the pipeline and starting stage (usually “New Lead”)
  5. Map the opportunity to the triggering contact

This step is what prevents leads from sitting in your CRM as contacts only, invisible to your sales team’s pipeline view.

Step 5: Set Up Stage-Based Automations

This is where GoHighLevel’s pipeline becomes more than a visual board. For each stage, decide what should happen automatically when an opportunity enters it — an SMS to the assigned rep, an email to the lead, a task reminder, or a tag update.

In Automation > Workflows, use the Pipeline Stage Changed trigger and filter by the specific stage. Common examples:

  • New Lead → Contacted: trigger an outbound call task and a follow-up email if no response within 24 hours
  • Proposal Sent → Negotiation: notify the sales manager
  • Won: trigger onboarding workflow and remove the lead from any nurture sequences
  • Lost: tag the contact and add to a long-term re-engagement list

Step 6: Assign Ownership and Permissions

If multiple team members work the pipeline, set up User Permissions under Settings so reps only see opportunities assigned to them, while managers retain full pipeline visibility. Go to Settings > My Staff to adjust this per user. Skipping this step is one of the more common reasons pipelines turn into a shared mess where no one is clearly accountable for a given lead.

Settings That Are Easy to Miss

  • Default pipeline assignment: If you don’t specify which pipeline new opportunities go to in your workflows, GoHighLevel may default to the original “Pipeline” rather than the one you built — double-check this in every lead-intake workflow.
  • Stage automation triggers firing on manual moves too: If a rep manually drags an opportunity to a new stage, stage-based automations still fire. This is usually desirable, but worth testing so you don’t send unintended messages while setting things up.
  • Lost reason tracking: When marking an opportunity as “Lost,” GoHighLevel allows you to capture a reason. Enabling and using this consistently makes your pipeline reporting far more useful when reviewing win/loss trends later.
  • Email/SMS deliverability setup: Pipeline automations that send messages won’t perform well if your domain’s SPF, DKIM, and DMARC records aren’t configured. This is a one-time setup under Settings > Email Services but is frequently skipped, leading to messages landing in spam.

Related Reading