Neo4J Relationships by Type¶
Fetches relationships from a Neo4J database filtered by a specific relationship type, with an optional limit on the number of results. It handles credential loading and remote service requests, returning a human-readable summary and the raw JSON payload.
Usage¶
Use this node when you need to inspect or export relationships of a specific type from your Neo4J graph (e.g., KNOWS, WORKS_WITH). Typical workflow: provide a valid Neo4J credential path, choose the relationship type, set a result limit, and connect the outputs to viewers or downstream processing nodes.
Inputs¶
| Field | Required | Type | Description | Example |
|---|---|---|---|---|
| credentials_path | True | STRING | Path or reference to the stored Neo4J credentials to authenticate against the database. | |
| timeout | True | INT | Maximum time in seconds to wait for the operation before it times out. | 60 |
| relationship_type | True | STRING | The Neo4J relationship type to filter by. | KNOWS |
| limit | True | INT | Maximum number of relationships to return. | 100 |
Outputs¶
| Field | Type | Description | Example |
|---|---|---|---|
| text | STRING | A formatted text summary of the query results for quick inspection. | Neo4J Relationships by Type: KNOWS — 100 relationships returned. |
| json | STRING | Raw JSON result containing the list of relationships and related metadata. | {"relationships": [{"start":"123","end":"456","type":"KNOWS","properties":{}}], "count": 100} |
Important Notes¶
- Credentials required: You must supply valid Neo4J credentials via credentials_path.
- Relationship type must exist: Ensure the relationship_type matches an existing type in your database.
- Result limiting: limit must be an integer between 1 and 10000.
- Timeouts: Large graphs or complex filtering may require increasing the timeout value.
- Output formats: The node returns a human-readable text summary and a JSON string suitable for parsing or export.
Troubleshooting¶
- Empty results: If you receive no relationships, verify the relationship_type spelling and confirm such relationships exist.
- Invalid JSON downstream: Ensure downstream nodes expecting structured data parse the JSON output field, not the text summary.
- Authentication failures: Double-check the credentials_path points to a valid Neo4J credential and that access is permitted.
- Timeout errors: Increase the timeout input value or reduce the limit to improve responsiveness.