What it is.
Every hour the workflow queries HubSpot for contacts with a score under 50, checks a Google Sheet so the same person doesn't get alerted repeatedly, then notifies the record owner in Slack and creates a follow-up task in HubSpot.
A Gmail node sends a re-engagement email and the run logs back to Sheets. The dedupe sheet is the piece that makes it usable, because an hourly job with no memory becomes noise inside a day.
What you get.
- An hourly HubSpot query on a score threshold you set.
- A Google Sheets dedupe layer, so one contact triggers one alert.
- A Slack message aimed at the contact's own owner.
- A HubSpot task created against the record, so the follow-up exists in the CRM.
- A re-engagement email through Gmail, plus an activity log in Sheets.
How to set it up.
Connect HubSpot and confirm which score property you want queried, since accounts often carry more than one.
Set the threshold; the template comes set at under 50 and your own model may sit elsewhere.
Create the dedupe sheet with the columns the template expects and point the Sheets nodes at it.
Add Slack and check the owner lookup returns a user, because an unowned contact has nobody to notify.
Rewrite the Gmail re-engagement email, since a generic one costs you more than silence.
Set the schedule to hourly, watch the first day, and raise the threshold if the volume is high.
Use cases
Work the leads nobody looks at
Query on a score threshold hourly and put the low scorers in front of someone.
One contact, one alert
Use the sheet as a dedupe layer so a repeat submission does not ping twice.
Set the threshold yourself
Move the score line until the alert volume matches what a rep can handle.
Best for
A scored database that decays
Leads that were warm and cooled are cheaper to work than new ones, and nothing surfaces them by default.
Owner accountability
The alert goes to the person who owns the record, so it lands as a task and not a report.
Recycling MQLs
A task in the CRM plus one email covers most of what a recycling process needs.