# Neo4j Output
##  Neo4j Output
### Description
The Neo4j Output transform allows you to do high performance updates in one node, two nodes or two nodes and a relationship.
The transform generates the required Cypher statements with accompanying parameters.
| Hop Engine | ✓ |
| ---------- | ------------ |
| Spark | ✓ |
| Flink | ✓ |
| Dataflow | ✓ |
### Usage
You can update one node or two nodes and a relationship. Nodes and relationships can have properties and the appropriate MERGE statements will be generated based on the information you provided. Make use of the "Get fields" buttons on the right hand side of the dialog to prevent you from having to type too much.
### Labels
You can get one node labels from a list of fields or you can use static values (with optionally variables). If you specify both the static value will be used if the field value is null. A label will not be used for the node if the label is null or empty.
### Notable options
| Option | Description |
| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Batch size | for better performance the transform will group records together in a single transaction |
| Use CREATE instead of MERGE | this bypasses any lookup and is faster. |
| Create indexes | creates unique field constraints for all Primary properties in the nodes to make sure performance stays good when dealing with merges and lookup of nodes for relationships. **NOTE:** Please consider only using this when doing prototyping and testing. It’s better to put the index creation statements explicitly in a Cypher Script action to make sure you never forget it even when moving to a new database. |
---
# Agent Instructions: 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:
```
GET https://docs.primeur.com/data-shaper-1.21/knowing-the-data-shaper-designer/pipelines/transforms/neo4j-output.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.