> For the complete documentation index, see [llms.txt](https://icij.gitbook.io/datashare/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://icij.gitbook.io/datashare/server-mode/create-the-neo4j-graph.md).

# Neo4j

This page explains how to setup Neo4j, install the Neo4j plugin and create a graph on your server

## Prerequisites

### Get Neo4j up and running

Follow the instructions of the [dedicated FAQ page](/datashare/usage/faq/general/how-to-run-neo4j.md) to get Neo4j up and running.

We recommend using a **recent release** of Datashare (`>= 14.0.0`) to use this feature, click on the '**All platforms and versions'** button when downloading to access versions if necessary.

### Add entities

If it's not done yet add entities to your project [using the Datashare CLI](/datashare/server-mode/add-entities-from-the-cli.md).

**If your project contains email documents, make sure to run the `EMAIL` pipeline** together with regular NLP pipeline. To do so set the `--nlpPipeline` flag to `--nlpPipeline CORENLP,EMAIL`.

## Next step

You can now [run Datashare with the Neo4j plugin](/datashare/server-mode/create-the-neo4j-graph/run-datashare-with-the-neo4j-plugin.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://icij.gitbook.io/datashare/server-mode/create-the-neo4j-graph.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.