Neo4j Find Available Slots ResourceOnlyInstall

Overview

This node queries a Neo4j database to find available booking time slots for a specified business, service, and required resource type within a given date/time range. It operates in "ResourceOnly" mode, meaning it focuses on resource availability without considering other constraints like staff or location.

Typical use cases include appointment scheduling systems where you need to check when certain resources (e.g., rooms, equipment) are free to be booked for a service of known duration. For example, a spa might want to find all available 15-minute intervals where a massage room (resource) is free to accommodate a massage service.

The node:

• Validates input parameters including business ID, service ID, date/time range, slot interval, required resource type, and capacity.
• Connects to Neo4j using provided credentials.
• Retrieves business hours, service duration, and resource type details.
• Generates potential time slots within the requested range at the specified interval.
• Checks each slot for resource availability based on capacity.
• Returns a list of available slots adjusted to the appropriate timezone.

Properties

Output

The node outputs JSON data containing:

• availableSlots: An array of ISO 8601 datetime strings representing available booking start times.
• timezone: The timezone string used for the returned slots (detected from query or business settings).
• mode: Always "ResourceOnly" indicating the mode of operation.
• serviceId: The service ID used in the query.
• serviceDuration: Duration of the service in minutes.
• resourceType: The name of the resource type or its ID if name unavailable.
• resourceTypeId: The resource type ID.
• requiredCapacity: Number of resources required.
• totalCapacity: Total capacity available for the resource type.
• resourceDescription: Description of the resource type if available.

No binary data output is produced by this node.

Dependencies

• Requires a Neo4j database connection configured via an API key credential with host, port, username, password, and optionally database name.
• Uses the neo4j-driver package to connect and run Cypher queries.
• Relies on helper modules for date/time normalization, timezone detection, and availability checks.
• Requires proper configuration of the Neo4j instance with relevant nodes and relationships for businesses, services, resource types, and business hours.

Troubleshooting

• Missing Required Resource Type ID: The node throws an error if the required resource type ID is not provided.
• Invalid Credentials: Errors occur if Neo4j credentials are incomplete or incorrect.
• Invalid Date/Time Format: Input dates must be valid ISO 8601 strings with timezone information.
• No Matching Records: If no business, service, or resource type matches the provided IDs, an error is thrown.
• Insufficient Resource Capacity: If the total capacity of the resource type is less than the required capacity, the node errors out.
• Neo4j Connection Failures: Network issues or misconfiguration can cause connection errors.
• Availability Check Failures: Individual slot checks may fail silently and log debug messages; these do not stop execution but reduce available slots.

To resolve errors:

• Verify all UUID inputs are correct and exist in the database.
• Ensure Neo4j credentials are properly set up in n8n.
• Confirm date/time inputs are correctly formatted and include timezone.
• Check Neo4j server accessibility and logs for connectivity issues.
• Review resource capacities and adjust requirements accordingly.

Links and References

• Neo4j Official Documentation
• ISO 8601 Date and Time Format
• Luxon DateTime Library
• n8n Documentation - Creating Nodes