Easy!Appointments

Overview

The Easy!Appointments node for n8n allows you to interact with the Easy!Appointments API. Specifically, when using the Appointment resource and the Delete operation, this node enables you to delete an existing appointment by its ID. This is useful in automated workflows where appointments need to be programmatically removed from your scheduling system, such as when a customer cancels or reschedules, or when cleaning up outdated records.

Example scenarios:

• Automatically deleting an appointment if a payment fails.
• Removing test or duplicate appointments during data cleanup.
• Integrating with other systems (e.g., CRM) to keep appointment data synchronized.

Properties

Output

The output for a successful deletion is a JSON object indicating success:

{
  "success": true
}

If an error occurs and "Continue On Fail" is enabled, the output will contain an error message:

{
  "error": "Error message text"
}

Dependencies

• External Service: Requires access to an Easy!Appointments instance with API enabled.
• Authentication: Needs credentials (easyAppointmentsApi) including:
  • Base URL of the Easy!Appointments API
  • Username
  • Password
• n8n Configuration: Credentials must be set up in n8n under the name easyAppointmentsApi.

Troubleshooting

Common Issues:

• Missing or incorrect Appointment ID: If the provided Appointment ID does not exist, the API may return an error.
• Invalid credentials: If the username, password, or base URL are incorrect, authentication will fail.
• Network issues: Connectivity problems between n8n and the Easy!Appointments server can cause failures.

Common Error Messages:

• "Base URL is required": Ensure the API URL is correctly set in the credentials.
• "Request failed with status code 404": The specified Appointment ID does not exist.
• "Request failed with status code 401": Authentication failed; check your credentials.
• "Network Error": There may be connectivity issues; verify network access to the API endpoint.

How to resolve:

• Double-check the Appointment ID.
• Verify that your credentials are correct and have sufficient permissions.
• Ensure the Easy!Appointments API is accessible from your n8n instance.

Links and References

• Easy!Appointments Documentation
• n8n Credentials Documentation
• n8n Error Handling