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 Service resource and the Get Many operation, this node retrieves a list of services from your Easy!Appointments instance. This is useful for scenarios where you need to fetch available services, filter them by category, paginate through results, or search for specific services.

Practical examples:

  • Displaying all available services on a website.
  • Filtering services by category for reporting or analytics.
  • Integrating service data into other business workflows.

Properties

Name Type Meaning
Filters Collection A group of optional filters to refine the list of returned services.
└ Page Number Page number for pagination (default: 1).
└ Length Number Number of results per page (default: 10).
└ Sort String Field and direction to sort by (e.g., "id asc").
└ Query String Search query string to filter services.
└ Category ID String Filter services by a specific category ID.

Output

  • The output is a JSON array containing service objects as returned by the Easy!Appointments API.
  • Each object typically represents a service and may include fields such as:
    • id
    • name
    • duration
    • price
    • currency
    • description
    • location
    • categoryId
    • ...and other service-related properties defined in your Easy!Appointments system.

Example output:

[
  {
    "id": 1,
    "name": "Consultation",
    "duration": 30,
    "price": 50,
    "currency": "EUR",
    "description": "Initial consultation session.",
    "location": "Room 101",
    "categoryId": "cat123"
  },
  ...
]

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
    • Username
    • Password

Troubleshooting

Common issues:

  • Invalid credentials: If the username or password is incorrect, authentication will fail.
  • Missing Base URL: If the base URL is not set in the credentials, the node will throw "Base URL is required".
  • Network errors: Connectivity issues between n8n and the Easy!Appointments server can cause failures.
  • Incorrect filter values: Using invalid filter parameters may result in empty responses or API errors.

Error messages:

  • "Base URL is required": Ensure the Easy!Appointments API URL is correctly set in your credentials.
  • Authentication errors: Double-check your username and password.
  • API-specific errors: Review the error message returned in the error field of the output if Continue On Fail is enabled.

Links and References

Discussion