Google Vertex AI Chat Model node missing GCP region and zone configuration options

[a-d-r-i-a-n-d]

Bug Description

The Google Vertex AI Chat Model node in n8n does not currently provide an option to configure the GCP region and zone for the API calls. This results in the default region being set to us-east, which in my case has a quota of 0, causing an error when trying to use the node. I have already attempted to set the default region and zone within the Google Cloud Console for my GCP project, but this did not resolve the issue.

The absence of a region and zone configuration option within the n8n node presents problems, such as running into quota limitations and potential GDPR concerns when using non-EU zones. This feature is crucial for users who need to specify a region that meets legal requirements or to access available resources in other zones.

A workaround to manually set the GCP region/zone via the node is currently unknown, and guidance would be appreciated in the meantime.

To Reproduce

1. Set up Google Vertex AI Chat Model node: • Go to n8n and create a new workflow. • Add the Google Vertex AI Chat Model node. • Authenticate using your GCP credentials.
2. Attempt to use the node: • Use a default prompt to trigger the chat model. • Ensure that your GCP project’s default region and zone are not set to us-east or that your us-east zone has a quota of 0 (to reproduce the error).
3. Run the workflow: • Run the workflow with the node using the Vertex AI Chat Model. • Actual result: You receive an error due to the default region being set to us-east with a quota of 0, even if the default region/zone is configured in the Google Cloud Console.

Expected behavior

• The Google Vertex AI Chat Model node should include options to set the GCP region and zone, allowing users to choose the appropriate location for their resources. • Users should be able to configure the region and zone directly from the node configuration to avoid quota issues and comply with legal regulations (such as GDPR). • The node should properly use the specified region/zone when making API calls.

Operating System

docker

n8n Version

1.59.4

Node.js Version

v20.17.0

Database

PostgreSQL

Execution mode

main (default)

[Joffcom]

Hey @a-d-r-i-a-n-d,

We have created an internal ticket to look into this which we will be tracking as "GHC-269"

[Joffcom]

Hey @a-d-r-i-a-n-d

Just to check as to me this seems like a feature request as it is adding something new and not fixing a issue.

Do you see this as a bug or also a feature request? This will help with prioritising this.

[a-d-r-i-a-n-d]

Hey @Joffcom,

I appreciate you looking into this. You’re right—it is more of a feature request than a bug, given that it’s about adding new configuration options. I’m currently working on a POC for my team/company using n8n, and due to an existing privacy contract, we can only use Google models. It would be great if we could specify the region and zone in the node itself, as it’s crucial for us to comply with regulations.

[a-d-r-i-a-n-d]

In the meantime if you can think of any workarounds that would be really helpful. Thanks.

[Joffcom]

Hey @a-d-r-i-a-n-d,

I can't think of any for this at the moment as it looks to be a default value.