Neo4J Node Labels¶
Retrieves the list of all node labels available in a connected Neo4J database. It authenticates using the provided credentials, calls the service to fetch labels, and returns a human-readable summary along with machine-readable JSON.
Usage¶
Use this node when you need to discover available labels in your Neo4J graph before constructing queries or building graph exploration workflows. It is commonly used early in a pipeline to inform filtering, schema exploration, or UI selection lists.
Inputs¶
| Field | Required | Type | Description | Example |
|---|---|---|---|---|
| credentials_path | True | STRING | Path or reference to stored Neo4J service credentials configured for the workspace. | |
| timeout | True | INT | Maximum time (in seconds) to wait for the service request before it is aborted. | 60 |
Outputs¶
| Field | Type | Description | Example |
|---|---|---|---|
| text | STRING | Readable summary of the retrieved node labels. | Neo4J Node Labels: ["Person", "Movie", "Company"] |
| json | JSON | Raw data payload containing the node labels. | ["Person", "Movie", "Company"] |
| html | HTML | HTML-formatted output (may be empty for this node unless enhanced rendering is enabled). | |
| xlsx | FILE | Generated spreadsheet file (may be empty for this node unless export is enabled). | |
| FILE | Generated PDF file (may be empty for this node unless export is enabled). |
Important Notes¶
- Credentials required: Ensure valid Neo4J credentials are configured and referenced by the provided credentials_path.
- Timeout behavior: Long-running or slow connections may require increasing the timeout value to avoid premature failures.
- Read-only operation: This node only reads metadata (labels) and does not modify the database.
- Result format: The JSON output is typically an array of label names; downstream nodes can parse it to drive dynamic selections.
Troubleshooting¶
- Empty output: If the JSON array is empty, verify that the database contains nodes and that your user has permissions to read schema metadata.
- Authentication errors: If you receive authentication or authorization errors, confirm the credentials_path points to valid Neo4J credentials and that the user has appropriate access.
- Connection timeouts: Increase the timeout input or check network connectivity, firewall rules, and service availability.
- Unexpected output format: Ensure downstream steps expect a JSON array of strings; if parsing fails, validate that the service response is not an error payload.