Neo4j Delete Business Hours
AI-generatedOverview
This node deletes all business hours records associated with a specified business in a Neo4j graph database. It is useful when you want to remove the operating hours data for one or more businesses, for example, when a business closes permanently or its schedule needs to be reset.
Typical use cases include:
- Cleaning up outdated or incorrect business hours data.
- Resetting business hours before importing new schedules.
- Removing all operating hours for a business that is no longer active.
The node connects to a Neo4j database using provided credentials, matches the business by its unique ID, and deletes all related BusinessHours nodes linked via the HAS_HOURS relationship.
Properties
| Name | Meaning |
|---|---|
| Business ID | The unique identifier (UUID) of the business whose business hours should be deleted. |
Output
The node outputs JSON data for each processed input item with the following structure:
{
"success": true,
"businessId": "string", // The business ID for which hours were deleted
"nodesDeleted": 0 // Number of nodes deleted (should correspond to business hours nodes)
}
If an error occurs and the node is configured to continue on failure, the output will include an error field describing the issue.
No binary data is produced by this node.
Dependencies
- Requires a Neo4j database accessible via host, port, username, password, and optionally a database name.
- Requires valid Neo4j credentials configured in n8n.
- Uses the official Neo4j driver library to connect and run Cypher queries.
Troubleshooting
- Neo4j credentials are not fully configured: Ensure all required fields (host, port, username, password) are correctly set in the node credentials.
- Failed to establish Neo4j connection: Verify network connectivity to the Neo4j server and that the credentials are correct.
- Neo4j session is not available: This indicates an internal error creating the session; restarting the workflow or n8n might help.
- If multiple items are processed, errors on individual items can be handled gracefully if "Continue On Fail" is enabled.
- Check logs for errors closing the Neo4j session or driver; these usually do not affect execution but indicate resource cleanup issues.