Easy!Appointments

Consume Easy!Appointments API

Actions38

Service → Delete

AI-generated

Overview

The Easy!Appointments node for n8n allows you to interact with the Easy!Appointments API. Specifically, when using the Service resource and the Delete operation, this node enables you to delete a service from your Easy!Appointments system by specifying its Service ID.

Common scenarios:

  • Automating the removal of outdated or deprecated services from your appointment booking system.
  • Integrating service deletion into larger workflows, such as after archiving related appointments or categories.
  • Keeping your Easy!Appointments instance synchronized with another system where services may be managed.

Practical example:
If you have a workflow that manages your business offerings and a service is discontinued, you can use this node to automatically remove it from Easy!Appointments when triggered by an external event (e.g., a product is removed from your inventory system).

Properties

Name Type Meaning
Service ID String The unique identifier of the service to delete. This is required to specify which service will be removed from Easy!Appointments.

Output

  • On successful deletion, the output will be:
    {
  "success": true
}
  • If an error occurs and "Continue On Fail" is enabled, the output will include:
    {
  "error": "<error message>"
}

No additional data is returned upon successful deletion.

Dependencies

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

Troubleshooting

Common issues:

  • Missing or incorrect Service ID: If the Service ID does not exist or is mistyped, the API will return an error indicating the service was not found.
  • Authentication errors: Invalid credentials or missing API configuration will result in authentication failures.
  • Base URL not set: If the base URL is missing in the credentials, the node will throw a "Base URL is required" error.

Error messages and resolutions:

  • "Base URL is required": Ensure the Easy!Appointments API credential has a valid URL.
  • "Request failed with status code 404": The specified Service ID does not exist; verify the ID.
  • "Unauthorized" or similar: Check your username and password in the credentials.

Links and References

Discussion