Skip to main content

Re-engage HubSpot leads using Azure OpenAI GPT-4o, Gmail and Slack

Workflow preview

Workflow preview
100%
Re-engage HubSpot leads using Azure OpenAI GPT-4o, Gmail and Slack preview
Open on n8n.io

1. Workflow Overview

Description This workflow automates daily re engagement for HubSpot leads that were previously paused due to timing. It runs every 24 hours, fetches recent leads with activity data, and filters ...

Best for

  • Lead Nurturing automation workflows
  • Multimodal AI automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.scheduletrigger, n8n-nodes-base.hubspot, n8n-nodes-base.if, n8n-nodes-base.splitinbatches, @n8n/n8n-nodes-langchain.agent, n8n-nodes-base.code, n8n-nodes-base.gmail, n8n-nodes-base.slack

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Rahul Joshi.

Original n8n.io source

1.1 Workflow description

Title
Re-engage HubSpot leads using Azure OpenAI GPT-4o, Gmail and Slack
Workflow name
Re-engage HubSpot leads using Azure OpenAI GPT-4o, Gmail and Slack

📘 Description

This workflow automates daily re-engagement for HubSpot leads that were previously paused due to timing. It runs every 24 hours, fetches recent leads with activity data, and filters only those marked as “bad timing,” ensuring active opportunities are not disturbed. Qualified leads are processed in batches, and an AI agent generates a short, polite follow-up email designed to reopen the conversation without sounding salesy. Instead of sending automatically, the workflow creates a Gmail draft for human review and notifies the assigned owner in Slack. If AI generation fails, the workflow sends a Slack alert with the lead details so manual follow-up can still happen. This ensures consistent reactivation of cold leads without silent failures or missed opportunities.

⚙️ What This Workflow Does (Step-by-Step)

⏰ Daily Trigger (Every 24h) Runs the workflow once per day. 📥 HubSpot: Fetch Recent Leads + Activity Fields Pulls up to 20 leads with key activity and lifecycle properties needed for follow-up timing. 🚦 Filter: Lead Status = BAD_TIMING Keeps only leads that were previously paused due to timing (targets cold opportunities only). 🔄 Batch Leads (Split In Batches) Processes leads one-by-one / in batches to prevent rate-limit issues and keep execution stable. ✍️ AI: Generate Re-Engagement Follow-Up Email Body Creates a short, friendly follow-up message based on lead context (no CRM labels, no salesy tone). 🧩 Parse AI JSON Normalizes AI output into usable fields (subject/body/toEmail/owner details). 📩 Gmail: Create Follow-Up Draft Email Creates a Gmail draft (human-in-the-loop; no auto-send). 🔔 Slack: Notify Owner to Re-Engage Lead Notifies the assigned owner that a draft is ready and the lead is worth revisiting. ⚠️ Build AI Error Payload Builds a clean error context (lead name/email + AI error message). 🚨 Slack: Alert AI Draft Failure Alerts the owner when AI fails so the lead can be followed up manually.

🧩 Prerequisites

• n8n instance • HubSpot App Token (read access to leads + properties) • Azure OpenAI credentials (GPT-4o) for email generation • Gmail OAuth2 (draft creation permissions) • Slack API token (DM user messaging permissions)

💡 Key Benefits

✔ Daily automated re-engagement for paused leads ✔ Prevents random outreach to active leads ✔ Human-in-the-loop safety via Gmail drafts (no auto-send) ✔ Owner notifications ensure follow-up execution ✔ Batch processing avoids rate-limit instability ✔ Strong failure handling prevents silent lead drops

👥 Perfect For

  • SDR teams managing large HubSpot pipelines
  • Founders doing lightweight outbound follow-ups
  • Sales ops teams wanting structured reactivation loops
  • Agencies re-engaging cold inbound / outbound leads

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Daily Trigger (Every 24h)

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.1

Block 2 - HubSpot: Fetch Recent Leads + Activity Fields

Type / Role
n8n-nodes-base.hubspot - hubspot
Config choices
Version 2

Block 3 - Filter: Lead Status = BAD_TIMING

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.3

Block 4 - Batch Leads (Split In Batches)

Type / Role
n8n-nodes-base.splitInBatches - splitInBatches
Config choices
Version 3

Block 5 - AI: Generate Re-Engagement Follow-Up Email Body

Type / Role
@n8n/n8n-nodes-langchain.agent - agent
Config choices
Version 2.1

Block 6 - Parse AI JSON

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 7 - Gmail: Create Follow-Up Draft Email

Type / Role
n8n-nodes-base.gmail - gmail
Config choices
Version 2.1

Block 8 - Slack: Notify Owner to Re-Engage Lead

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.2

Block 9 - Slack: Alert AI Draft Failure

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.2

Block 10 - Build AI Error Payload

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 11 - Execute Re-Engagement Follow-Up Email Body with Azure OpenAI

Type / Role
@n8n/n8n-nodes-langchain.lmChatAzureOpenAi - lmChatAzureOpenAi
Config choices
Version 1

Block 12 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 13 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 14 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 15 - Sticky Note3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 16 - Sticky Note4

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 17 - Sticky Note5

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 18 - Sticky Note6

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 19 - Sticky Note7

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 20 - Sticky Note8

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

3. Summary Table

Workflow Re-engage HubSpot leads using Azure OpenAI GPT-4o, Gmail and Slack
Complexity advanced
Nodes 20
Categories Lead Nurturing, Multimodal AI
Author Rahul Joshi
Published 19 Feb 2026

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/13518/13518.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Re-engage HubSpot leads using Azure OpenAI GPT-4o, Gmail and Slack do?

Description This workflow automates daily re engagement for HubSpot leads that were previously paused due to timing. It runs every 24 hours, fetches recent leads with activity data, and filters ...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Lead Nurturing, Multimodal AI use case.