Easy!Appointments icon

Easy!Appointments

Interact with Easy!Appointments API
Join our community

Actions21

Overview

This node integrates with the Easy!Appointments API to manage various resources such as appointments, customers, providers, services, and availabilities. Specifically, for the Service resource with the Delete operation, it allows users to delete a service record by specifying its unique Service ID.

Common scenarios where this node is beneficial include automating the management of appointment-related data in Easy!Appointments, such as removing obsolete or discontinued services programmatically within an automated workflow.

For example, if a business no longer offers a particular service, this node can be used to delete that service from Easy!Appointments automatically when triggered by certain events or conditions.

Properties

Name Meaning
Service ID The unique identifier of the service to delete

Output

The output JSON contains the response from the Easy!Appointments API after attempting to delete the specified service. Typically, this will be a confirmation of deletion or an error message if the deletion failed.

  • The json field holds the API response object.
  • No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Easy!Appointments API.
  • Needs an API authentication credential configured in n8n (e.g., an API key or token).
  • The base URL for the Easy!Appointments instance must be set in the node credentials.

Troubleshooting

  • Common issues:
    • Providing an invalid or non-existent Service ID will result in an error from the API.
    • Network connectivity problems or incorrect API credentials will cause request failures.
  • Error messages:
    • Errors returned by the API typically indicate why the deletion failed (e.g., "Service not found").
    • If the node throws an error about invalid credentials or connection issues, verify the API key/token and base URL configuration.
  • To resolve errors, ensure the Service ID is correct and the API credentials are valid and have sufficient permissions.

Links and References

Discussion