- Home
- Resources
- Integrations
- Embeddings OpenAI
n8n Embeddings OpenAI nodeConfigure Embeddings OpenAI in n8n.
Every vector store in n8n needs something to turn text into numbers first. The n8n Embeddings OpenAI node is that piece: a sub-node with 7 parameters, no main input of its own, that plugs into the embeddings port of a root node. Built for anyone wiring up a search index or a RAG chatbot.
Verified Trustpilot reviews · AI, automation & growth agency
What does the n8n Embeddings OpenAI node actually do?
It converts text into embeddings, the vectors that let a database compare meaning instead of matching words. It never runs on its own. You attach it to a root node that needs embeddings, that root node feeds it the text, and it hands vectors back. Nothing appears on the canvas after it, because it has no main output of its own.
The clearest scenario is a document search. A Default Data Loader reads a file, a Token Splitter cuts it into chunks, and a Qdrant Vector Store stores them. The store itself has no idea how to vectorize anything, so Embeddings OpenAI sits underneath it and does that step. Templates on n8n.io build exactly this shape, workflow 2846 among them.
The second scenario is answering questions over that index. An AI Agent gets a Vector Store Question Answer Tool, the tool queries the same store, and the same embeddings node runs again so the question is vectorized the same way the documents were. If you swap the model or the dimensions value between indexing and querying, the two sets of vectors stop lining up and the answers go strange.
The third one is smaller and often overlooked: a newsletter or digest that scores incoming items for similarity before anything is written. Workflow 3986 pairs an agent with a Simple Vector Store, RSS content, and Gmail at the end.
When would you use something else? If your goal is a chat completion, a transcription or an image, this is the wrong node and the OpenAI node is the one you want. Embeddings OpenAI does one job and exposes no operations at all, only options.
The known limits are worth reading before you commit. The node has a single version in the catalog, version 1, and its whole surface is the 7 parameters below. There is no retry setting, no chunking, no text cleanup beyond Strip New Lines. Chunk size belongs to the splitter node, not here. And the model provider bills its own API calls under its own terms, while n8n adds nothing on top. If you want a longer look at the platform before going further, the n8n review and the n8n training pages cover it.
What do you connect before the node will run?
- 01
Open the Credentials menu
The node reads an OpenAI credential, and that credential lives in n8n rather than in the node. Create it once from the Credentials menu and every workflow on the instance can reuse it, including the chat model nodes that sit next to this one in a RAG setup. Nothing is stored inside the workflow itself, so exporting the workflow never carries the key with it.
- 02
Paste the API key
The credential page for OpenAI is the same one the other OpenAI nodes use, so if you already built one for a chat model, select it and you are done. A fresh key is created on the OpenAI side, then pasted into the credential form in n8n. Keep in mind that the provider charges its own API calls according to its own terms; n8n does not resell or mark up anything.
- 03
Attach the node to a root node
Drag the node onto the canvas and connect it to the embeddings port of a vector store or a similar root node. Until that link exists, the node has nowhere to send its vectors and the workflow will not execute it. There is no main input line to draw, only the port connection underneath the root node.
Where does this sub-node plug in?
n8n splits AI work between a root node, which receives the workflow items, and sub-nodes attached to its ports, one type of sub-node per port. This node is a sub-node and has no main input at all.
Output (what it plugs into)
- Embeddings
ai_embedding
01Embeddings
The node exposes a single output port of type ai_embedding. A root node that indexes or searches documents opens an embeddings slot underneath itself, and this node fills it.
Key parameters
- Required: the node never runs alone, so the port has to be connected to a root node before anything executes.
Which parameter do you change, and when?
The Embeddings OpenAI node has 7 parameters. For each one: the node as you configure it in n8n, what the parameter changes, and our field notes.
Parameters index
Model
modelWhat you see in n8n
Notes & use cases
This is the only parameter that changes what the vectors actually are. It picks the model which will generate the embeddings, and every other setting on the node only shapes how the request is sent.
Key parameters
- Model: chosen from the option list in the node panel, and it has to stay identical between the run that indexes documents and the run that searches them.
Dimensions
options.dimensionsWhat you see in n8n
Notes & use cases
Vectors have a length, and this option sets it. Fewer dimensions means a smaller index and cheaper storage, more dimensions means finer distinctions between two similar paragraphs.
Key parameters
- Dimensions: the number of dimensions the resulting output embeddings should have, picked from
256,512,1024,1536or3072, and only supported in text-embedding-3 and later models.
Base URL
options.baseURLWhat you see in n8n
Notes & use cases
Requests go to OpenAI by default. Fill this field and they go somewhere else instead, which is what you need when the endpoint is not OpenAI itself.
Key parameters
- Base URL: overrides the default base URL for the API, and the documentation points to it when you run a self-hosted OpenAI-like model.
Batch Size
options.batchSizeWhat you see in n8n
Notes & use cases
Documents are not sent one by one unless you ask for that. This number sets the maximum number of documents to send in each request, which decides how many round trips a large index build costs.
Key parameters
- Batch Size: a number, raised to move a big import faster and lowered when the provider starts pushing back on large requests.
Strip New Lines
options.stripNewLinesWhat you see in n8n
Notes & use cases
Line breaks carry no meaning for an embedding, but they do take up room in the text being sent. The toggle removes them before the request leaves n8n, and it is on by default.
Key parameters
- Strip New Lines: whether to strip new lines from the input text, turned on unless you deliberately turn it off.
Timeout
options.timeoutWhat you see in n8n
Notes & use cases
A request that hangs will block the execution behind it. This value caps how long the node waits before giving up, expressed in seconds.
Key parameters
- Timeout: the maximum amount of time a request is allowed to take in seconds, set to
-1for no timeout at all.
Encoding Format
options.encodingFormatWhat you see in n8n
Notes & use cases
The vectors have to travel back over the network in some shape, and this selector decides which one. It affects the transport, not the meaning of the numbers.
Key parameters
- Encoding Format: the format to return the embeddings in, either
floatorbase64.
Need help automating Embeddings OpenAI with n8n?
A person reads every message.
Questions people ask next
01Is the Embeddings OpenAI node included in n8n?
02What do you need for it to work?
03What are the limits of the n8n Embeddings OpenAI node?
04What should you connect at a minimum to get started?
05n8n or Make for this kind of AI workflow?
Get our weekly integration tips.
No spam. Unsubscribe anytime.

