Back to Catalog

Build a personalized shopping assistant with Zep Memory, GPT-4 and Google Sheets

InfyOm TechnologiesInfyOm Technologies
1243 views
2/3/2026
Official Page

βœ… What problem does this workflow solve?

Most e-commerce chatbots are transactional; they answer one question at a time and forget your context right after. This workflow changes that. It introduces a smart, memory-enabled shopping assistant that remembers user preferences, past orders, and previous queries to offer deeply personalized, natural conversations.


βš™οΈ What does this workflow do?

  1. Accepts real-time chat messages from users.
  2. Uses Zep Memory to store and recall personalized context.
  3. Integrates with:
    • πŸ›’ Product Inventory
    • πŸ“¦ Order History
    • πŸ“œ Return Policy
  4. Answers complex queries based on historical context.
  5. Provides:
    • Personalized product recommendations
    • Context-aware order lookups
    • Seamless return processing
    • Policy discussions with minimal user input

🧠 Why Context & Memory Matter

Traditional bots:

  • ❌ Forget what the user said 2 messages ago
  • ❌ Ask repetitive questions (name, order ID, etc.)
  • ❌ Can’t personalize beyond basic filters

With Zep-powered memory, your bot:

  • βœ… Remembers preferences (e.g., favorite categories, past questions)
  • βœ… Builds persistent context across sessions
  • βœ… Gives dynamic, user-specific replies (e.g., "You ordered this last week…")
  • βœ… Offers a frictionless support experience

πŸ”§ Setup Instructions

🧠 Zep Memory Setup

  • Create a Zep instance and connect it via the Zep Memory node.
  • It will automatically store user conversations and summarize facts.

πŸ’¬ Chat Trigger

  • Use the "When chat message received" trigger to initiate the conversation workflow.

πŸ€– AI Agent Configuration

  • Connect:
    • Chat Model β†’ OpenAI GPT-4 or GPT-3.5
    • Memory β†’ Zep
    • Tools:
      • Get_Orders – Fetch user order history from Google Sheets
      • Get_Inventory – Recommend products based on stock and preferences
      • Get_ReturnPolicy – Answer policy-related questions

πŸ“„ Google Sheets

  • Store orders, inventory, and return policies in structured sheets.
  • Use read access nodes to fetch data dynamically during conversations.

🧠 How it Works – Step-by-Step

  1. Chat Trigger – User sends a message.
  2. AI Agent (w/ Zep Memory):
    • Reads past interactions to build context.
    • Pulls memory facts (e.g., "User prefers men's sneakers").
  3. Uses External Tools:
    • Looks up orders, return policies, or available products.
  4. Generates Personalized Response using OpenAI.
  5. Reply Sent Back to the user through chat.

🧩 What the Bot Can Do

  • πŸ› Suggest products based on past browsing or purchase behavior.
  • πŸ“¦ Check order status and history without requiring the user to provide order IDs.
  • πŸ“ƒ Explain return policies in detail, adapting answers based on context.
  • πŸ€– Engage in more human-like conversations across multiple sessions.

πŸ‘€ Who can use this?

This is ideal for:

  • πŸ›’ E-commerce store owners
  • πŸ€– Product-focused AI startups
  • πŸ“¦ Customer service teams
  • 🧠 Developers building intelligent commerce bots

If you're building a chatbot that goes beyond canned responses, this memory-first shopping assistant is the upgrade you need.


πŸ›  Customization Ideas

  • Connect with Shopify, WooCommerce, or Notion instead of Google Sheets.
  • Add payment processing or shipping tracking integrations.
  • Customize the memory expiration or fact-summarization rules in Zep.
  • Integrate with voice AI to make it work as a phone-based shopping assistant.

πŸš€ Ready to Launch?

Just connect:

  • βœ… OpenAI Chat Model
  • βœ… Zep Memory Engine
  • βœ… Your Product/Order/Policy Sheets

And you’re ready to deliver truly personalized shopping conversations.

Personalized Shopping Assistant with Zep Memory, GPT-4, and Google Sheets (n8n Workflow)

This n8n workflow demonstrates how to build a personalized shopping assistant that leverages conversational AI, long-term memory, and potentially external tools (though not explicitly defined in this JSON). It acts as a foundational example for creating intelligent agents that can maintain context across interactions.

What it does

This workflow sets up a basic AI agent capable of engaging in conversational interactions, utilizing a chat model and a memory store.

  1. Listens for Chat Messages: The workflow is triggered whenever a new chat message is received. This could be from various chat platforms integrated with n8n (e.g., Telegram, Slack, custom webhooks).
  2. Initializes AI Agent: An AI Agent node is used to orchestrate the conversation. This agent is designed to understand user input and decide on the best course of action.
  3. Integrates Long-Term Memory (Zep): The agent is configured to use Zep as its memory store. This allows the AI to remember past conversations and user preferences, enabling a more personalized and coherent interaction over time.
  4. Utilizes OpenAI Chat Model: The agent employs an OpenAI Chat Model (likely GPT-4 or similar) for generating responses and understanding natural language.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • OpenAI API Key: An API key for OpenAI to use their chat models.
  • Zep Instance: Access to a Zep memory instance (either self-hosted or cloud-based) for long-term conversational memory.
  • Chat Platform Integration: An n8n chat trigger configured for your desired chat platform (e.g., Telegram, Slack, Discord, or a custom webhook).

Setup/Usage

  1. Import the Workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • OpenAI Chat Model: Configure your OpenAI API key within the "OpenAI Chat Model" node.
    • Zep Memory: Configure the connection details for your Zep instance within the "Zep" node.
  3. Configure Chat Trigger: Set up the "When chat message received" trigger to listen for messages from your preferred chat platform.
  4. Activate the Workflow: Once all credentials and configurations are set, activate the workflow.

The workflow is now ready to process incoming chat messages, engage in conversations, and leverage Zep for memory and OpenAI for language understanding and generation.

Related Templates

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

AI-powered code review with linting, red-marked corrections in Google Sheets & Slack

Advanced Code Review Automation (AI + Lint + Slack) Who’s it for For software engineers, QA teams, and tech leads who want to automate intelligent code reviews with both AI-driven suggestions and rule-based linting β€” all managed in Google Sheets with instant Slack summaries. How it works This workflow performs a two-layer review system: Lint Check: Runs a lightweight static analysis to find common issues (e.g., use of var, console.log, unbalanced braces). AI Review: Sends valid code to Gemini AI, which provides human-like review feedback with severity classification (Critical, Major, Minor) and visual highlights (red/orange tags). Formatter: Combines lint and AI results, calculating an overall score (0–10). Aggregator: Summarizes results for quick comparison. Google Sheets Writer: Appends results to your review log. Slack Notification: Posts a concise summary (e.g., number of issues and average score) to your team’s channel. How to set up Connect Google Sheets and Slack credentials in n8n. Replace placeholders (<YOURSPREADSHEETID>, <YOURSHEETGIDORNAME>, <YOURSLACKCHANNEL_ID>). Adjust the AI review prompt or lint rules as needed. Activate the workflow β€” reviews will start automatically whenever new code is added to the sheet. Requirements Google Sheets and Slack integrations enabled A configured AI node (Gemini, OpenAI, or compatible) Proper permissions to write to your target Google Sheet How to customize Add more linting rules (naming conventions, spacing, forbidden APIs) Extend the AI prompt for project-specific guidelines Customize the Slack message formatting Export analytics to a dashboard (e.g., Notion or Data Studio) Why it’s valuable This workflow brings realistic, team-oriented AI-assisted code review to n8n β€” combining the speed of automated linting with the nuance of human-style feedback. It saves time, improves code quality, and keeps your team’s review history transparent and centralized.

higashiyama By higashiyama
90

Auto-reply & create Linear tickets from Gmail with GPT-5, gotoHuman & human review

This workflow automatically classifies every new email from your linked mailbox, drafts a personalized reply, and creates Linear tickets for bugs or feature requests. It uses a human-in-the-loop with gotoHuman and continuously improves itself by learning from approved examples. How it works The workflow triggers on every new email from your linked mailbox. Self-learning Email Classifier: an AI model categorizes the email into defined categories (e.g., Bug Report, Feature Request, Sales Opportunity, etc.). It fetches previously approved classification examples from gotoHuman to refine decisions. Self-learning Email Writer: the AI drafts a reply to the email. It learns over time by using previously approved replies from gotoHuman, with per-classification context to tailor tone and style (e.g., different style for sales vs. bug reports). Human Review in gotoHuman: review the classification and the drafted reply. Drafts can be edited or retried. Approved values are used to train the self-learning agents. Send approved Reply: the approved response is sent as a reply to the email thread. Create ticket: if the classification is Bug or Feature Request, a ticket is created by another AI agent in Linear. Human Review in gotoHuman: How to set up Most importantly, install the gotoHuman node before importing this template! (Just add the node to a blank canvas before importing) Set up credentials for gotoHuman, OpenAI, your email provider (e.g. Gmail), and Linear. In gotoHuman, select and create the pre-built review template "Support email agent" or import the ID: 6fzuCJlFYJtlu9mGYcVT. Select this template in the gotoHuman node. In the "gotoHuman: Fetch approved examples" http nodes you need to add your formId. It is the ID of the review template that you just created/imported in gotoHuman. Requirements gotoHuman (human supervision, memory for self-learning) OpenAI (classification, drafting) Gmail or your preferred email provider (for email trigger+replies) Linear (ticketing) How to customize Expand or refine the categories used by the classifier. Update the prompt to reflect your own taxonomy. Filter fetched training data from gotoHuman by reviewer so the writer adapts to their personalized tone and preferences. Add more context to the AI email writer (calendar events, FAQs, product docs) to improve reply quality.

gotoHumanBy gotoHuman
353