Neo4j Find Services by Business
AI-generatedOverview
This node queries a Neo4j graph database to find all service items offered by a specified business. It is useful when you want to retrieve detailed information about services linked to a particular business entity stored in Neo4j.
Typical use cases include:
- Fetching all services provided by a business for display or further processing.
- Integrating Neo4j data into workflows that require business-service relationships.
- Data enrichment or reporting based on services associated with businesses.
For example, given a business ID, the node returns all related service nodes connected via an "OFFERS" relationship.
Properties
| Name | Meaning |
|---|---|
| Business ID | The unique identifier (UUID) of the business whose services you want to query. |
Output
The output consists of JSON objects representing each service node connected to the specified business. Each service object includes all properties of the service node plus its service_id.
Output structure example:
{
"service": {
"service_id": "string",
"property1": "...",
"property2": "...",
"...": "..."
}
}
If multiple input items are processed, the output will be an array of such service objects aggregated from all inputs.
No binary data is produced by this node.
Dependencies
- Requires a Neo4j database accessible via host, port, username, and password credentials.
- Needs a configured API key credential for Neo4j authentication.
- Uses the official Neo4j driver library to connect and run Cypher queries.
- The node expects the Neo4j database to have
Businessnodes with abusiness_idproperty andServicenodes connected byOFFERSrelationships.
Troubleshooting
- Missing or incomplete credentials: The node throws an error if Neo4j connection details (host, port, username, password) are missing or incomplete. Ensure all required fields are set correctly.
- Connection failures: Errors during driver connection or session creation indicate network issues or incorrect credentials. Verify connectivity and credentials.
- Cypher query errors: If the query fails, the node attempts to parse and report the error. Common causes include incorrect property names or schema mismatches.
- Session closure errors: Errors closing the Neo4j session or driver are logged but do not stop execution.
- Continue on fail: If enabled, the node continues processing other items even if one item causes an error, returning error details alongside successful results.
Links and References
- Neo4j Official Documentation
- Neo4j Cypher Query Language
- n8n Neo4j Integration Guide (general reference)