AI-driven lead classification & routing with HighLevel and Azure GPT-4o-mini
Description:
Streamline your lead management process with this AI-driven n8n automation template. The workflow fetches opportunities from HighLevel (GHL), enriches them with contact details, and uses Azure OpenAI GPT-4o-mini to analyze each lead’s intent (e.g., Demo Request, Support Query, or Partnership Inquiry). It then automatically routes the lead to the right internal team via email, ensuring instant follow-up and zero delays in response time. Perfect for sales, support, and partnership teams who want to save time on manual triage and ensure every inquiry reaches the correct department within seconds.
✅ What This Template Does (Step-by-Step)
⚡ Manual or Scheduled Trigger Run the workflow manually for on-demand classification or schedule it to execute periodically.
📥 Fetch Opportunities from HighLevel Retrieves all opportunities from your GHL CRM, serving as the starting dataset for AI-powered intent detection.
👤 Fetch Detailed Contact Information Enriches each opportunity with full contact details such as name, email, and message notes.
🧠 AI-Powered Lead Classification Uses Azure OpenAI GPT-4o-mini via the LangChain AI Agent to analyze the lead’s message and determine the intent. Possible outputs include:
- 🎯 Demo Request
- 🛠️ Support Query
- 🤝 Partnership Inquiry
- 🧾 Post-Processing of AI Response JavaScript logic parses and formats the AI’s output into actionable data for conditional routing.
🔀 Intelligent Routing to Relevant Teams
- Demo Requests → demo@company.com
- Support Queries → support@company.com
- Partnership Inquiries → partnership@company.com Each email includes full contact info and original message context.
📧 Instant Team Notifications Sends neatly formatted emails from a centralized sender (noreply@company.com) to ensure smooth handoff and accountability.
🧠 Key Features
🤖 AI intent classification using Azure OpenAI GPT-4o-mini 🔀 Automated lead routing via email 📋 Structured data enrichment from HighLevel ⚙️ Smart conditional logic for 3 lead categories 📩 End-to-end automation from CRM intake to response
💼 Use Cases
📞 Automatically route demo requests to the sales team 🛠️ Send support-related queries directly to helpdesk 🤝 Forward partnership inquiries to business development 💡 Reduce response delays and manual triage errors
📦 Required Integrations
HighLevel (GHL) – for opportunity and contact data Azure OpenAI – for AI-driven lead classification SMTP / Gmail – for team routing email notifications
🎯 Why Use This Template?
✅ Automates manual lead sorting and tagging ✅ Ensures every inquiry reaches the right team ✅ Increases response speed and lead conversion ✅ Scalable AI logic adaptable to any organization
AI-Driven Lead Classification & Routing with HighLevel and Azure GPT-4o Mini
This n8n workflow automates the process of classifying leads using an AI agent and then routing them within HighLevel based on the classification. It leverages Azure OpenAI's GPT-4o Mini for intelligent lead analysis and provides a mechanism for human review via email.
What it does
This workflow performs the following key steps:
- Manual Trigger: The workflow is initiated manually, allowing for on-demand lead processing or testing.
- AI Agent for Lead Classification: An AI Agent, powered by an Azure OpenAI Chat Model (likely GPT-4o Mini, as suggested by the directory name), analyzes lead information to classify it.
- Conditional Routing: Based on the AI agent's classification, the workflow uses an 'If' node to route the lead.
- HighLevel Integration (Success Path): If the lead meets specific criteria (e.g., classified as "qualified" or "high-priority"), it is processed and updated within HighLevel.
- Email Notification (Review Path): If the lead's classification requires human review or falls into a specific category, an email is sent for manual intervention.
- Code Node (Potential Data Transformation): A 'Code' node is present, suggesting custom logic or data transformation might be applied at some point in the workflow, though its exact position in the connections is not defined in the provided JSON.
- Sticky Note: A sticky note is included, likely for documentation or instructions within the workflow canvas.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance.
- Azure OpenAI Account: Access to Azure OpenAI with a deployed GPT-4o Mini model (or similar chat model).
- HighLevel Account: An active HighLevel account with appropriate API access.
- SMTP Credentials: SMTP server details for sending email notifications.
Setup/Usage
- Import the Workflow: Import the provided JSON into your n8n instance.
- Configure Credentials:
- Azure OpenAI Chat Model: Configure the 'Azure OpenAI Chat Model' node with your Azure OpenAI API key, endpoint, and model deployment name.
- HighLevel: Set up your HighLevel credentials within the 'HighLevel' node.
- Send Email: Configure the 'Send Email' node with your SMTP server details, sender email, and recipient email for notifications.
- Customize AI Agent: Adjust the prompt and tools within the 'AI Agent' node to accurately classify your leads based on your specific criteria.
- Define 'If' Conditions: Modify the 'If' node to define the conditions for routing leads to HighLevel or triggering an email notification.
- Customize HighLevel Actions: Configure the 'HighLevel' node to perform the desired actions (e.g., create a contact, update a lead, add to a campaign) based on the AI classification.
- Run the Workflow: Execute the workflow manually using the 'Manual Trigger' to test and verify its functionality.
Related Templates
Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets
This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.
By Ranjan DailataGenerate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax
Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions
By Daniel NkenchoAutomate Dutch Public Procurement Data Collection with TenderNed
TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte
By Wessel Bulte