access file from "download" node for gemini
Hi,
in order to have gemini analyze a image in the multimodal gemini node I need to attach an image to the api call.
So I am using the download node to download the file, but I am having trouble accessing the actual file. Please have a look at the screenshots,
Thanks
Solution:Jump to solution
Hey @Thomas, I've responded to your support request addressing the issues in your workflow. Here's a quick recap:
I've reviewed your workflow and identified a couple of issues that I've addressed below:
- There was an issue with the download node not automatically creating intermediate folders. We've now updated the logic to create folders according to the flat file structure....
3 Replies
AI Support Bot Information
<@1085900587767431259> you can react on the relevant answer (message) with a ✅ in this thread when you think it has been solved, by the bot or by a human!
Anyone can react on this message with a ❌ if the GPT bot is unhelpful or hallucinating answers.
Please note: Team members will review and answer the questions on best efforts basis.
AI Response
It seems like there is an ongoing challenge in accessing the file when using the download node in BuildShip. As a potential solution, you may try using a buffer. By creating a new node, you can let that node return the buffer. This method has been used to save files in cloud storage, although it may not be a permanent fix【4:0†buildship-support-site.json】.
If this solution doesn't work for you, you might consider exploring alternative methods. For instance, utilizing a "create public URL node" as part of your download process might provide better results【4:0†buildship-support-site.json】.
For more detailed support or if these solutions don't solve the issue, it would be advisable to contact BuildShip support via their in-app support feature.
BuildShip AI Support
Solution
Hey @Thomas, I've responded to your support request addressing the issues in your workflow. Here's a quick recap:
I've reviewed your workflow and identified a couple of issues that I've addressed below:
- There was an issue with the download node not automatically creating intermediate folders. We've now updated the logic to create folders according to the flat file structure.
- The Image URL provided to the download node is currently returning a 404 error. This could be because the file URL is not public or has restricted access.
Once you update the image url in the download node, your flow should run as expected.