LLM Customer Assistant: Manage Tickets, Orders, and Inquiries

This workflow delivers AI-powered customer support using OpenAI's GPT-4o, managing inquiries, orders, and tickets via a chat interface. Key nodes include Chat Trigger for customer interactions, Condition for input validation, Google Sheets Tool for customer and order data, Supabase for ticket tracking, OpenAI for response generation, and Set for session processing. It ensures professional, personalized service with robust error handling. To set up, install n8n by downloading from n8n.io for self-hosted or sign up at cloud.n8n.io for cloud hosting. Obtain an OpenAI API key from openai.com under account settings. Get Google Sheets OAuth2 credentials from Google Cloud Console (console.cloud.google.com) under 'APIs & Services' > 'Credentials' > 'Create Credentials' > 'OAuth 2.0 Client', enabling the Google Sheets API. Acquire Supabase credentials from supabase.com by creating a project and table for support tickets. In n8n, import the workflow JSON, configure the OpenAI node with the API key, Google Sheets Tool nodes with OAuth2 credentials, and Supabase node with database credentials. Set up the Chat Trigger by copying its webhook URL for integration with a chat platform. Configure the Condition node to validate 'chatInput' for non-empty inputs. Set variables like CUSTOMER_DATABASE_ID and ORDERS_SHEET_NAME in the workflow settings to match your Google Sheets. Test by sending a POST request to the Chat Trigger webhook via Postman (e.g., {chatInput: 'Check my order status', sessionId: 'test123', customerId: 'C001'}). Verify responses in the Interaction Logger node for customer messages and agent replies. Check Google Sheets for updated order statuses and Supabase for logged tickets. Monitor for errors like missing credentials (HTTP 401) or empty inputs (response: 'Please describe your question'). If authentication fails, regenerate credentials in Google Cloud or Supabase. Deploy by activating the workflow in n8n’s interface. Monitor logs for issues like invalid customer IDs or rate limits, ensuring valid credentials and input formats before live use.