How to Build Advanced AI Ecommerce Agents using Flowise, Postgres and N8N (Text-to-SQL) | Part 1

Поделиться
HTML-код
  • Опубликовано: 9 янв 2025

Комментарии • 8

  • @n8n-io
    @n8n-io Месяц назад +2

    Hey Thomas, just a quick thank you note for your n8n videos on RUclips. We appreciate it!

  • @OnyxStudiosInteractive
    @OnyxStudiosInteractive  2 месяца назад +1

    👍Download/Clone This AgentFlow: onyxstudiosinteractive.com/ecom-agents-download
    👍Get Our New Training - Flowise Core Essentials: onyxstudiosinteractive.com/flowise-core-essentials

  • @myworld342
    @myworld342 Месяц назад +1

    Thanks Thomas, this is a really useful video. Is there a reason why you are using SQL rather than json for the database/product list?

    • @OnyxStudiosInteractive
      @OnyxStudiosInteractive  Месяц назад +1

      I'm glad you enjoyed the video. We're using SQL because we need a database to store and retrieve the product information. JSON is simply a data format. SQL also gives us an easy way to query the database using AI and automation.

    • @myworld342
      @myworld342 29 дней назад

      @@OnyxStudiosInteractive Thank you Thomas for the clarification!

  • @sleepless-nite
    @sleepless-nite 13 дней назад

    Any reason why you are using N8B and FlowWise? why not just use N8N?

  • @St_Phoenix
    @St_Phoenix 2 месяца назад

    I'm confused, where does the Agent come in? This looks like the normal SQL Prompt template from the market place with some nice backend automation but not an agent flow...

    • @OnyxStudiosInteractive
      @OnyxStudiosInteractive  2 месяца назад +1

      This is essentially a single agent flow. In this case the agent uses a variety of tools and training to turn your request into an SQL query and then filter the results to recommend products based on what you're looking for. That's why it's an agentflow.
      It's not a multi-agent or a sequential agentflow where multiple agents are working together. You could do that but it would be more complicated and potentially take longer.
      As far as the SQL Prompt template, I used it as a starting point but the template is intended to be
      more of a concept. It is not plug and play and takes a lot of work and customization for a specific use case.