GoHighLevel Stale Opportunity Trigger: Full Setup Guide

A deal that goes quiet in your pipeline doesn’t announce itself. Nobody gets an alert when a prospect stops replying to your rep’s follow-ups — the opportunity just sits in “Negotiation” or “Proposal Sent” until someone happens to scroll past it during a Monday pipeline review, weeks after the lead has already gone cold. GoHighLevel’s Stale Opportunities workflow trigger exists to close that gap: it watches every open opportunity in a pipeline and fires a workflow the moment one has gone untouched for longer than you’re willing to tolerate.

This is not a feature you toggle on. It’s a trigger you configure inside a workflow, with its own filters and its own quirks, and getting those settings wrong is why most agencies that “tried it once” ended up with either a flood of false-positive notifications or a trigger that never fires at all. Below is the configuration itself — where to find it, what each filter actually controls, and the escalation pattern that turns a stale-deal alert into a deal that gets saved instead of quietly closed-lost three months later.

What “Stale” Actually Means in GoHighLevel’s Pipeline

GoHighLevel doesn’t judge staleness by when the opportunity was created or by its dollar value. It measures time since the opportunity last saw activity in its current stage — a stage change, a field update, or a manual touch resets the clock. That distinction matters for how you’ll use the trigger: it’s built to catch opportunities that are stuck in one place, not opportunities that are simply moving slowly through a long pipeline. A deal that advances every two weeks through six stages will never trip a 10-day stale threshold, even if the whole cycle takes three months. A deal that has sat in “Negotiation” untouched for 10 days will trip it immediately, regardless of how new the opportunity is overall.

Two behaviors are worth knowing before you build anything. First, the duration only starts counting from when you add the trigger — it is not retroactive, so opportunities that have already been stale for weeks won’t fire the moment you turn this on; they’ll fire once they cross your threshold going forward. Second, if a stale opportunity gets touched and then goes quiet again, the trigger can fire again on the same opportunity. Build your downstream actions with that in mind, or you’ll end up notifying the same rep about the same deal every few weeks indefinitely.

Where to Build It

The trigger lives inside the standard workflow builder, not in pipeline settings:

• Open the sub-account and go to Automation → Workflows
• Click + Create Workflow and choose Start from Scratch (skip the recipe templates — none of them ship with this trigger pre-filtered for your pipeline)
• Click + Add New Trigger and search for Stale Opportunities (in some accounts this appears under the internal label Opportunity Decay — same trigger, check both names if the search comes up empty)
• Configure the filters, described below, then build your action sequence
• Click Save at the top — until you do, the whole workflow is an unpublished draft and nothing will fire, even if the toggle looks active

Configuring the Trigger Filters

Three filters control when this trigger fires, and all three should be set deliberately rather than left on whatever the builder defaults to:

Duration in Days. The number of days an opportunity can sit without activity before it counts as stale. There’s no universal correct number here — it should match how fast deals normally move for the pipeline you’re attaching it to, not a company-wide default. A threshold that’s too short trains reps to ignore the notifications; too long and deals go cold before anyone hears about it.

In Pipeline. Scope the trigger to one specific pipeline. If an agency account runs separate pipelines for new business and client renewals, a single stale-opportunity workflow covering both will need one duration to fit two very different sales motions, which usually satisfies neither. Build one workflow per pipeline instead.

Pipeline Stage. Restrict which stage(s) the trigger watches. This is the filter most setups get wrong by skipping it entirely, which lets the trigger fire on every stage in the pipeline including the ones where staleness doesn’t matter. Exclude Closed Won and Closed Lost outright — there’s nothing to rescue in a stage that’s already resolved, and leaving it in just generates noise.

Setting Different Thresholds by Stage

Because the trigger is scoped to a stage, nothing stops you from building several stale-opportunity workflows on the same pipeline, each watching a different stage with its own duration. That’s usually the right move: a lead sitting in “New Inquiry” for three days is a different problem than a proposal sitting untouched for three days, and treating them identically wastes the trigger’s precision.

Treat this table as a starting point to test against your own close-rate data, not a fixed rule. Pull up how long your won deals actually sat in each stage before you commit to a number, and verify current filter behavior in your account before rolling it out agency-wide — HighLevel updates this trigger’s options periodically.

The Actions Worth Stacking

A single email to the assigned rep is the minimum viable version of this workflow, and it’s also the version most agencies eventually replace, because a single email gets ignored the same way the original follow-up did. A stacked, escalating sequence performs better:

• Immediate: Send an Internal Notification to the assigned rep — a nudge, not a scolding, with a direct link back to the opportunity
• Same step or a short delay later: Add a task to the rep’s task list so the nudge has a concrete next action attached, not just a message that scrolls past
• If still untouched after a further delay: Escalate the Internal Notification to the rep’s manager or the account owner, so a deal doesn’t die simply because one person is out sick or overloaded
• Optional, for genuinely dead deals: Move the opportunity to a dedicated “Needs Review” or “Re-engage Later” stage rather than leaving it to rot in the active pipeline, which keeps your win-rate and pipeline-value reporting honest

Where GoHighLevel supports it in your plan, add a wait step between the first notification and the escalation rather than firing every action simultaneously — the point of stacking actions is to give the assigned rep a real window to act before anyone above them gets pulled in.

Building It Once, Deploying It to Every Client

If you manage this trigger across multiple client sub-accounts, build the canonical version once inside a template sub-account, then pull it into your agency snapshot. New client accounts inherit a working stale-opportunity workflow on day one instead of every onboarding starting from a blank workflow builder. The one thing a snapshot can’t do for you is set the Duration in Days and Pipeline Stage filters correctly for a client whose sales cycle you haven’t seen yet — treat those two filters as required edits on every new deployment, not defaults to leave untouched.

Mistakes That Quietly Break This Trigger

Most stale-opportunity workflows that get abandoned after a month fail for one of a few avoidable reasons:

• No stage filter set. The workflow fires on every stage in the pipeline, including ones where staleness is expected or irrelevant, and reps start muting the notifications.
• Closed stages left in scope. Closed Won and Closed Lost opportunities technically sit “stale” forever once resolved — exclude them explicitly.
• One threshold for a pipeline with wildly different deal sizes. A five-figure enterprise deal and a small one-off job don’t stall on the same schedule; a single duration setting will be wrong for one of them.
• No escalation path. A notification that only ever reaches the original rep repeats the exact failure mode it’s supposed to catch — the rep who already isn’t following up isn’t going to start because of an automated email.
• Duplicate triggers on the same opportunity. Running this alongside another workflow that also monitors the same stage can produce doubled notifications; check for overlap before publishing a second workflow on a pipeline that already has one.

Testing Before You Trust It

Before rolling this out on a live client pipeline, create a throwaway test opportunity, set its stage manually, and set the Duration in Days filter to something absurdly short — a fraction of a day, if the builder allows it — just to confirm the trigger fires and the actions execute in the order you built them. Reset the duration to its real value only after you’ve watched one full cycle succeed. Because the clock only starts once the workflow is saved, this is also the point to note the exact save time, so you know when to expect the first real firing on existing opportunities that were already sitting stale before you built the workflow.

Frequently Asked Questions

Does the Stale Opportunities trigger apply to opportunities that were already stale before I built the workflow?

No. The duration only starts counting from when the trigger is added and the workflow is saved. Opportunities that have already been sitting untouched for weeks won't fire immediately; they'll fire once they cross your threshold counting forward from that save point.

Can I use one Stale Opportunities workflow to cover an entire pipeline?

You can, but it usually produces worse results than scoping it to specific stages. A single duration setting rarely fits both an early qualifying stage and a late-stage negotiation equally well, so most working setups use a separate trigger per stage, or at least exclude Closed Won and Closed Lost explicitly.

What happens if an opportunity goes stale, gets touched, and then goes quiet again?

The trigger can fire again on the same opportunity once it re-crosses the duration threshold after the last update. Build your actions expecting repeat firings, or add a filter or tag check that stops the escalation from restarting indefinitely on the same deal.

Is Stale Opportunities the same as the missed call or missed opportunity notifications in GoHighLevel?

No. Missed call text-back responds to an unanswered inbound call in near real time. Stale Opportunities is a separate, slower-moving workflow trigger that watches for inactivity on an open pipeline opportunity over days, not seconds, and is built and configured inside the workflow automation builder rather than in phone or business profile settings.

We build your GoHighLevel account for you

CRM, pipelines, funnels, SMS and automation — configured for your business, not left for you to figure out.

• Setup (one-time)$850
• Ongoing (per month)$38.80

Get my free setup quote

No obligation quote · reply within 1 business day

This site is independently operated and is not officially affiliated with, endorsed by, or sponsored by HighLevel LLC. We do not receive referral commissions — this is our own flat-fee implementation service.