> For the complete documentation index, see [llms.txt](https://academy.any2info.com/any2info-academy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.any2info.com/any2info-academy/no-code-platform/data-studio/data-hubs/toolbox/import-and-export/ai/export-to-openai-vectorstore.md).

# Export to OpenAI Vectorstore

**Category:** AI

**Version:** 1.0

**Last updated:** July 6, 2026

**Author:** Any2Info

***

### Description

The **Export To OpenAI Vectorstore** node allows you to upload files from your data flow to an OpenAI Vector Store.\
Vector stores are used to store and index documents so they can be efficiently searched and used in AI.

With this node, you can send one or more files to a selected vector store, making them available for AI processing.

Steps:

1. Select a valid **Connection** to OpenAI
2. Choose the target **Vectorstore**
3. Select the **File(s) column** containing the files
4. Optionally enable **Replace existing**
5. The node uploads the file(s) to the vector store

***

### Configuration Options

| Setting          | Required | Description                                                       |
| ---------------- | -------- | ----------------------------------------------------------------- |
| Connection       | Yes      | Select the OpenAI connection (API key).                           |
| Vectorstore      | Yes      | Select the target vector store where files will be uploaded.      |
| File(s) column   | Yes      | The column that contains the file(s) to upload.                   |
| Replace existing | No       | When enabled, existing files with the same name will be replaced. |

***

### Input

The node expects a column of type **File** or **MultipleFiles**.

* Each row can contain one or multiple files
* Each file includes:
  * File name
  * File content

***

### Replace Existing

The **Replace existing** option controls how duplicate file names are handled.

#### Disabled (default)

* Files are added to the vector store
* Existing files with the same name remain unchanged

#### Enabled

* If a file with the same name already exists in the vector store
* The existing file is replaced with the new version

***

### Output

* The node does **not** modify the data structure
* No additional columns are added
* The original data continues through the data flow

***

### Behavior & Processing

* Each file in the selected column is uploaded to the vector store
* Multiple files per row are processed individually
* All files are uploaded to the same selected vector store

***

### Tips & Best Practices

* Use clear and unique file names
* Enable **Replace existing** when updating documents
* Keep file sizes manageable for faster processing

***

### Changelog

| Version | Date         | Change                               |
| ------- | ------------ | ------------------------------------ |
| 1.0     | July 6, 2026 | Initial documentation version added. |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://academy.any2info.com/any2info-academy/no-code-platform/data-studio/data-hubs/toolbox/import-and-export/ai/export-to-openai-vectorstore.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.