Easy!Appointments

Overview

The Easy!Appointments n8n node allows you to interact with the Easy!Appointments API. Specifically, for the Unavailability resource and the Get operation, this node retrieves detailed information about a specific unavailability entry by its ID. This is useful in scenarios where you need to fetch and process information about periods when a provider is unavailable (e.g., vacations, breaks, or other absences) within automated workflows.

Practical examples:

• Automatically retrieve and display a provider's unavailability details in a dashboard.
• Integrate unavailability data into scheduling logic to prevent double-booking.
• Use as part of a workflow to notify staff or customers about unavailable time slots.

Properties

Output

The output will be a JSON object containing the details of the requested unavailability. The structure depends on the Easy!Appointments API but typically includes fields such as:

{
  "id": "123",
  "providerId": "456",
  "start": "2024-07-01 09:00:00",
  "end": "2024-07-01 12:00:00",
  "location": "Office",
  "notes": "Vacation"
}

• id: Unique ID of the unavailability.
• providerId: ID of the provider who is unavailable.
• start: Start date and time of the unavailability.
• end: End date and time of the unavailability.
• location: Location associated with the unavailability (if any).
• notes: Additional notes or description.

Note: The actual fields may vary depending on your Easy!Appointments API version and configuration.

Dependencies

• External Service: Requires access to an Easy!Appointments instance with its API enabled.
• API Credentials: You must configure the easyAppointmentsApi credential in n8n, including:
  • Base URL (without trailing slash)
  • Username
  • Password

Troubleshooting

Common issues:

• Missing or incorrect Unavailability ID: If the provided ID does not exist, the node will return an error from the API.
• Invalid credentials or base URL: If authentication fails or the URL is incorrect, you may see errors like "Base URL is required" or HTTP 401/403 errors.
• Network issues: Connectivity problems between n8n and the Easy!Appointments server can cause request failures.

Error messages and resolutions:

• "Base URL is required": Ensure the Easy!Appointments API URL is set correctly in your credentials.
• "Request failed with status code 404": The specified Unavailability ID does not exist; verify the ID.
• "Request failed with status code 401": Authentication failed; check your username and password.

Links and References

• Easy!Appointments Official Website
• Easy!Appointments API Documentation
• n8n Documentation: Credentials