Easy!Appointments

Consume Easy!Appointments API

Actions38

Overview

The Easy!Appointments node for n8n allows you to interact with the Easy!Appointments API. Specifically, when using the Availability resource with the Get operation, this node retrieves available time slots for a given provider and service on a specified date. This is useful for automating appointment scheduling workflows, checking real-time availability before booking, or integrating appointment data into other systems.

Practical examples:

  • Displaying available appointment slots to customers before confirming a booking.
  • Syncing provider availability with external calendars or CRM systems.
  • Automating reminders or follow-ups based on open time slots.

Properties

Name Type Meaning
Provider ID String The unique identifier of the provider whose availability you want to check.
Service ID String The unique identifier of the service for which availability is being checked.
Date String The date to check availability (format: YYYY-MM-DD).

Output

The output will be a JSON object (or array) representing the available time slots for the specified provider, service, and date. The exact structure depends on the Easy!Appointments API, but typically includes details such as start/end times and possibly additional metadata about each slot.

Example output structure:

[
  {
    "start": "2024-07-01T09:00:00",
    "end": "2024-07-01T09:30:00",
    "available": true
  },
  {
    "start": "2024-07-01T10:00:00",
    "end": "2024-07-01T10:30:00",
    "available": false
  }
]

Note: The actual fields may vary depending on your Easy!Appointments API version/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 credentials: If the base URL, username, or password are missing or incorrect, the node will throw an error such as "Base URL is required" or authentication errors.
  • Invalid input values: Supplying an invalid provider ID, service ID, or incorrectly formatted date may result in API errors or empty results.
  • API connectivity issues: Network problems or incorrect API endpoint configuration can cause request failures.

Error messages and resolutions:

  • "Base URL is required": Ensure the Easy!Appointments API URL is set correctly in your credentials.
  • Authentication errors: Double-check your username and password in the n8n credentials.
  • Empty or unexpected output: Verify that the provider ID, service ID, and date exist and are valid in your Easy!Appointments system.

Links and References

Discussion