Actions6
- Vector Store Actions
- Graph Database Actions
Overview
This node integrates with a Neo4j database to manage vector stores and graph data. Specifically, for the Vector Store - Add Texts operation, it allows users to add multiple text documents into a Neo4j-backed vector store. This is useful in scenarios where you want to build or update a semantic search index by embedding texts and storing them as vectors for later similarity searches.
Practical examples include:
- Adding new documents or knowledge base articles to a vector store to enable semantic search.
- Incrementally updating an existing vector index with fresh textual data.
- Preparing data for AI-powered retrieval tasks that rely on vector similarity.
Properties
| Name | Meaning |
|---|---|
| Index Name | The name of the vector index to use within Neo4j. Defaults to "vector". |
| Texts | An array of text strings to be added to the vector store. Each string represents a document or piece of content to embed and store. |
Output
The output is a JSON array containing a single object indicating success:
[
{
"success": true
}
]
This confirms that the texts were successfully added to the vector store.
No binary data output is produced by this operation.
Dependencies
- Requires a Neo4j database connection configured via credentials including URI, username, password, and database name.
- Uses an AI embedding input connection to generate vector embeddings for the provided texts before adding them to the vector store.
- Relies on the
@langchain/community/vectorstores/neo4j_vectorpackage for vector store operations.
Troubleshooting
- Missing or invalid credentials: Ensure the Neo4j connection details (URI, username, password, database) are correctly set up in n8n credentials.
- No AI embedding connected: The node expects an embedding input connection when working with vector store resources. Make sure an embedding node is connected and properly configured.
- Invalid texts input: The "Texts" property must be a non-empty array of strings. Empty or malformed inputs may cause errors.
- Database connectivity issues: Network problems or incorrect Neo4j configuration can prevent successful addition of texts.
- Error messages from Neo4j or embedding service: These will be surfaced as node operation errors. Check logs for detailed error descriptions.