Easy!Appointments

Consume Easy!Appointments API

Actions38

Category → Create

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 Create operation, this node enables you to create a new category in your Easy!Appointments system. This is useful for organizing services or appointments into logical groups, such as "Consultations", "Therapies", or "Workshops".

Common scenarios:

  • Automating the setup of new categories when onboarding new service types.
  • Integrating with other systems to synchronize category data.
  • Batch creation of categories based on external triggers or data sources.

Example:
Automatically create a new "Online Consultation" category whenever a new type of online service is added in your CRM.

Properties

Name Type Meaning
Additional Fields Object A collection of fields for the new category. See below for details.

Fields within "Additional Fields":

Name Type Meaning
Name String Name of the category
Description String Description of the category

Output

The output will be a JSON object representing the newly created category as returned by the Easy!Appointments API. The exact structure depends on the API response, but typically includes at least the following fields:

{
  "id": "123",
  "name": "Category Name",
  "description": "Description of the category",
  // ...other possible fields from the API
}

If an error occurs and "Continue On Fail" is enabled, the output will include an error field with the error message.

Dependencies

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

Troubleshooting

Common issues:

  • Missing or incorrect credentials: Ensure the API URL, username, and password are correct and that the user has permission to create categories.
  • Base URL is required: If the base URL is missing in credentials, the node will throw "Base URL is required".
  • Invalid input: If required fields (like "Name") are not provided, the API may reject the request.
  • API connection errors: Network issues or wrong endpoint URLs can cause failures.

Error messages:

  • "Base URL is required": Set the correct API URL in your credentials.
  • API-specific errors (e.g., validation errors) will be returned in the output if "Continue On Fail" is enabled.

Links and References

Discussion