How to automate HubSpot lead follow-up with n8n (no code)
Most HubSpot lead-follow-up automations in n8n follow the same three-stage shape, whatever the specific business logic ends up being: capture, enrich, route.
Capture. A webhook trigger fires on a new form submission or deal-stage change, or, if you would rather not expose a public endpoint, a Schedule Trigger polls a saved HubSpot list every few minutes using the HubSpot node's search operation.
Enrich. Before anything gets written back to HubSpot, an HTTP Request node can call a third-party enrichment API (company size, industry, tech stack) or an AI node can summarize the lead's own website into a short lead-scoring note, which then gets written to a custom HubSpot property.
Route. A Switch node keyed on the lead score or source decides what happens next: high-score leads get a personalized outreach draft from an AI node, handed to a human to review before it goes out through Gmail or Outlook; lower-score leads get logged to a sheet for a weekly batch review instead of an individual email.
The review step matters more than it sounds. Auto-sending AI-drafted outreach without a human check is how good lead lists turn into spam complaints - keep a human in the loop for anything that actually sends, and use n8n only to prepare the draft and the context around it.
This same shape - capture, enrich, route - shows up across most of our lead-generation templates, just with different trigger sources and enrichment steps depending on where the lead originates.
Clean company profiles: Notion
Task automation on n8n: runs on a schedule across Notion, HubSpot and Slack, starting at "Pull Side A (HubSpot)". Diffs the two sides and writes only the gaps. 16 documented nodes.
Clean company profiles: HubSpot for conversational AI
Conversational AI on n8n: runs on a schedule across HubSpot, Slack, Google Sheets and MySQL, starting at "Read Pending Queue (HubSpot)". 24 documented nodes.
Augment company profiles: Slack for research assistant, scheduled
Research assistant on n8n: runs on a schedule across Slack, HubSpot and Google Sheets, starting at "Read Pending Queue (HubSpot)". Walks the list in batches, pausing between them. 16 documented nodes.
Augment contact records: Slack + approval pause
Multi-tool agent on n8n: runs on a schedule across Slack, Google Sheets and HubSpot, starting at "Read Pending Queue (HubSpot)". Walks the list in batches, pausing between them. 16 documented nodes.
Clean contact records with Slack & HubSpot
Research assistant on n8n: runs on a schedule across Slack and HubSpot, starting at "Keep Valid Requests". Branches on the check before anything is written. 18 documented nodes.
Augment company profiles for multi-tool agent
Multi-tool agent on n8n: runs on a schedule across Google Sheets, Slack, HubSpot and Google Drive, starting at "Pull Side A (HubSpot)". 23 documented nodes.
A handful of our HubSpot-integrated templates below already wire up this exact pattern, if you want a starting point instead of building the three stages from a blank canvas.
Browse all HubSpottemplates →Want structured practice? Our practice bundles arrange real, ready-to-import templates into a beginner-to-advanced curriculum.
Explore practice bundles →