Easy!Appointments icon

Easy!Appointments

Interact with Easy!Appointments API

Actions21

Overview

This node integrates with the Easy!Appointments API to manage providers, appointments, customers, services, and availabilities. Specifically, for the Provider - Delete operation, it deletes a provider record identified by a given Provider ID. This is useful in scenarios where you need to remove a service provider from your appointment system, such as when a provider leaves the organization or their profile needs to be purged.

Practical example:

  • Automatically removing a provider from the scheduling system when they are no longer available to take appointments.

Properties

Name Meaning
Provider ID The unique identifier of the provider to delete

Output

The output JSON contains the response from the Easy!Appointments API after attempting to delete the specified provider. Typically, this will be an empty object or a confirmation message indicating successful deletion. If the deletion fails, the output may contain error details.

No binary data is produced by this operation.

Dependencies

  • Requires an active connection to the Easy!Appointments API.
  • Requires an API authentication token configured in the node credentials.
  • The base URL for the Easy!Appointments API must be set in the node credentials.

Troubleshooting

  • Common issues:

    • Invalid or missing Provider ID: Ensure the Provider ID is correctly provided and exists in the system.
    • Authentication errors: Verify that the API key or authentication token is valid and has sufficient permissions.
    • Network connectivity problems: Confirm that the API endpoint is reachable from n8n.
  • Error messages:

    • "Invalid settings JSON": This error can occur if JSON fields (in other operations) are malformed; not applicable directly to delete but relevant if updating provider settings.
    • HTTP 404 Not Found: The specified Provider ID does not exist.
    • HTTP 401 Unauthorized: Authentication failed; check API credentials.

To resolve errors, verify input parameters, credentials, and network access.

Links and References

Discussion