How to Automate Your GHL Sales Pipeline So Leads Move Themselves (Step-by-Step)
If you're still manually dragging cards across your GHL pipeline, you're doing it wrong. After building pipeline automation for 150+ coaches at Systrify, Harsh Sharma explains the exact workflow setup that turns your pipeline into a self-driving deal machine.
Most coaches set up a GHL pipeline, add a few stages, and then spend 30 minutes a day manually moving leads from "New Lead" to "Booked" to "Proposal Sent." That's not automation — that's a to-do list with a fancier UI.
The real power of GHL's pipeline is that every stage change can trigger a workflow. When you wire those two things together properly, leads move themselves, follow-ups fire automatically, and you only touch a deal when it needs a human decision.
Here's exactly how to set it up.
Step 1: Design Your Pipeline Stages First (Don't Skip This)
Before touching a single workflow, map your actual sales process onto paper. For most coaching businesses, this looks like:
- New Lead — just opted in or was added manually
- Contacted — first outreach sent
- Call Booked — appointment confirmed in calendar
- Call Completed — discovery call happened
- Proposal Sent — offer or pricing shared
- Won — paid and onboarding
- Lost / Nurture — not ready now, long-term follow-up
Resist the urge to add 12 stages. Complexity kills automation. If a stage doesn't trigger a different action, merge it with the one before it.
Step 2: Set Up the "Opportunity Stage Changed" Trigger
Go to Automation → Workflows → + New Workflow. The trigger you want is Opportunity Stage Changed. This fires every time a deal moves to a specific stage — manually or automatically.
Set the filter to a specific pipeline and a specific stage. You'll build one workflow per stage transition that needs an action. Here's what each stage should fire:
- New Lead → Send instant SMS + email intro sequence. Tag contact as "pipeline-active."
- Call Booked → Send confirmation email, calendar invite, and a 24-hour reminder SMS.
- Call Completed → Send a "thanks for our call" email with a link to your offer or proposal doc.
- Proposal Sent → Start a 3-day follow-up sequence: Day 1 check-in, Day 3 urgency nudge.
- Won → Send welcome email, add to onboarding pipeline, remove from all follow-up sequences.
- Lost / Nurture → Enroll in a 90-day long-game email nurture. Remove from active sequences.
Step 3: Auto-Advance Stages Based on Contact Actions
This is where most people stop — and it's only half the setup. You also want leads to move themselves when they take an action.
Create separate workflows with these triggers:
- Appointment Booked → Move opportunity to "Call Booked" stage automatically
- Appointment Completed → Move to "Call Completed"
- Form Submitted (e.g. intake form) → Move to "Proposal Sent"
- Payment Received → Move to "Won," stop all other sequences
In each workflow, use the Update Opportunity action and set the stage field to the correct destination. Takes 2 minutes per workflow and removes 100% of the manual dragging.
Step 4: Add Pipeline Value and Close Date Automatically
At Systrify, Harsh Sharma adds one extra step that makes reporting actually useful: when a lead hits "Call Booked," a workflow automatically sets the opportunity value (based on the product/tag they came from) and a projected close date (7 days out by default).
This means your pipeline value number is always live and accurate — not a guess you update when you remember. Go to the Update Opportunity action → set Monetary Value using a custom field or a fixed amount, and set Close Date using the "Add Days to Current Date" formula.
Step 5: Set Up a Stale-Deal Notification
Even the best pipeline has deals that go cold without you noticing. Create a workflow that checks: if an opportunity has been in the same stage for more than X days, send you an internal notification.
Use a Time Delay action (e.g., 3 days), followed by a condition check — if the stage hasn't changed, fire a Slack or email alert to yourself with the contact name and stage. Now nothing hides in "Proposal Sent" for three weeks without you knowing.
Common Mistakes to Avoid
- Running two conflicting sequences at once. When a lead moves to "Won," you must remove them from all other active workflows. Use the "Remove from Workflow" action explicitly — don't rely on it happening automatically.
- Using Opportunity Created instead of Stage Changed. These are different triggers. Stage Changed fires on every move, including back-moves. Add a filter for the exact stage you want or you'll double-fire.
- Not testing with a real contact. Always run through the full pipeline manually with a test contact before going live. GHL's workflow history shows you exactly which actions fired and when.
- Skipping the "Lost" workflow. Most coaches set up the win flow and ignore the loss flow. A good nurture sequence on lost deals recovers 10–15% of them within 90 days. That's revenue you're currently leaving behind.
What This Looks Like When It's Running
When Harsh Sharma runs a fully automated pipeline at Systrify, here's what a typical lead journey looks like with zero manual intervention: Lead opts in → instantly enters pipeline at "New Lead" → receives intro SMS and email → books call → moves to "Call Booked" automatically → gets confirmation and reminders → call happens → moves to "Call Completed" → receives proposal email → follows up 3 days later → pays → moves to "Won" → all sequences stop → onboarding starts.
The only time a human touches the deal is to show up for the call and send the invoice. Everything else runs itself.
Your Pipeline Is Leaking Deals Right Now
If you don't have stage-based automation firing on every move, you're losing leads between the cracks every day. Book a free GHL audit and Harsh Sharma will map out exactly where your pipeline is breaking — and show you the fix.
Book Your Free GHL Audit →If this hit a nerve, that is exactly what I fix. I build done-for-you automation systems — GHL funnels, HubSpot CRM, WhatsApp, WordPress and Make/Zapier — for coaches and founders who are done running their business by hand. You bring the problem; I build the system that handles it.