Easy!Appointments

Consume Easy!Appointments API

Actions38

Overview

The Easy!Appointments node for n8n allows you to interact with the Easy!Appointments API. Specifically, when using the Working Plan resource and the Get operation, this node retrieves the working plan (schedule) of a specific provider by their ID. This is useful in scenarios where you need to automate workflows that depend on a provider's availability, such as scheduling appointments, checking free slots, or synchronizing calendars.

Practical examples:

  • Fetching a provider's weekly schedule to display available time slots on a booking website.
  • Integrating provider availability into automated reminders or notifications.
  • Syncing working plans with other calendar systems.

Properties

Name Type Meaning
Provider ID String The ID of the provider whose working plan you want to retrieve. Required for this action.

Output

The output will be a JSON object representing the provider's working plan. The structure typically includes days of the week as keys, each containing details about start/end times and breaks.

Example output:

{
  "monday": {
    "start": "09:00",
    "end": "18:00",
    "breaks": [
      { "start": "12:00", "end": "13:00" }
    ]
  },
  "tuesday": {
    "start": "09:00",
    "end": "18:00",
    "breaks": []
  }
  // ...other days
}
  • Each day contains:
    • start: Start time of work.
    • end: End time of work.
    • breaks: Array of break periods with their own start and end times.

Dependencies

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

Troubleshooting

Common issues:

  • Missing or incorrect Provider ID: If the Provider ID is missing or invalid, the node will throw an error indicating that the provider could not be found.
  • Invalid credentials or base URL: If the API credentials are incorrect or the base URL is not set, you may see errors like "Base URL is required" or authentication failures.
  • Network/API errors: Any connectivity issues or server-side problems will result in error messages from the API.

How to resolve:

  • Double-check the Provider ID for typos or correctness.
  • Ensure your Easy!Appointments API credentials are correctly configured in n8n.
  • Verify that the Easy!Appointments server is reachable from your n8n instance.

Links and References

Discussion