Build Your Own AI Chatbot for Documents with n8n (No Code Required!) [Part 1]

Подписаться 1,6 тыс.

Просмотров 4,3 тыс.

50% 1

In this tutorial, we'll be building a powerful AI chatbot for your documents using a no-code tool called n8n.
Say goodbye to sifting through endless files and PDFs to find the information you need. Our chatbot will allow you to simply ask questions and receive accurate and detailed responses in seconds.
Follow along as we guide you through the process of setting up your own AI chatbot for documents.
Next steps to go deeper:
✅ To get started with n8n and to help support this channel, sign-up to n8n with this partner link: n8n.partnerlinks.io/pxj22or4p8l8
✅ Download this n8n template for free when you sign-up for the weekly newsletter: aifornoncoders.com
✅Join my Udemy course - Introduction to AI Automation with n8n and LangChain
Discount code with this link : www.udemy.com/course/introduc...
Buy me a coffee ☕: buymeacoffee.com/aifornoncoders

Наука

Опубликовано:

30 июн 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 25

@JoaquinTorroba 4 месяца назад

Very useful! It'd be great to see a tutorial with Buildship. As always, thanks for sharing Derek!

@jackmermigas9465 2 месяца назад

Brilliant this is exactly what I've been looking for. The potential for this is limitless how exciting!

@GlobalUpdateNow37 Месяц назад

Me too

@adanpalma4026 3 месяца назад

thanks four your simple but valuables and helpful videos. Can you load multiples pdf but using N8N?

@RolandoLopezNieto 4 месяца назад

Great video buddy. Since you can do pretty much the same setup on Flowise, what would be deciding factors that would make you choose between Flowise or n8n?

@derekcheung2598 4 месяца назад

Hi Rolando, that's a great question. There's some overlap in functionality. Flowise is AI native -- built ground up on AI use cases. n8n is built with automation as main use case with AI being added recently. Chat with your data is a use case that is common to both. But what you'll see in next week's tutorial is how easy it is to integrate into tools like Slack and later Discord. It's built into n8n, so those types of use cases are much easier. Flowise has strengths in the amount of integration in all the different types of vector stores, LLMs, service providers etc... There are use cases that one will use the other: for example, Flowise calling into n8n flows as tools to get access to Google tools like drive and docs. And n8n flows that call into Flowise to access all the different LLMs that Flowise has.

@RolandoLopezNieto 4 месяца назад

@@derekcheung2598 thanks for the reply.

@SeanTierney 2 месяца назад

Derek, this tutorial is truly fantastic (helped me get a basic proof of concept in place for something I've been trying to build). Question for you: are you aware of a way for n8n to pass in other variables on upserting the data? My case is I'm doing a HTTP post to a webhook in n8n and it's indexing member content using this workflow. I added a field in the documents table of Supabase called "userid" and I'm trying to log that at the time of upsert but don't see a way to append additional info. Wondering if this is best accomplished by some type of trigger in supabase that tries to extract it from metadata... or more ideally there would be a way to append additional params from the insert step in n8n. Any suggestions?

@derekcheung2598 2 месяца назад

Thanks Sean for your feedback! One easy approach for the use case you mentioned is to use a slightly different vector store QDrant. QDrant might be easier in this case because if an index is not created yet, it will automatically create it. So in your upserting flow, you can pass into the webhook the userid and have Qdrant create an index based on that id. When you add, you specific the user id again and it will add to that index.

@SeanTierney 2 месяца назад

@@derekcheung2598 thx so much. Will investigate Qdrant. I came up with a solution though I'm not sure it's ideal- I was able to inject the userid as metadata into Supabase and then I also stuffed it into the indexed content itself so that the LLM has the userid and I can query the LLM and return ID's via structured output parser. I can think of reasons why this approach is less ideal (seems more brittle and less deterministic, no surefire way to return all indexed content by userid, potential privacy issues with LLM as a downstream provider now having PID). But this is at least a semi-workable solution for now. Will check out Qdrant and see how hard to swap out the vector store. It sounds like the abstraction of LangChain should make that fairly straightforward which is great.

@EliSpizzichino 3 месяца назад

I see all the workflows that use Gdrive to download a single file, what about accessing the local fs and index/vectorize a directory full of files (for example code)?

@user-ri9jv4fz5q 4 месяца назад

Great video! Would I be able to use this workflow with my google sheets files?

@derekcheung2598 4 месяца назад

Yup

@cgc2300 8 дней назад

hello could you explain to me when and why to use this or that node and also explain to me and the workflows which are made available on the site, there are very few explanations and I do not understand not

@user-gh4rk2tp1j 4 месяца назад

Hi Derek, thanks for your video, and your explanation. Do you know if there is any way to embed the caht in wp site, or any html file? Thanks very much for your help

@derekcheung2598 4 месяца назад

Yup, here is how: www.npmjs.com/package/@n8n/chat?activeTab=readme

@musumo1908 2 месяца назад

hello again - anyway to stop the upsert reuploading the same documents every time you run this? Or is it standard older langchain where you just create a chat flow with retrieval instead? Too used to flowise! thanks And how can you scrape a website and add to the vectorDB?!

@DROTIMA 4 месяца назад

Excellent video! Can we do this with 100k pdf pages? And how can we customize the chat interface?

@derekcheung2598 4 месяца назад

It's a good question on scaling. First is also cost of vectorizing 100K pdf pages. It might get quite expensive. Second is performance, vector databases will vary quite a bit in terms of performance at scale, so you'll want to do your due diligence there. There's a lot of database options to pick from. You'll also want to add in meta data so that you can filter out your similarity search. In terms of customize chat interface, yes. In fact, there are different channels you can plug into: slack, discord, telegram, teams, whatsapp, and webpage embed.

@musumo1908 4 месяца назад

Great vid! Would love to see a WhatsApp n8n bot..it looks like there’s no direct WA API integration?? And it still needs twillio?? Thx

@derekcheung2598 4 месяца назад

Thanks! I did notice a Whatsapp node in n8n. I haven't looked in detail, but it has a couple credential settings that I think you need to go through the Whatsapp for business application process to get an access token

@arthuraquino8356 4 месяца назад

Could I somehow use the assistant? My idea is to use pgvector to store the threads and then the assistant retrieves them in the context to be larger than the model's context capacity.

@derekcheung2598 4 месяца назад

Hi Arthur, can you expand a bit more on your use case? What data are you thinking to store in your database