Neo4J Relationship Types¶
Retrieves all relationship types defined in a Neo4J database. It connects using a provided database URI, calls the Neo4J data connector to fetch types, and returns both a human-readable summary and the raw JSON.
Usage¶
Use this node when you need to inspect or discover the available relationship types in a Neo4J graph before building queries, schema exploration, or analytics. Typically placed early in a workflow to inform downstream nodes (e.g., querying relationships by type).
Inputs¶
| Field | Required | Type | Description | Example |
|---|---|---|---|---|
| credentials_path | True | STRING | Neo4J connection URI. Must include protocol, host, optional port, and optional database (e.g., bolt, bolt+s, neo4j, neo4j+s). | bolt://neo4j: |
| timeout | True | INT | Request timeout in seconds for the data connector call. | 60 |
Outputs¶
| Field | Type | Description | Example |
|---|---|---|---|
| result | STRING | Human-readable summary of the retrieved relationship types. | Neo4J Relationship Types: KNOWS, LIKES, WORKS_WITH |
| json_result | STRING | Raw JSON string of the relationship types returned by the service. | ["KNOWS", "LIKES", "WORKS_WITH"] |
| html_table | STRING | HTML table representation (empty when using default text output). | |
| xlsx_data | STRING | Base64-encoded XLSX data (empty when using default text output). | |
| pdf_data | STRING | Base64-encoded PDF data (empty when using default text output). |
Important Notes¶
- Credentials URI required: The credentials_path must be a valid Neo4J-style URI (e.g., bolt://, bolt+s://, neo4j://, neo4j+s://).
- Service endpoint dependency: This node calls the Neo4J data connector service; ensure the 'neo4j_data_connector' endpoint is configured in ENDPOINTS.
- Output formats: By default, only text and JSON outputs are populated. HTML/XLSX/PDF outputs are empty unless a node explicitly generates those formats.
- Scope of results: Returned relationship types reflect what's present in the target database and may change as the graph evolves.
Troubleshooting¶
- Invalid credentials URI: If you see an error about an invalid credentials URI, verify the scheme, host, port, and query parameters in credentials_path.
- Connection or auth failures: If the request fails, confirm the service endpoint is reachable, the database is running, and the username/password in the URI are correct.
- Empty results: If no relationship types are returned, ensure your database contains relationships or check that you are connecting to the intended database.
- Timeouts: Increase the timeout input if the database or network is slow.