If the CRM is HubSpot, choosing the right date properties removes most of the false alarms waqas mentioned.
For “nobody replied”, skip Last Activity Date (notes_last_updated), because notes and tasks move it. Last Contacted (notes_last_contacted) only moves when a call, sales email or meeting is logged, which is much closer to real contact with the client.
For “the deal sat untouched”, compare against the date the deal entered its current stage rather than the last modified date, which any sync bumps. HubSpot keeps a date-entered property for each stage; look up the internal names under Settings > Properties > Deal properties.
The filter that cuts the most noise is Next Activity Date (notes_next_activity_date). If a deal has a future task or meeting, someone already owns the next step. Only flag deals where it’s empty or already in the past.
In n8n that’s one HTTP Request with your HubSpot credential to POST /crm/v3/objects/deals/search:
{
"filterGroups": [{
"filters": [
{"propertyName": "dealstage", "operator": "IN", "values": ["<stage ids>"]},
{"propertyName": "notes_last_contacted", "operator": "LT", "value": "<now minus N days, epoch ms>"},
{"propertyName": "notes_next_activity_date", "operator": "NOT_HAS_PROPERTY"}
]
}],
"properties": ["dealname", "amount", "hubspot_owner_id", "notes_last_contacted"],
"limit": 100
}
Filter groups are OR’ed, so add a second group with notes_next_activity_date LT now to catch overdue next steps. Deals that were never contacted have no Last Contacted value and won’t match LT, so give them a group of their own.
For the alert, a HubSpot task for the deal owner works better than a Slack message. The task sets Next Activity Date, so the deal drops out of tomorrow’s check by itself and the same rep doesn’t get nagged twice.