Easy!Appointments

Consume Easy!Appointments API

Actions38

Overview

The Unavailability → Delete operation in the Easy!Appointments n8n node allows you to delete a specific unavailability record from your Easy!Appointments system by its ID. This is useful for automating the management of provider schedules, such as removing time slots previously marked as unavailable due to cancellations or changes in staff availability.

Practical scenarios:

  • Automatically clear unavailability when a provider returns to work.
  • Remove blocks on the calendar after resolving scheduling conflicts.
  • Integrate with HR or leave management systems to keep provider calendars up-to-date.

Properties

Name Type Meaning
Unavailability ID String The unique identifier of the unavailability to delete.

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 text"
    }
    

Dependencies

  • External Service: Requires access to an Easy!Appointments API instance.
  • Authentication: Needs valid credentials (username, password, and base URL) configured in n8n under the credential type easyAppointmentsApi.
  • n8n Configuration: The node must be set up with the correct API credentials and the base URL of your Easy!Appointments installation.

Troubleshooting

Common Issues:

  • Invalid or missing Unavailability ID: If the provided ID does not exist, the API may return a "not found" error.
  • Authentication errors: Incorrect username, password, or base URL will result in authentication failures.
  • Network issues: Connectivity problems between n8n and the Easy!Appointments server can cause request failures.

Common Error Messages:

  • "Base URL is required": Ensure the Easy!Appointments API URL is set in your credentials.
  • "Request failed with status code 404": The specified Unavailability ID does not exist.
  • "Request failed with status code 401": Authentication failed; check your credentials.

How to resolve:

  • Double-check the Unavailability ID.
  • Verify your API credentials and base URL.
  • Ensure the Easy!Appointments server is reachable from your n8n instance.

Links and References

Discussion