AI orchestrator: dynamically selects models based on input type
This workflow is designed to intelligently route user queries to the most suitable large language model (LLM) based on the type of request received in a chat environment. It uses structured classification and model selection to optimize both performance and cost-efficiency in AI-driven conversations.
It dynamically routes requests to specialized AI models based on content type, optimizing response quality and efficiency.
Benefits
- Smart Model Routing: Reduces costs by using lighter models for general tasks and reserving heavier models for complex needs.
- Scalability: Easily expandable by adding more request types or LLMs.
- Maintainability: Clear logic separation between classification, model routing, and execution.
- Personalization: Can be integrated with session IDs for per-user memory, enabling personalized conversations.
- Speed Optimization: Fast models like
GPT-4.1 miniorGemini Flashare chosen for tasks where speed is a priority.
How It Works
-
Input Handling:
- The workflow starts with the "When chat message received" node, which triggers the process when a chat message is received. The input includes the chat message (
chatInput) and a session ID (sessionId).
- The workflow starts with the "When chat message received" node, which triggers the process when a chat message is received. The input includes the chat message (
-
Request Classification:
- The "Request Type" node uses an OpenAI model (
gpt-4.1-mini) to classify the incoming request into one of four categories:general: For general queries.reasoning: For reasoning-based questions.coding: For code-related requests.search: For queries requiring search tools.
- The classification is structured using the "Structured Output Parser" node, which enforces a consistent output format.
- The "Request Type" node uses an OpenAI model (
-
Model Selection:
- The "Model Selector" node routes the request to one of four AI models based on the classification:
- Opus 4 (Claude 4 Sonnet): Used for
codingrequests. - Gemini Thinking Pro: Used for
reasoningrequests. - GPT 4.1 mini: Used for
generalrequests. - Perplexity: Used for
search(Google-related) requests.
- Opus 4 (Claude 4 Sonnet): Used for
- The "Model Selector" node routes the request to one of four AI models based on the classification:
-
AI Processing:
- The selected model processes the request via the "AI Agent" node, which includes intermediate steps for complex tasks.
- The "Simple Memory" node retains session context using the provided
sessionId, enabling multi-turn conversations.
-
Output:
- The final response is generated by the chosen model and returned to the user.
Set Up Steps
-
Configure Trigger:
- Ensure the "When chat message received" node is set up with the correct webhook ID to receive chat inputs.
-
Define Classification Logic:
- Adjust the prompt in the "Request Type" node to refine classification accuracy.
- Verify the output schema in the "Structured Output Parser" node matches expected categories (
general,reasoning,coding,search).
-
Connect AI Models:
- Link each model node (Opus 4, Gemini Thinking Pro, GPT 4.1 mini, Perplexity) to the "Model Selector" node.
- Ensure credentials (API keys) for each model are correctly configured in their respective nodes.
-
Set Up Memory:
- Configure the "Simple Memory" node to use the
sessionIdfrom the input for context retention.
- Configure the "Simple Memory" node to use the
-
Test Workflow:
- Send test inputs to verify classification and model routing.
- Check intermediate outputs (e.g.,
request_type) to ensure correct model selection.
-
Activate Workflow:
- Toggle the workflow to "Active" in n8n after testing.
Need help customizing?
Contact me for consulting and support or add me on Linkedin.
AI Orchestrator: Dynamically Selects Models Based on Input Type
This n8n workflow acts as an intelligent AI orchestrator, dynamically selecting the most appropriate Large Language Model (LLM) based on the input received. It allows for flexible integration with various chat models (OpenAI, Anthropic, Google Gemini, OpenRouter) and can be configured to use either a basic LLM chain or a more complex AI agent, complete with memory and structured output parsing.
What it does
This workflow provides a robust framework for processing chat messages with AI, offering the following key functionalities:
- Triggers on Chat Message: Initiates the workflow whenever a chat message is received.
- Dynamically Selects LLM: Utilizes a "Model Selector" to intelligently choose between different chat models (OpenAI, Anthropic, Google Gemini, OpenRouter) based on predefined logic (which can be customized within the Model Selector node).
- Configurable AI Logic: Allows the user to select between two primary AI processing paths:
- Basic LLM Chain: A straightforward chain for simple conversational tasks.
- AI Agent with Memory and Structured Output: A more advanced setup that includes:
- Simple Memory: Maintains conversational context across interactions.
- Structured Output Parser: Ensures the AI's responses adhere to a predefined structure (e.g., JSON), making them easier to integrate with other systems.
- Supports Multiple Chat Models: Integrates with a variety of leading AI providers, including:
- OpenAI Chat Model
- Anthropic Chat Model
- Google Gemini Chat Model
- OpenRouter Chat Model
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance (cloud or self-hosted).
- AI Service Accounts/API Keys:
- An OpenAI API Key (for the OpenAI Chat Model)
- An Anthropic API Key (for the Anthropic Chat Model)
- A Google Cloud Project with the Gemini API enabled (for the Google Gemini Chat Model)
- An OpenRouter API Key (for the OpenRouter Chat Model)
- LangChain Nodes: Ensure the
@n8n/n8n-nodes-langchainpackage is installed in your n8n instance.
Setup/Usage
- Import the workflow: Download the JSON content and import it into your n8n instance.
- Configure Credentials: For each AI Chat Model node you intend to use (OpenAI, Anthropic, Google Gemini, OpenRouter), create and configure the respective API credentials within n8n.
- Customize Model Selector: Open the "Model Selector" node and define the logic for choosing between the different LLMs. This could be based on input content, user preferences, or other workflow data.
- Choose AI Logic: Decide whether to use the "Basic LLM Chain" or the "AI Agent" path. Connect the output of the "Model Selector" to your chosen path.
- Configure AI Agent (if used):
- Adjust the "Simple Memory" node's settings as needed.
- Define the desired output schema in the "Structured Output Parser" node.
- Activate the Workflow: Save and activate the workflow. It will now listen for incoming chat messages and process them according to your configuration.
Related Templates
AI multi-agent executive team for entrepreneurs with Gemini, Perplexity and WhatsApp
This workflow is an AI-powered multi-agent system built for startup founders and small business owners who want to automate decision-making, accountability, research, and communication, all through WhatsApp. The “virtual executive team,” is designed to help small teams to work smarter. This workflow sends you market analysis, market and sales tips, It can also monitor what your competitors are doing using perplexity (Research agent) and help you stay a head, or make better decisions. And when you feeling stuck with your start-up accountability director is creative enough to break the barrier 🎯 Core Features 🧑💼 1. President (Super Agent) Acts as the main controller that coordinates all sub-agents. Routes messages, assigns tasks, and ensures workflow synchronization between the AI Directors. 📊 2. Sales & Marketing Director Uses SerpAPI to search for market opportunities, leads, and trends. Suggests marketing campaigns, keywords, or outreach ideas. Can analyze current engagement metrics to adjust content strategy. 🕵️♀️ 3. Business Research Director Powered by Perplexity AI for competitive and market analysis. Monitors competitor moves, social media engagement, and product changes. Provides concise insights to help the founder adapt and stay ahead. ⏰ 4. Accountability Director Keeps the founder and executive team on track. Sends motivational nudges, task reminders, and progress reports. Promotes consistency and discipline — key traits for early-stage success. 🗓️ 5. Executive Secretary Handles scheduling, email drafting, and reminders. Connects with Google Calendar, Gmail, and Sheets through OAuth. Automates follow-ups, meeting summaries, and notifications directly via WhatsApp. 💬 WhatsApp as the Main Interface Interact naturally with your AI team through WhatsApp Business API. All responses, updates, and summaries are delivered to your chat. Ideal for founders who want to manage operations on the go. ⚙️ How It Works Trigger: The workflow starts from a WhatsApp Trigger node (via Meta Developer Account). Routing: The President agent analyzes the incoming message and determines which Director should handle it. Processing: Marketing or sales queries go to the Sales & Marketing Director. Research questions are handled by the Business Research Director. Accountability tasks are assigned to the Accountability Director. Scheduling or communication requests are managed by the Secretary. Collaboration: Each sub-agent returns results to the President, who summarizes and sends the reply back via WhatsApp. Memory: Context is maintained between sessions, ensuring personalized and coherent communication. 🧩 Integrations Required Gemini API – for general intelligence and task reasoning Supabase- for RAG and postgres persistent memory Perplexity API – for business and competitor analysis SerpAPI – for market research and opportunity scouting Google OAuth – to connect Sheets, Calendar, and Gmail WhatsApp Business API – for message triggers and responses 🚀 Benefits Acts like a team of tireless employees available 24/7. Saves time by automating research, reminders, and communication. Enhances accountability and strategy consistency for founders. Keeps operations centralized in a simple WhatsApp interface. 🧰 Setup Steps Create API credentials for: WhatsApp (via Meta Developer Account) Gemini, Perplexity, and SerpAPI Google OAuth (Sheets, Calendar, Gmail) Create a supabase account at supabase Add the credentials in the corresponding n8n nodes. Customize the system prompts for each Director based on your startup’s needs. Activate and start interacting with your virtual executive team on WhatsApp. Use Case You are a small organisation or start-up that can not afford hiring; marketing department, research department and secretar office, then this workflow is for you 💡 Need Customization? Want to tailor it for your startup or integrate with CRM tools like Notion or HubSpot? You can easily extend the workflow or contact the creator for personalized support. Consider adjusting the system prompt to suite your business
🎓 How to transform unstructured email data into structured format with AI agent
This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From – sender’s email address To – recipient’s email address Subject – email subject line Summary – short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits ✅ Full Automation: Eliminates manual reading and data entry from incoming emails. ✅ Multi-Source Integration: Handles data from different email providers seamlessly. ✅ AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. ✅ Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. ✅ Time Efficiency: Processes emails in real time, improving productivity and response speed. *✅ Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.
Send WooCommerce discount coupons to customers via WhatsApp using Rapiwa API
Who is this for? This workflow is ideal for WooCommerce store owners who want to automatically send promotional WhatsApp messages to their customers when new coupons are created. It’s designed for marketers and eCommerce managers looking to boost engagement, streamline coupon sharing, and track campaign performance effortlessly through Google Sheets. Overview This workflow listens for WooCommerce coupon creation events (coupon.created) and uses customer billing data to send promotional WhatsApp messages via the Rapiwa API. The flow formats the coupon data, cleans phone numbers, verifies WhatsApp registration with Rapiwa, sends the promotional message when verified, and logs each attempt to Google Sheets (separate sheets for verified/sent and unverified/not sent). What this Workflow Does Listens for new coupon creation events in WooCommerce via the WooCommerce Trigger node Retrieves all customer data from the WooCommerce store Processes customers in batches to control throughput Cleans and formats customer phone numbers for WhatsApp Verifies if phone numbers are valid WhatsApp accounts using Rapiwa API Sends personalized WhatsApp messages with coupon details to verified numbers Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Automated coupon distribution: Triggers when new coupons are created in WooCommerce Customer data retrieval: Fetches all customer information from WooCommerce Phone number validation: Verifies WhatsApp numbers before sending messages Personalized messaging: Includes customer name and coupon details in messages Dual logging system: Tracks both successful and failed message attempts Rate limiting: Uses batching and wait nodes to prevent API overload Data formatting: Structures coupon information for consistent messaging Google Sheet Column Structure A Google Sheet formatted like this ➤ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: | name | number | email | address1 | couponCode | couponTitle | couponType | couponAmount | createDate | expireDate | validity | status | | ----------- | ------------- | --------------------------------------------------- | --------- | ---------- | -------------- | ---------- | ------------ | ------------------- | ------------------- | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur-DOHS | 62dhryst | eid offer 2025 | percent | 20.00 | 2025-09-11 06:08:02 | 2025-09-15 00:00:00 | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur-DOHS | 62dhryst | eid offer 2025 | percent | 20.00 | 2025-09-11 06:08:02 | 2025-09-15 00:00:00 | verified | sent | Requirements n8n instance with the following nodes: WooCommerce Trigger, Code, SplitInBatches, HTTP Request, IF, Google Sheets, Wait WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) Important Notes Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy: Ensure compliance with data protection regulations when sending marketing messages. Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Message Content: The current message template references the first coupon only (coupons[0]). Adjust if you need to handle multiple coupons. Useful Links Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen