Daily
Find deals stuck in one stage too long
Each morning you see the open deals that haven't moved in two weeks, before they go cold.
- Runs
- Daily
- Apps
- HubSpot
- AI
- Not needed
- Access
- crm.objects.deals.read
Send this to your assistant
Create a ClickRuntime automation: every weekday at 9am, send me a Slack message listing HubSpot deals that have been in the same stage for more than 14 days, with owner and amount.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
A deal that has sat in Proposal for two weeks is not a deal, it is a liability on the forecast. In HubSpot such deals stay green on the board, since nothing flags that nobody has touched them. Reps focus on the new and the exciting, the quiet ones age quietly, and the quarter ends with $200,000 in pipeline that was never going to close, discovered only when it fails to convert.
Each day, open deals are searched and the date each entered its current stage is read. Deals that have sat longer than your limit, say 14 days in Proposal, are posted to Slack with the owner, amount and days in stage.
It suits managers who review pipeline hygiene and want stalled deals raised before they become forecast problems.
What you get out of it
Stalled deals get attention in time
A nudge on day 14 gives the rep a chance to re-engage, with a call or a new offer, while the buyer still remembers the conversation. Re-engaging early also shows buyers that you are attentive.
Forecasts become more honest
Deals that cannot move are visible, so leaders can discount them in their forecast instead of being surprised at quarter end. A more honest forecast protects credibility with the board and with finance partners.
Reps are reminded without a manager chasing
The post is a neutral prompt in a shared channel, which is easier to take than a private message asking why a deal has not moved. Public prompts feel impersonal and routine, which keeps the tone constructive instead of accusatory.
Dead deals are closed cleanly
Some stalled deals should be closed lost. Seeing them listed makes it easier to clean up the pipeline, which makes reports more reliable. Closing dead deals frees reps to focus on real ones, and sharper pipeline numbers make coverage ratios believable.
Process problems become visible
If many deals stall at the same stage, the issue may be the process, such as slow legal review, and not individual reps. Fixing a slow approval step benefits every future deal, not just one account.
How it works
What happens, step by step
Every morning, ClickRuntime reads your open HubSpot deals and the date each one entered its current stage.
It picks out deals that have sat in the same stage for more than 14 days, or the limit you set.
The list is posted to your Slack channel with each deal's stage, how many days it has been there, its owner and amount.
Before it runs live
- Connect HubSpot
What you get
Build your own
Need it to work differently?
Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.
Changes you can ask for
- Run it at a different time, more or less often, or only on weekdays
- Add an AI step, for example to summarize, sort or draft a reply
- Add another app, for example also send it to Slack
- Combine it with other HubSpot steps into one automation
Under the hood
The code that runs this automation
from datetime import datetime, timezone
from clickruntime import on_trigger, credentials, http, notify
DAYS = 14
@on_trigger
def run(event):
deals = http.post("https://api.hubapi.com/crm/v3/objects/deals/search",
headers={"Authorization": f"Bearer {credentials.connection('hubspot', 'work')}"},
json={"limit": 100, "properties": ["dealname", "dealstage", "amount", "hubspot_owner_id", "hs_v2_date_entered_current_stage"],
"filterGroups": [{"filters": [{"propertyName": "hs_is_closed", "operator": "EQ", "value": "false"}]}]}).json()["results"]
now, lines = datetime.now(timezone.utc), []
for d in deals:
p = d["properties"]
entered = p.get("hs_v2_date_entered_current_stage")
if entered:
days = (now - datetime.fromisoformat(entered.replace("Z", "+00:00"))).days
if days > DAYS:
lines.append(f"• {p['dealname']} · {p['dealstage']} for {days} days · owner {p.get('hubspot_owner_id')} · ${float(p.get('amount') or 0):,.0f}")
if lines:
notify.slack(f"Deals stuck more than {DAYS} days:\n" + "\n".join(lines), channel="#sales")
return {"stuck": len(lines)}FAQ
Common questions
How is the time in stage measured?
Can different stages have different limits?
Will the same deal be posted every day?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Get a weekly CSV of your HubSpot contacts
A full export of your contacts arrives in your inbox every week, ready to open in a spreadsheet.
See how it worksGet a daily list of overdue HubSpot tasks
Each weekday you get the tasks that are past due and not done, grouped by owner.
See how it worksGet a weekly list of customers at risk of leaving
Each Monday you get a ranked list of customers who look likely to churn, with a reason for each.
See how it worksKeep exploring
Set up “Find deals stuck in one stage too long” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.