On a schedule
Flag stalled HubSpot deals with a suggested follow-up
Each weekday, deals that have gone quiet for two weeks are listed in your Stalled deals sheet with a suggested follow-up, and owners get a Slack nudge.
- Runs
- On a schedule
- Apps
- Google Sheets, HubSpot
- AI
- Yes, uses the built-in AI allowance
- Access
- HubSpot deals read; Sheets edit
Send this to your assistant
Create a ClickRuntime automation: every weekday morning, find HubSpot deals with no activity for 14 days, draft a follow-up for each, log them in my 'Stalled deals' sheet and post the list to Slack for the owners.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
In a busy pipeline, a deal that's gone quiet for two weeks doesn't look urgent until it's lost. Reps have the best intentions to follow up, but finding the stalled ones means filtering HubSpot by last activity and then deciding what to say to each.
This does the finding and the first draft. Every weekday morning it lists the deals that have gone quiet, writes a suggested follow-up for each based on the deal, logs them in a shared sheet and nudges the team in Slack, so restarting a conversation takes minutes.
What you get out of it
Stalled deals surface on their own
Deals that drift past 14 days without activity are flagged, before they quietly die.
A ready-made message for each
AI suggests a short follow-up using the deal name, stage and amount, so the rep starts from a draft.
A record managers can review
The sheet keeps a dated log of every stalled deal and what was suggested.
Each deal flagged once per stall
A deal is listed once until it sees new activity, so the sheet doesn't repeat the same names daily.
How it works
What happens, step by step
Every weekday at 8 a.m., ClickRuntime looks for open HubSpot deals with no activity for 14 days.
It skips deals it has already flagged during this quiet spell.
AI writes a short suggested follow-up for each deal based on its name, stage and amount.
Each deal is added to your Stalled deals sheet, and the list is posted to your Slack sales channel.
Before it runs live
- Connect your Google Sheets account and pick the spreadsheets it may use
- 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
- Change what the AI looks for, or how it writes the result
- Add another app, for example also send it to Slack
- Combine it with other Google Sheets and HubSpot steps into one automation
Under the hood
The code that runs this automation
import time
from datetime import date
from google.oauth2.credentials import Credentials
from googleapiclient.discovery import build
from clickruntime import on_trigger, credentials, http, ai, notify, state
SHEET_ID = "1AbCdEfGhIjKlMnOpQrStUvWxYz"
def hs(method, path, **kw):
r = http.request(method, f"https://api.hubapi.com{path}", headers={"Authorization": f"Bearer {credentials.connection('hubspot', 'work')}"}, **kw)
return r.raise_for_status() or (r.json() if r.content else {})
@on_trigger
def run(event):
cutoff = str(int((time.time() - 14 * 86400) * 1000))
deals = hs("POST", "/crm/v3/objects/deals/search", json={"filterGroups": [{"filters": [{"propertyName": "hs_is_closed", "operator": "EQ", "value": "false"},
{"propertyName": "notes_last_updated", "operator": "LT", "value": cutoff}]}], "properties": ["dealname", "dealstage", "amount", "notes_last_updated"], "limit": 50})["results"]
flagged = state.get("flagged") or {}
new = [d for d in deals if flagged.get(d["id"]) != d["properties"].get("notes_last_updated")]
if not new:
return {"stalled": 0}
rows = []
for d in new:
p = d["properties"]
tip = ai.generate(f"Suggest a 2-sentence follow-up email to restart this stalled deal: {p['dealname']}, stage {p['dealstage']}, amount {p.get('amount')}.", max_output_tokens=120).text.strip()
rows.append([date.today().isoformat(), p["dealname"], p.get("amount"), p["dealstage"], tip])
flagged[d["id"]] = p.get("notes_last_updated")
build("sheets", "v4", credentials=Credentials(credentials.connection("google", "work")), cache_discovery=False).spreadsheets().values().append(
spreadsheetId=SHEET_ID, range="Stalled deals!A1", valueInputOption="RAW", body={"values": rows}).execute()
notify.slack(f"{len(new)} deals have gone quiet for 14 days:\n" + "\n".join(f"- {r[1]} ({r[2]}): {r[4]}" for r in rows), channel="#sales")
state.set("flagged", flagged)
return {"stalled": len(new)}FAQ
Common questions
How is a stalled deal defined?
Does it send the follow-up to the customer?
Who is mentioned in Slack?
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
Track weekly HubSpot lifecycle numbers in a sheet
Every Monday a new row in your Pipeline metrics sheet shows how many contacts reached each lifecycle stage last week, split by source.
See how it worksLog a weekly HubSpot revenue forecast in a sheet
Every Monday your weighted pipeline forecast is added to your Forecast sheet and you get an email with the highlights.
See how it worksEnrich companies from a sheet and update HubSpot
Companies you add to your Enrich sheet are researched, created or updated in HubSpot with industry, size and a summary, and the row is marked done.
See how it worksKeep exploring
Set up “Flag stalled HubSpot deals with a suggested follow-up” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.