This article provides a complete, practical walkthrough of the Schedule Http Send Webhook n8n agent. It connects HTTP Request, Webhook across approximately 1 node(s). Expect a Intermediate setup in 15-45 minutes. One‑time purchase: €29.

What This Agent Does

This agent orchestrates a reliable automation between HTTP Request, Webhook, handling triggers, data enrichment, and delivery with guardrails for errors and rate limits.

It streamlines multi‑step processes that would otherwise require manual exports, spreadsheet cleanup, and repeated API requests. By centralizing logic in n8n, it reduces context switching, lowers error rates, and ensures consistent results across teams.

Typical outcomes include faster lead handoffs, automated notifications, accurate data synchronization, and better visibility via execution logs and optional Slack/Email alerts.

How It Works

The workflow uses standard n8n building blocks like Webhook or Schedule triggers, HTTP Request for API calls, and control nodes (IF, Merge, Set) to validate inputs, branch on conditions, and format outputs. Retries and timeouts improve resilience, while credentials keep secrets safe.

Third‑Party Integrations

• HTTP Request
• Webhook

Import and Use in n8n

1. Open n8n and create a new workflow or collection.
2. Choose Import from File or Paste JSON.
3. Paste the JSON below, then click Import.
4. Show n8n JSON

   Title:
   Automated Follow-Up Workflow with n8n: Re-Engage Leads via HubSpot and Gmail
   
   Meta Description:
   Learn how to create an automated sales follow-up workflow using n8n, Gmail, and HubSpot. This guide explains how to re-engage leads who've only been contacted once and haven’t responded in over a month.
   
   Keywords:
   n8n automation, HubSpot follow-up, Gmail outreach, sales automation, email marketing, CRM automation, HubSpot contact engagement, n8n HubSpot workflow, Gmail integration, lead re-engagement
   
   Third-Party APIs Used:
   - HubSpot CRM API (via OAuth 2.0)
   - Gmail API (via OAuth 2.0)
   
   Article:
   
   Re-Engaging Leads with n8n: Automating Personalized Sales Follow-Ups Using HubSpot and Gmail
   
   Consistent follow-up is one of the most crucial yet under-prioritized aspects of sales. Often, potential leads engage once—and then the momentum drops. What if you could build an automated system that identifies which leads haven’t heard from you in over a month, checks whether they’ve only been contacted once, and then sends them a personalized follow-up email? Even better—what if it logged the interaction in your CRM platform?
   
   This is exactly what the no-code tool n8n can help you achieve with a powerful sales automation workflow that connects HubSpot and Gmail.
   
   In this article, we’ll break down how an n8n workflow automatically sends follow-up emails to specific HubSpot contacts and tracks engagement back in the CRM. The process removes manual pipeline management and ensures you never miss an opportunity to reignite a sales conversation.
   
   Overview of the Workflow
   
   Every day at 9:00 AM, this n8n automation executes the following steps:
   
   1. 🧑‍💼 Fetch HubSpot contacts with a recorded "last contact date".
   2. 📆 Filter only those leads who haven’t been contacted in over 30 days.
   3. 📊 Check whether they’ve only been engaged once before.
   4. 📧 Send a personalized follow-up email using Gmail.
   5. 📝 Record the engagement back in HubSpot to update their contact log.
   
   Let’s break down how each of these actions is implemented in the n8n workflow.
   
   Step 1: Scheduled Daily Trigger
   
   The workflow is initiated by an n8n Schedule Trigger node, set to run once every day at 9 AM. This ensures timely and regular follow-ups without needing anyone to manually initiate them.
   
   Step 2: Fetch Previously Contacted Leads in HubSpot
   
   Using the HubSpot node, the workflow searches the CRM for all contacts who have a known last contact date. The contacts are sorted in ascending order based on the "notes_last_contacted" field, prioritizing those who were contacted a long time ago.
   
   In terms of integration, this uses the HubSpot CRM API with OAuth 2.0 credentials, so make sure your authorization and scope settings are configured properly in n8n.
   
   Step 3: Filter Contacts Last Engaged Over One Month Ago
   
   A condition node (“If”) checks if the contact's last engagement was more than 30 days ago using datetime logic. Only those that match this criterion proceed through the workflow.
   
   This part ensures you're following up just once a month, which avoids over-communicating while keeping the lead warmed up.
   
   Step 4: Check Engagement History from HubSpot
   
   Next, an HTTP Request is made using the HubSpot CRM API to pull the number of existing engagements tied to a contact. Another conditional ("If") node checks whether this count equals exactly one previous engagement—meaning the contact has been reached once and is ready for a second touchpoint.
   
   This logic is particularly valuable in adjusting your communication cadence. For example, if a contact has already received several messages, you might choose a different approach or stop follow-ups altogether.
   
   Step 5: Customize and Send Gmail Email
   
   If the prior criteria are met, the workflow uses a Set node to generate a custom email, inserting the contact’s first name and a personalized message encouraging them to revisit your product offering: n8n. The subject is set to "Follow up on n8n", and the email body includes a polite nudge—and your name, Mutasem, for that human touch.
   
   The Gmail node then sends the email via your authenticated Gmail account using OAuth 2.0. The sender’s name appears as “Mutasem from n8n”, keeping the brand voice consistent.
   
   Step 6: Log Engagement in HubSpot
   
   To close the loop, the final HubSpot node logs this outreach as an email-type engagement on the contact’s record, thereby updating the "last contacted" field. This step ensures that future runs of the workflow won't include this contact again until another month passes.
   
   The engagement is logged with metadata including sender/recipient emails, subject, body, and contact association.
   
   Added Notes & Tips
   
   - Enrich Your Filtering: You can expand the logic to account for multiple engagement types (calls, notes, tasks) and decide whether to follow up depending on interaction types.
   - Customize Templates: You can A/B test subject lines or tweak email content based on lead segmentation, all within this n8n flow.
   - OAuth 2.0 Configuration: As noted in the sticky notes within the workflow, careful attention must be paid to scope selection when integrating with HubSpot’s and Gmail’s OAuth APIs.
   
   Conclusion
   
   With this automated n8n workflow, you’re not only ensuring timely follow-ups but also building a sustainable, repeatable sales cadence that nurtures leads and keeps your contact records clean and current. By combining HubSpot’s rich CRM platform with Gmail’s messaging capabilities and n8n’s flexible automation engine, your CRM becomes your most powerful sales assistant—working every day at 9 AM sharp.
   
   Whether you're an SDR looking to scale personalized outreach or a founder wearing multiple hats, this solution ensures contacts don’t fall through the cracks and helps move them further down the sales funnel—automatically.
   
   Ready to supercharge your lead engagement? Spin up your n8n instance and let automation do the talking.

5. Set credentials for each API node (keys, OAuth) in Credentials.
6. Run a test via Execute Workflow. Inspect Run Data, then adjust parameters.
7. Enable the workflow to run on schedule, webhook, or triggers as configured.

Tips: keep secrets in credentials, add retries and timeouts on HTTP nodes, implement error notifications, and paginate large API fetches.

Validation: use IF/Code nodes to sanitize inputs and guard against empty payloads.

Why Automate This with AI Agents

AI‑assisted automations offload repetitive, error‑prone tasks to a predictable workflow. Instead of manual copy‑paste and ad‑hoc scripts, your team gets a governed pipeline with versioned state, auditability, and observable runs.

n8n’s node graph makes data flow transparent while AI‑powered enrichment (classification, extraction, summarization) boosts throughput and consistency. Teams reclaim time, reduce operational costs, and standardize best practices without sacrificing flexibility.

Compared to one‑off integrations, an AI agent is easier to extend: swap APIs, add filters, or bolt on notifications without rewriting everything. You get reliability, control, and a faster path from idea to production.

Best Practices

• Credentials: restrict scopes and rotate tokens regularly.
• Resilience: configure retries, timeouts, and backoff for API nodes.
• Data Quality: validate inputs; normalize fields early to reduce downstream branching.
• Performance: batch records and paginate for large datasets.
• Observability: add failure alerts (Email/Slack) and persistent logs for auditing.
• Security: avoid sensitive data in logs; use environment variables and n8n credentials.

FAQs

Can I swap integrations later? Yes. Replace or add nodes and re‑map fields without rebuilding the whole flow.

How do I monitor failures? Use Execution logs and add notifications on the Error Trigger path.

Does it scale? Use queues, batching, and sub‑workflows to split responsibilities and control load.

Is my data safe? Keep secrets in Credentials, restrict token scopes, and review access logs.