Back to Catalog

Create AI support assistant for any device with GPT-4-mini & Pinecone

Jah cooziJah coozi
1220 views
2/3/2026
Official Page

Universal Digital Device Support Assistant

Transform any device manual into an intelligent AI assistant that provides 24/7 support for your users. This template works with ANY household appliance, electronic device, or technical equipment.

๐ŸŽฏ Use Cases

  • Manufacturers: Provide instant support for your products
  • Support Teams: Reduce ticket volume with AI-powered answers
  • Smart Homes: Centralized help for all devices
  • Personal Use: Never lose a manual again

โœจ Features

  • Universal Compatibility: Works with any device type
  • Multi-Language Support: Serve global customers
  • Intelligent Search: Semantic understanding of user queries
  • Context Awareness: Remembers conversation history
  • Easy Setup: Just upload your manual and go

๐Ÿ› ๏ธ What's Included

  1. Webhook Endpoint: Receive user queries via API
  2. AI Agent: Processes questions intelligently
  3. Vector Database: Stores and searches manuals
  4. Memory System: Maintains conversation context
  5. Upload Pipeline: Easy manual ingestion

๐Ÿ“‹ Setup Instructions

  1. Add Your Credentials:

    • OpenAI API key (or alternative LLM)
    • Pinecone API key (or alternative vector DB)
  2. Upload Device Manuals:

    • Use the manual upload trigger
    • Paste manual text or upload PDF
    • System automatically indexes content
  3. Configure Webhook:

    • Set your preferred endpoint path
    • Enable CORS if needed
    • Deploy and share URL
  4. Optional Customization:

    • Adjust chunk size for your content
    • Modify system prompts for your brand
    • Add additional tools or integrations

๐Ÿ”ง Supported Devices (Examples)

  • Kitchen Appliances (ovens, dishwashers, coffee machines)
  • Home Entertainment (TVs, sound systems, gaming consoles)
  • Smart Home Devices (thermostats, cameras, lights)
  • Computer Equipment (printers, routers, monitors)
  • Power Tools & Garden Equipment
  • Medical Devices
  • And many more!

๐ŸŒ Integration Options

  • Embed in your website
  • Connect to chat platforms
  • Mobile app integration
  • Voice assistant compatibility
  • Email support automation

๐Ÿ“ˆ Benefits

  • Reduce support costs by 70%
  • Available 24/7 in multiple languages
  • Consistent, accurate responses
  • Scales infinitely
  • Improves with usage

๐Ÿ” Privacy & Security

  • Your data stays in your control
  • Can be deployed on-premise
  • GDPR compliant architecture
  • No data sharing between devices

๐Ÿ’ก Pro Tips

  • Upload manuals in sections for better accuracy
  • Include troubleshooting guides and FAQs
  • Add model numbers and specifications
  • Regular updates keep content fresh

Start providing world-class device support today!

n8n AI Support Assistant with GPT-4 Mini and Pinecone

This n8n workflow demonstrates how to create an AI-powered support assistant that can answer questions based on a custom knowledge base stored in Pinecone, using an OpenAI Chat Model (like GPT-4 Mini) and Langchain agents. The workflow is triggered by an incoming webhook, processes a user query, retrieves relevant information from Pinecone, generates a response using the AI model, and sends the answer back via the webhook.

What it does

This workflow automates the process of querying a knowledge base and generating AI-driven responses:

  1. Receives a User Query: It listens for incoming HTTP requests (webhooks) containing a user's question.
  2. Prepares the Query: A "Set" node ensures the incoming data is structured correctly for the AI agent.
  3. Initializes AI Agent: An "AI Agent" node (Langchain Agent) is configured to use a chat model, memory, and a Pinecone vector store as a tool.
    • OpenAI Chat Model: Utilizes an OpenAI chat model (e.g., GPT-4 Mini) for conversational AI.
    • Simple Memory: Maintains a short-term conversational memory to provide context for follow-up questions.
    • Pinecone Vector Store: Acts as a tool for the AI agent to search and retrieve relevant documents from a custom knowledge base.
      • OpenAI Embeddings: Used by the Pinecone Vector Store to convert text into numerical vectors for similarity searches.
      • Recursive Character Text Splitter: Used to break down large documents into smaller, manageable chunks before embedding and storing them in Pinecone.
      • Default Data Loader: A placeholder for loading documents into the vector store (this workflow focuses on the query part, not the initial data loading).
  4. Processes the Query: The AI Agent uses its configured tools and model to understand the query, search Pinecone for answers, and formulate a coherent response.
  5. Responds to Webhook: The generated AI response is sent back as the payload of the initial webhook request.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • OpenAI API Key: For the OpenAI Chat Model and Embeddings.
  • Pinecone Account and API Key: To host your vector database. You'll also need a Pinecone Environment and Index Name.
  • Data for Pinecone: Prior to running this workflow for queries, you need to have your knowledge base documents embedded and stored in a Pinecone index. This workflow assumes the Pinecone index is already populated.

Setup/Usage

  1. Import the Workflow: Download the JSON provided and import it into your n8n instance.
  2. Configure Credentials:
    • OpenAI: Set up your OpenAI API credentials in n8n.
    • Pinecone: Set up your Pinecone API credentials in n8n, including your API Key, Environment, and the name of your Pinecone index.
  3. Activate the Webhook: Enable the "Webhook" trigger node. This will generate a unique URL.
  4. Populate Pinecone (if not already done): This workflow focuses on querying. You would typically have a separate workflow or script to load your documents, split them, generate embeddings using OpenAI, and upsert them into your Pinecone index.
  5. Test the Workflow:
    • Send an HTTP POST request to the Webhook URL.
    • The request body should be a JSON object containing your query, for example:
      {
          "query": "What are the benefits of using n8n for automation?"
      }
      
    • The workflow will process the query and return the AI-generated answer in the webhook response.
  6. Customize: Adjust the AI Agent's prompt, temperature, and other parameters in the "AI Agent" node to fine-tune its behavior. You can also modify the "Set" node to handle different incoming data structures.

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.

Ranjan DailataBy Ranjan Dailata
161

Generate 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

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive โžœ Download PDF โžœ OCR text โžœ AI normalize to JSON โžœ Upsert Buyer (Account) โžœ Create Opportunity โžœ Map Products โžœ Create OLI via Composite API โžœ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content โ†’ the parsed JSON (ensure itโ€™s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id โžœ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total โžœ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger โ†’ Download File From Google Download File From Google โ†’ Extract from File โ†’ Update File to One Drive Extract from File โ†’ Message a model Message a model โ†’ Create or update an account Create or update an account โ†’ Create an opportunity Create an opportunity โ†’ Build SOQL Build SOQL โ†’ Query PricebookEntries Query PricebookEntries โ†’ Code in JavaScript Code in JavaScript โ†’ Create Opportunity Line Items --- Quick setup checklist ๐Ÿ” Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. ๐Ÿ“‚ IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) ๐Ÿง  AI Prompt: Use the strict system prompt; jsonOutput = true. ๐Ÿงพ Field mappings: Buyer tax id/name โ†’ Account upsert fields Invoice code/date/amount โ†’ Opportunity fields Product name must equal your Product2.ProductCode in SF. โœ… Test: Drop a sample PDF โ†’ verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep โ€œReturn only a JSON arrayโ€ as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields donโ€™t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your orgโ€™s domain or use the Salesforce nodeโ€™s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942