You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use the Cloudflare AI Gateway proxied for Google Gemini.
I noticed one thing: GooglePlamApi.credentials supports a custom host attribute, but LmChatGoogleGemini and EmbeddingaGoogleGemini nodes only use this host attribute to retrieve the model list, and do not use the custom host in chat completions and embeddings requests.
In contrast, LmChatOpenAi uses the custom base_url parameter.
To Reproduce
Create a GooglePlamApi credentials with a custom host (e.g., cloudflare ai gateway).
Use the LmChatGoogleGemini node in the workflow.
Chat with any Gemini model.
The logs only requests for list models and do not include chat completion requests.
Expected behavior
The ChatGoogleGenerativeAI class's constructor parameters include base_url, similar to the LmChatOpenAi node, where the base_url parameter is appended when creating an instance of the model.
Operating System
Debian 12.8
n8n Version
1.72.1
Node.js Version
20.18.0
Database
SQLite (default)
Execution mode
main (default)
The text was updated successfully, but these errors were encountered:
Bug Description
I use the Cloudflare AI Gateway proxied for Google Gemini.
I noticed one thing:
GooglePlamApi.credentials
supports a customhost
attribute, butLmChatGoogleGemini
andEmbeddingaGoogleGemini
nodes only use thishost
attribute to retrieve the model list, and do not use the custom host in chat completions and embeddings requests.In contrast,
LmChatOpenAi
uses the custom base_url parameter.To Reproduce
Expected behavior
The ChatGoogleGenerativeAI class's constructor parameters include base_url, similar to the LmChatOpenAi node, where the
base_url
parameter is appended when creating an instance of the model.Operating System
Debian 12.8
n8n Version
1.72.1
Node.js Version
20.18.0
Database
SQLite (default)
Execution mode
main (default)
The text was updated successfully, but these errors were encountered: