Why is it that Embeddings Google Vertex is not available as a regular functional node as shown in integrations?

I have cleaned text content (from scraping) which I want to get text embeddings for. The input text could come from BigQuery or Google Sheets, and I want to use an Google vertex embedding function in n8n.

According to the n8n integrations page, the Google Vertex AI Embeddings node is available as a regular node:

However, in my self-hosted version of n8n, this node is not available in the node selector:

Interestingly, when I try the n8n cloud version, the Vertex AI Embeddings integration does appear, but it’s available as a “tool”, not a typical workflow node - it doesn’t connect to other nodes.

Is Google text embedding (and other vertex AI features) not available as in-built nodes? Or Am I missing something here?

P.S.
I’m aware that I can use http request to call the Google Cloud Console APIs, but I want to use native/in-built nodes if available.

Integrations mentioned:

Information on your n8n setup

  • n8n version: 1.88.0
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Self hosted (npm)
  • Operating system: Windows 11 64-bit

Hey!

The embeddings tool nodes are intended to be connected to AI agent nodes or other nodes that support automatically calling the embeddings tool, like the vector store nodes.

What were you going to do with the embeddings data at your workflow? If you’re for instance trying to build for instance an integration from BigQuery to a vector database, you could use the Google Vertex embeddings by building something like this:

That integrations page does seem a bit misleading, as we don’t currently have a standalone embeddings node like shown on the screenshot there. I’ll raise this up.

Hi @Jaakko
My objective here is to calculate similarity scores using text embedding between different documents I have gathered. What I gather from your response is that, I will have to use custom http request to call text embedding APIs manually.

Yeah, there were several similar instances in integrations section where things were not that clear straightaway. They might need some reviewing.

Thank you for the response!