feat(ChainLLM): Add support for multiple binary fields and URLs for image inputs

[amirhmoradi]

Summary

This PR enhances the Basic LLM Chain (ChainLLM) node by adding support for multiple image inputs, both as binary files and URLs, similar to the OpenAI Image Analysis node.

🔹 What’s New?

• Multi-Image Support via Binary Fields

  • Users can now specify multiple binary field names in a comma-separated format (e.g., data, image1, image2).
  • This allows multiple images to be passed in a single request, ensuring that the model processes all images together.

• Multi-Image Support via URLs

  • Users can now input multiple image URLs (comma-separated, e.g., https://example.com/image1.jpg, https://example.com/image2.png).
  • All images are sent together to the model, just like binary files.

• Updated UI for Better Usability

  • Placeholders & Examples added to guide users:
    • Binary Field Input: "e.g. data, image1, image2"
    • Image URL Input: "e.g. https://example.com/image1.jpg, https://example.com/image2.png"
  • Tooltips & Descriptions explain how to use these fields.

• Backend Changes

  • The getImageMessage() function now:
    • Loops through multiple binary field names to extract images.
    • Processes multiple URLs.
    • Combines all images into a single structured request.
  • Ensures the model considers all images together rather than processing them separately.

🚀 How to Test:

1. Test Binary Image Input:

   • Add the Basic LLM Chain node.
   • Select Binary Image.
   • Provide multiple binary field names (e.g., data, image1, image2).
   • Verify that all images are processed together.

2. Test Image URL Input:

   • Add the Basic LLM Chain node.
   • Select Image URL.
   • Provide multiple URLs (comma-separated).
   • Verify that all images are processed together.

---

Related Linear tickets, Github issues, and Community forum posts

No related issue reported yet. This PR proactively improves functionality and aligns ChainLLM with the OpenAI Image Analysis node.

---

Review / Merge checklist

• PR title and summary are descriptive. (conventions)
• Docs updated or follow-up ticket created.
• Tests included.
• PR Labeled with release/backport (if the PR is an urgent fix that needs to be backported)

[CLAassistant]

All committers have signed the CLA.

[Joffcom]

Hey @amirhmoradi,

Thanks for the PR, We have created "GHC-1006" as the internal reference to get this reviewed.

One of us will be in touch if there are any changes needed, in most cases this is normally within a couple of weeks but it depends on the current workload of the team.