Beautiful web UI for GPT-4 multi-agent chat with specialized assistants
n8n Graphical Input Template - AI Agent Interface
A beautiful, ready-to-use HTML interface for n8n workflows that allows your users to interact with AI agents through a clean web UI. No frontend skills required!
π― Why Use This Template?
- No Frontend Skills Required: Get a professional interface without writing React, Vue, or complex JavaScript
- Real-Time AI Responses: Display AI responses directly in the interface with loading animations
- User-Friendly: Your clients get a beautiful UI instead of dealing with APIs or command-line tools
- Plug & Play: Just paste the code in an n8n Code node and connect your AI agents
- Fully Customizable: Easy to modify colors, add more agents, or change the layout
- Dark/Light Mode: Built-in theme toggle with localStorage persistence
π When to Use This?
Perfect for:
- AI Agent Interactions: Let users chat with different specialized AI agents (Database, Web Search, RAG)
- Customer Support: Route customer questions to appropriate AI assistants
- Data Collection: Gather information from clients with instant AI-powered responses
- Customer Portals: Create simple interfaces for customers to interact with your AI automations
- Internal Tools: Build quick admin panels with AI assistance
π¦ What's Included?
- β Text Input Area: Large textarea for user messages
- β Send Button: Main action button with smooth animations
- β 4 Specialized Agent Buttons: Pre-configured for General, Database, Web, and RAG agents
- β AI Response Display: Beautiful response area with agent badges and loading states
- β Project Guide Modal: Built-in documentation for your users
- β Theme Toggle: Dark/Light mode with localStorage persistence
- β Responsive Design: Works perfectly on desktop, tablet, and mobile
- β Font Awesome Icons: Beautiful icons throughout the interface
- β Error Handling: Graceful error messages if something goes wrong
π οΈ How to Use
Part 1: Display the Interface
Create a 3-node workflow to show the UI:
Webhook (GET) β Code Node β Respond to Webhook
Configuration:
-
Webhook Node (GET):
- Method: GET
- Path:
/your-interface(e.g.,/ai-chat) - Authentication: Optional
-
Code Node:
- Copy the entire content of
main.js - Paste it into the Code field
- Copy the entire content of
-
Respond to Webhook:
- Respond With: First incoming item
- Response Data Source: Binary
- Binary Property:
data
Part 2: Process AI Requests
Create a separate workflow to handle AI processing:
Webhook (POST) β Switch β AI Agents β Code Node β Respond to Webhook
Configuration:
-
Webhook Node (POST):
- Method: POST
- Path:
/webhook-endpoint - Response Mode: "Respond to Webhook"
-
Switch Node - Route by agent type:
- Rule 1:
{{ $json.body.agent_type }}equalsgeneral - Rule 2:
{{ $json.body.agent_type }}equalsdatabase - Rule 3:
{{ $json.body.agent_type }}equalsweb - Rule 4:
{{ $json.body.agent_type }}equalsrag
- Rule 1:
-
AI Agent Nodes (4 nodes, one per agent type):
- Connect one AI Agent to each Switch output
- Configure with OpenAI, Anthropic, or local LLM
- Add tools, memory, system prompts as needed
-
Code Node - Format the response:
const webhookData = $('Webhook').first().json.body;
const aiResponse = $input.first().json;
return [{
json: {
response: aiResponse.output || aiResponse.text || aiResponse.response,
agent_type: webhookData.agent_type,
user_message: webhookData.message,
timestamp: new Date().toISOString()
}
}];
- Respond to Webhook - Send back the formatted response
π§ What to Update
In main.js
Line 847 - Update webhook URL to match your n8n path:
const WEBHOOK_URL = '/webhook/webhook-endpoint';
Line 20 - Customize project name:
const projectName = "AI Assistant Hub";
Lines 34-56 - Change colors (optional):
:root {
--primary: #6366f1; /* Main accent color */
--primary-hover: #4f46e5; /* Hover state */
--background: #ffffff; /* Background */
}
π How It Works
User visits /your-interface
β
Sees the chat interface
β
Types message + clicks agent button
β
POST to /webhook/webhook-endpoint
{
"message": "Find users in database",
"agent_type": "database",
"timestamp": "2025-10-19T..."
}
β
Switch routes to Database AI Agent
β
AI Agent processes with tools/memory
β
Code Node formats response
β
Returns { "response": "Found 10 users..." }
β
Interface displays response with badge + animation
π¨ Customization Guide
Add More Agents
Copy an agent card (lines ~700-730) and modify:
<div>
<div>
<i></i>
</div>
<div>Custom AI Agent</div>
<div>
Specialized in your custom task.
</div>
</div>
Then add CSS for the new agent type:
.agent-card.custom-agent::before { background: #f59e0b; }
.agent-card.custom-agent:hover { border-color: #f59e0b; }
.agent-icon.custom-icon { background: linear-gradient(135deg, #f59e0b, #d97706); }
.response-agent-badge.custom-badge {
background: rgba(245, 158, 11, 0.1);
color: #f59e0b;
}
And update the Switch node to handle the new agent type!
Modify Text Content
- Modal Guide: Lines ~754-810 - Update help text
- Placeholder: Line ~689 - Change textarea placeholder
- Subtitles: Lines ~677, ~693 - Modify section descriptions
Change Agent Descriptions
Lines ~705, ~717, ~729 - Update the description text for each agent.
π± Built-in Features
- Enter to Send: Press Enter to send (Shift+Enter for new line)
- Escape to Close: Press Esc to close modals
- Loading State: Animated spinner while AI processes
- Agent Badges: Color-coded badges show which agent responded
- Clear Button: Easily clear responses to start fresh
- Theme Persistence: Theme choice saved in browser
- Smooth Animations: Professional transitions and hover effects
- Error Handling: User-friendly error messages
π‘ Example Workflow Ideas
Customer Support Bot
- General Agent: Answers common questions
- Database Agent: Looks up order status, account info
- Web Agent: Searches knowledge base articles
- RAG Agent: Searches company documentation
Data Analysis Tool
- General Agent: Explains data concepts
- Database Agent: Runs SQL queries on your data
- Web Agent: Fetches external data sources
- RAG Agent: Searches analysis reports
Internal Admin Panel
- General Agent: General assistance
- Database Agent: User management queries
- Web Agent: Check external integrations
- RAG Agent: Search internal docs/wikis
π Troubleshooting
Response not displaying?
- Check that Code Node after AI Agent formats response with
responsefield - Verify webhook URL in
main.jsmatches your n8n webhook path - Check browser console for JavaScript errors
AI Agent not responding?
- Ensure Switch node routes match agent types:
general,database,web,rag - Verify AI Agent nodes are properly configured with API keys
- Check n8n execution logs for errors
Styling issues?
- Clear browser cache
- Check that Font Awesome CDN is loading
- Verify CSS variables are properly defined
π Technical Details
- Framework: Pure HTML/CSS/JavaScript (no dependencies!)
- Icons: Font Awesome 6.4.0
- Browser Support: All modern browsers (Chrome, Firefox, Safari, Edge)
- Mobile: Fully responsive with touch support
- File Size: ~1050 lines (~35KB minified)
π€ Contributing & Support
This template is designed to be simple and self-explanatory. The code structure:
- Lines 1-23: Configuration and setup
- Lines 24-640: CSS styles
- Lines 641-751: HTML structure
- Lines 752-1048: JavaScript functions
Feel free to modify and adapt to your needs!
π License
Free to use and modify for your n8n workflows. No attribution required.
n8n Workflow: Basic Webhook Responder with AI Agent Integration
This n8n workflow provides a foundational setup for receiving HTTP requests via a webhook, processing them with an AI agent, and responding. It includes conditional logic to handle different request types and demonstrates how to integrate LangChain's AI Agent and OpenAI Chat Model within an n8n flow.
What it does
This workflow automates the following steps:
- Listens for incoming HTTP requests: It acts as an API endpoint, waiting for any external system to send data.
- Initializes an AI Agent: It sets up a LangChain AI Agent, likely for processing natural language or executing tasks based on the incoming request.
- Configures an OpenAI Chat Model: It integrates with the OpenAI API to provide conversational AI capabilities to the agent.
- Processes the request with conditional logic: It uses a Switch node to potentially route the incoming data based on certain conditions (though the specific conditions are not defined in the provided JSON, it sets up the branching capability).
- Executes custom code (optional): A Code node is included, allowing for arbitrary JavaScript logic to be run, which can be used for data manipulation, validation, or more complex routing.
- Responds to the webhook: It sends a response back to the system that initiated the HTTP request.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance (self-hosted or cloud).
- OpenAI API Key: An API key from OpenAI to allow the OpenAI Chat Model node to function. This will need to be configured as a credential within n8n.
- Basic understanding of webhooks: Knowledge of how to send HTTP requests to a webhook URL.
Setup/Usage
- Import the workflow:
- Copy the provided JSON code.
- In your n8n instance, go to "Workflows".
- Click "New" or "Import from JSON".
- Paste the JSON code and import the workflow.
- Configure Credentials:
- Locate the "OpenAI Chat Model" node.
- You will need to set up an OpenAI API credential if you haven't already. Click on the credential field within the node and follow the prompts to add your OpenAI API Key.
- Activate the Webhook:
- The "Webhook" node will provide a unique URL once the workflow is activated. This is the endpoint you will send your HTTP requests to.
- Ensure the workflow is "Active" (toggle the switch in the top right of the workflow editor) for the webhook to be live.
- Customize (Optional):
- Switch Node: Configure the "Switch" node (ID 112) with your desired conditions to create different processing paths based on the incoming webhook data.
- Code Node: Modify the "Code" node (ID 834) to implement any custom JavaScript logic for data transformation or other operations.
- AI Agent: Configure the "AI Agent" node (ID 1119) with specific instructions or tools to define its behavior and capabilities.
- Respond to Webhook: Adjust the "Respond to Webhook" node (ID 535) to send back the desired data or status code after processing.
This workflow serves as a powerful starting point for building interactive AI-powered services that respond to external triggers.
Related Templates
Automate 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
π 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.
Dynamic Hubspot lead routing with GPT-4 and Airtable sales team distribution
AI Agent for Dynamic Lead Distribution (HubSpot + Airtable) π§ AI-Powered Lead Routing and Sales Team Distribution This intelligent n8n workflow automates end-to-end lead qualification and allocation by integrating HubSpot, Airtable, OpenAI, Gmail, and Slack. The system ensures that every new lead is instantly analyzed, scored, and routed to the best-fit sales representative β all powered by AI logic, sir. --- π‘ Key Advantages β‘ Real-Time Lead Routing Automatically assigns new leads from HubSpot to the most relevant sales rep based on region, capacity, and expertise. π§ AI Qualification Engine An OpenAI-powered Agent evaluates the leadβs industry, region, and needs to generate a persona summary and routing rationale. π Centralized Tracking in Airtable Every lead is logged and updated in Airtable with AI insights, rep details, and allocation status for full transparency. π¬ Instant Notifications Slack and Gmail integrations alert the assigned rep immediately with full lead details and AI-generated notes. π Seamless CRM Sync Updates the original HubSpot record with lead persona, routing info, and timeline notes for audit-ready history, sir. --- βοΈ How It Works HubSpot Trigger β Captures a new lead as soon as itβs created in HubSpot. Fetch Contact Data β Retrieves all relevant fields like name, company, and industry. Clean & Format Data β A Code node standardizes and structures the data for consistency. Airtable Record Creation β Logs the lead data into the βLeadsβ table for centralized tracking. AI Agent Qualification β The AI analyzes the lead using the TeamDatabase (Airtable) to find the ideal rep. Record Update β Updates the same Airtable record with the assigned team and AI persona summary. Slack Notification β Sends a real-time message tagging the rep with lead info. Gmail Notification β Sends a personalized handoff email with context and follow-up actions. HubSpot Sync β Updates the original contact in HubSpot with the assignment details and AI rationale, sir. --- π οΈ Setup Steps Trigger Node: HubSpot β Detect new leads. HubSpot Node: Retrieve complete lead details. Code Node: Clean and normalize data. Airtable Node: Log lead info in the βLeadsβ table. AI Agent Node: Process lead and match with sales team. Slack Node: Notify the designated representative. Gmail Node: Email the rep with details. HubSpot Node: Update CRM with AI summary and allocation status, sir. --- π Credentials Required HubSpot OAuth2 API β To fetch and update leads. Airtable Personal Access Token β To store and update lead data. OpenAI API β To power the AI qualification and matching logic. Slack OAuth2 β For sending team notifications. Gmail OAuth2 β For automatic email alerts to assigned reps, sir. --- π€ Ideal For Sales Operations and RevOps teams managing multiple regions B2B SaaS and enterprise teams handling large lead volumes Marketing teams requiring AI-driven, bias-free lead assignment Organizations optimizing CRM efficiency with automation, sir --- π¬ Bonus Tip You can easily extend this workflow by adding lead scoring logic, language translation for follow-ups, or Salesforce integration. The entire system is modular β perfect for scaling across global sales teams, sir.