Hey AI Automation Society 👋 I came across an incredible resource that I think you’ll find super helpful: Vellum’s LLM Leaderboard. 💡What’s it about? This site breaks down all the top large language models (LLMs) by: - Context window size (some handle up to 1 million tokens!) - Pricing (great for spotting cost-effective options) - Performance on tasks like coding, math, and language understanding If you’re exploring which LLM is the best fit for your AI automations, this is a great place to start. Check it out and let me know your thoughts! 👇

Hi, I struggle building this Agent on n8n: The agent scans a Google Drive folder and all its subfolders once a day, finding new or updated files and uploading them to Pinecone vector database while keeping the folder name as the namespace (Keeping my Google Drive and the vector database synchronized). If you have built something similar in the past and would like to share your n8n templet or comments, I would greatly appreciate it...

First off, the actual Google Drive trigger does not fire as it should in this particular flow. I did find a workaround for that. But my question is this or these rather. 1 . When pulling a Google doc from Google Drive. is there any way to have the folder name as an actual parameter that can be used 1. When I use the on-schedule node can I use it to sweep multiple modes, and how would this fire off exactly? The problem I am looking to solve and the overview of this workflow. The workflow takes a document from a folder on the drive and uses it to post an article on a website. The website has multiple categories for the blogs, and I am trying to create a solution that will allow me to post the category for the blog along with the rest of the parts. So my solution was to have each blog placed in a folder for its specific category but I can't find a way to read the folder name in a way I can pass around n8n and if I just have a scan this drive folder + set category node for each category should I use one on schedule node or (11 in my case ) but a schedule node for each drive node