Easy!Appointments

Consume Easy!Appointments API

Actions38

Category → Get

AI-generated

Overview

The Easy!Appointments node for n8n allows you to interact with the Easy!Appointments API. Specifically, when using the Category resource and the Get operation, this node retrieves detailed information about a single category by its ID from your Easy!Appointments system.

Common scenarios:

  • Fetching category details to use in subsequent workflow steps.
  • Validating the existence or properties of a category before creating or updating related records (such as services).
  • Integrating category data into reports or dashboards.

Practical example:
You might use this node to retrieve the name and description of a specific appointment category, then use that information to filter appointments or display category details in an automated email.

Properties

Name Type Meaning
Category ID String The unique identifier of the category to retrieve. This is required.

Output

The output will be a JSON object containing all available details about the requested category. The exact structure depends on the Easy!Appointments API, but typically includes fields such as:

{
  "id": "123",
  "name": "Consultation",
  "description": "General consultation appointments"
}
  • id: The unique identifier of the category.
  • name: The name of the category.
  • description: A description of the category.

Note: Additional fields may be present depending on your Easy!Appointments setup.

Dependencies

  • External Service: Requires access to an Easy!Appointments instance with API enabled.
  • Credentials: You must configure the easyAppointmentsApi credential in n8n, which includes:
    • Base URL of your Easy!Appointments installation
    • Username
    • Password

Troubleshooting

Common issues:

  • Invalid Category ID: If the provided Category ID does not exist, the node will return an error message from the API (e.g., "Category not found").
  • Authentication errors: Incorrect credentials or missing permissions will result in authentication failures.
  • Missing Base URL: If the base URL is not set in the credentials, the node will throw "Base URL is required".

How to resolve:

  • Double-check the Category ID for typos or ensure it exists in your Easy!Appointments system.
  • Verify your API credentials in n8n are correct and have sufficient permissions.
  • Ensure the base URL in your credentials does not end with a slash and is accessible from the n8n server.

Links and References

Discussion