How Do You Build a Stale Deal Alert in HubSpot?

How do you get HubSpot to tell you when a deal goes quiet?

Build a deal-based workflow that enrolls open deals whose last activity date is older than a set number of days, then sends the deal owner a task and a notification. The setup itself is short. The hard part is not the clicks. It is deciding what "stale" means for your sales process.

Stale deals are the quiet leak in most small pipelines. A rep gets busy, a buyer stops replying, and the deal sits in "Proposal sent" for six weeks while the forecast still counts it. Nobody notices until the end of the quarter, when it is too late to rescue.

This tutorial is for a founder or sales lead running HubSpot with a small team who wants a simple, reliable nudge. I will walk through how I would define stale, build the workflow, avoid the common traps, and check that it actually works.

What counts as a stale deal?

A stale deal is an open deal with no meaningful activity for longer than your normal gap between touches. That gap depends on the stage. A deal in early discovery might go stale after seven days of silence. A deal waiting on legal review might reasonably sit for two or three weeks.

Write your thresholds down before you build anything. I usually start with one number for the whole pipeline, such as fourteen days, because it is simple and gets the alert running. Once the team trusts it, I split the threshold by stage. One alert that fires correctly beats five clever ones that nobody believes.

Also decide what counts as activity. In HubSpot, the deal's Last activity date tracks the most recent past note, call, logged or tracked sales email, meeting, and similar records on the deal. If your reps work mostly in another tool and never log activity in HubSpot, this property will be empty or wrong, and the alert will fire on healthy deals.

What do you need before you start?

You need a HubSpot subscription that includes workflows, a pipeline with clear open and closed stages, and deal owners set on every open deal. HubSpot's documentation lists workflows on Professional and Enterprise tiers of its hubs, so check your plan first. Without workflows, you can still filter your deals by last activity date and check that view every week.

Check deal ownership next. The Deal owner property is the user the deal is assigned to, and the alert will go to that person. Filter your pipeline for open deals with no owner and fix them before you turn anything on. An alert sent to nobody is the same as no alert.

Finally, spot-check activity logging. Open five deals you know are active and confirm their Last activity date looks right. If it does not, fix the logging habit or the email integration first. This step saves you from a week of false alarms that teaches the team to ignore the alert.

How do you build the workflow step by step?

Create a new deal-based workflow from scratch. Set the enrollment trigger to deals in your open stages whose Last activity date is more than your chosen number of days ago. Then add actions that create a follow-up task for the deal owner and send them a notification. Turn it on after a test.

Start in the Workflows tool and choose a deal-based workflow. For the enrollment trigger, use filter criteria. Add a filter on Deal stage set to any of your open stages, so closed-won and closed-lost deals never enroll. Add a second filter on Last activity date using the "is more than" a number of days ago option, and enter your threshold.

Next, add the actions. I use a Create task action assigned to the deal owner, with a title like "Deal quiet for 14 days: next step?" and a due date of today. Then I add a Send internal email notification action or a Send in-app notification action to the deal owner, so the task does not sit unseen. HubSpot's docs describe both actions, and the email version works with all workflow types.

If you want a manager to see the pattern too, add a second notification to the sales lead. Keep it to the owner at first, though. Copying the manager on every alert can feel like surveillance, and reps tend to respond better to a private nudge.

Why might the alert fire late or not at all?

Because date filters are checked on a schedule, not instantly, and because empty values behave differently. HubSpot's documentation says triggers using "is more than" or "is less than" a number of days ago are checked at the start of the day, which can delay enrollment. A deal can cross your threshold mid-morning and enroll the next day.

That delay is fine for this use case. A stale deal alert does not need to be instant. It just needs to be reliable. If your team expects the nudge at a precise hour, set that expectation clearly so nobody thinks the workflow is broken.

Empty values are the bigger trap. A deal that never had any logged activity has no Last activity date at all, and a "more than X days ago" filter may not catch it. Test this directly by creating a deal with no activity and checking whether it enrolls. If it does not, add a separate trigger branch for deals where the date is unknown and the deal was created more than X days ago.

How do you make the alert fire again if the deal stays quiet?

Turn on re-enrollment carefully, or use a schedule. HubSpot's documentation notes that activities cannot be used as re-enrollment triggers. That means you cannot simply say "re-enroll when activity is logged." The cleanest approach for a recurring nudge is a weekly review step, or a scheduled workflow if your account offers schedule-based enrollment.

In practice, I prefer one alert per quiet stretch and then a human check-in. If a deal triggers the alert and the rep does nothing, the next useful step is a conversation in the weekly pipeline review, not a second automated email. Repeated alerts on the same deal quickly turn into noise.

If you do want a repeat and your account supports schedule-based enrollment, a weekly workflow that enrolls deals matching the same stale criteria works well. Check HubSpot's current docs for how scheduled triggers behave on your plan. It acts like a standing reminder. Test it against a small group first so you can see exactly how many alerts each rep will get.

How do you set different thresholds for each stage?

Use branches or separate workflows, one per stage group. HubSpot tracks a Date entered current stage and a Time in current stage property on deals. Combining those with Last activity date lets you flag a deal that has both sat in one stage too long and had no recent touch.

I like a two-signal rule for later stages. A deal in "Contract sent" is stale if it has been in that stage for more than fourteen days and has had no activity for seven. Either signal alone can be normal. Both together usually mean the deal is slipping and nobody has noticed.

Keep the number of variations small. Two or three stage groups with their own thresholds cover most small pipelines. Every extra branch is another thing to maintain when you change your stages later, so add them only when the simple version has proved itself.

How do you know the alert is working?

Track how many alerts fire each week and what happens next. A healthy alert produces a handful of tasks per rep, most of which get completed or turn into a closed-lost decision. If tasks pile up untouched, the threshold is too tight or the team does not trust the signal.

Review the first two weeks closely. Open every enrolled deal and ask whether it really was stale. If many were false alarms, check activity logging and adjust the threshold. If real stale deals did not enroll, check the empty-value case and the stage filter.

The best outcome is honest pipeline. A stale alert often leads to more deals moving to closed-lost, and that is a good thing. A smaller pipeline you believe is far more useful for forecasting than a large one padded with deals nobody is working. An alert tells you a deal is stuck, and deciding what to do next is covered in when to disqualify a deal instead of chasing it.

What should you do next?

Pick one threshold, check deal ownership and activity logging, and build the basic workflow with a task and a notification. Test it with a deal you know is quiet and one with no activity at all. Run it for two weeks, review every alert, then add stage-specific thresholds if you need them.

Once stale deals start closing out, you will want to know why they were lost, so pair this with a lost deal reason report in HubSpot. If your stages are loose and deals move without the right data, tighten them first with required properties on HubSpot deal stages.

This is one of the smallest automations I build for sales teams, and one of the most useful. If you want help setting it up or connecting it to a wider pipeline review, reach out and let's chat.