This article provides a complete, practical walkthrough of the Schedule Filter Create Scheduled 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:**  
   Building a Real-Time High-Value Lead Alert System with n8n, HubSpot, and Slack
   
   **Meta Description:**  
   Learn how to automate lead notifications using n8n by integrating HubSpot and Slack. This workflow monitors new company leads every 5 minutes and alerts your sales team about leads with over $5M in revenue.
   
   **Keywords:**  
   n8n, automation, HubSpot, Slack, sales automation, lead tracking, real-time notifications, workflows, business automation, lead scoring
   
   ---
   
   ## Building a Real-Time High-Value Lead Alert System with n8n, HubSpot, and Slack
   
   Responding quickly to new leads is essential in high-stakes sales environments. What if your sales reps could be immediately notified when a high-value company lead appears in your CRM? Thanks to modern workflow automation tools like n8n and integrations with popular platforms like HubSpot and Slack, this fast-response system is simple to set up—and even easier to scale.
   
   In this article, we’ll explore a real-world n8n workflow that automatically checks for new company leads every five minutes in HubSpot, filters for those exceeding $5 million in revenue, and notifies a designated sales representative in Slack. It’s a powerful, real-time solution for improving time-to-contact and prioritizing top-tier leads.
   
   ---
   
   ## The Workflow Overview
   
   This workflow is built in [n8n](https://n8n.io), a powerful open-source workflow automation tool. Here’s a step-by-step breakdown of how this system works:
   
   ### 1. Time-Based Trigger
   
   The workflow kicks off with a Schedule Trigger node configured to execute every five minutes.
   
   Node: `Trigger every 5 minutes`
   
   There are no complicated configurations here—just a repeating interval that ensures your system stays responsive to incoming leads.
   
   ### 2. Retrieve Recently Created or Updated Companies from HubSpot
   
   Next, we interact with the HubSpot API to pull the latest company records created or updated in the past five minutes.
   
   Node: `Get leads created last 5 minutes`  
   API Call: HubSpot CRM (Company Search)
   
   Using the `getRecentlyCreatedUpdated` operation, the node fetches all companies added or updated within the last five minutes. This ensures that the data is fresh and aligns precisely with the polling interval.
   
   💡 Note: The `since` parameter is dynamically calculated using `{{$now.minus({ "minutes": 5 })}}` to stay synced with the workflow trigger. This is crucial to avoid duplicate or missed leads.
   
   ### 3. Filter High-Revenue Leads
   
   Not every lead deserves immediate attention. To ensure our reps only get alerts on big opportunities, a filter ensures only companies with annual revenue over $5 million are allowed to pass through.
   
   Node: `Keep the ones that make more than $5M in revenue`
   
   This node checks the `annualrevenue` property of each company record and uses a strict numerical comparison (`gt` operation) to include only those with a value greater than 5,000,000.
   
   🔍 Bonus Tip: You can enhance this filter to include multiple conditions—like employee count, geographic location, or industry!
   
   ### 4. Notify a Sales Rep in Slack
   
   The final leg of this automation pipeline is a direct message to the sales rep via Slack.
   
   Node: `Notify sales rep`  
   API Call: Slack (Chat Post Message)
   
   The message includes the company name, website, annual revenue, and number of employees—helpful context for reps to evaluate the lead quickly.
   
   Message Template:
   
   ```
   New high-quality lead 🤑  
   *Company Name*: {{ $json.properties.name.value }}  
   *Website*: {{ $json.properties.website.value }}  
   *Revenue*: {{ $json.properties.annualrevenue.value }}  
   *Number of employees*: {{ $json.properties.numberofemployees.value }}
   ```
   
   This kind of instantaneous alert is a game-changer for sales teams trying to connect with potential clients at the peak of their interest.
   
   ---
   
   ## Setup Considerations
   
   Included sticky notes throughout the workflow provide helpful setup reminders such as:
   
   - Adding HubSpot and Slack API credentials via OAuth2.
   - Ensuring the polling time and the `since` parameter match.
   - Optionally tuning lead criteria within the filter node to suit your organization’s goals.
   
   ---
   
   ## Why Use This Workflow?
   
   This lead alert system offers several competitive advantages:
   
   - ⏱️ Faster Lead Response: Real-time alerts improve your chances of conversion.
   - 🎯 Quality Filtering: Only high-value leads get flagged, saving your team’s time.
   - 🤖 Low-Code Automation: Leverage n8n’s intuitive interface to automate without writing custom backend code.
   - 🔄 Scalability: Easily enhanced with more filters, enriched data, or multi-channel notifications (like email or CRM updates).
   
   ---
   
   ## Third-Party APIs Used
   
   This workflow integrates seamlessly with third-party services via API:
   
   - **HubSpot** – For retrieving company lead data (HubSpot CRM API)
   - **Slack** – For sending real-time notifications to team members (Slack Web API)
   
   ---
   
   ## Final Thoughts
   
   Automating intelligent lead notifications is just one of the many ways you can supercharge your sales pipeline using n8n. Whether you’re scaling a startup or optimizing an enterprise funnel, setting up real-time, data-driven alerts keeps your team proactive and ahead of the curve.
   
   So why wait to hear about promising leads hours later? With n8n, Slack, and HubSpot, you can start acting on them within minutes.
   
   ---
   
   Ready to build this yourself? With n8n’s no-code interface and robust integrations, you can have this up and running in under 30 minutes—no developer required. 🛠️

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.