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 - Get operation, it retrieves detailed information about a single service by its ID. This is useful when you want to fetch the current configuration or details of a particular service offered in your Easy!Appointments system.

Common scenarios include:

  • Fetching service details to display or use in workflows.
  • Validating service information before creating or updating appointments.
  • Synchronizing service data with other systems.

Example: You have a service with ID "123" and want to retrieve its name, duration, price, and other attributes to use in subsequent workflow steps.

Properties

Name Meaning
Service ID The unique identifier of the service to retrieve. It must be provided to get the specific service record.

Output

The output is a JSON object representing the service's details as returned by the Easy!Appointments API. This typically includes fields such as:

  • id: The service ID.
  • name: The name of the service.
  • duration: Duration of the service in minutes.
  • price: Price of the service.
  • Additional optional fields like currency, location, description, availability type, number of attendants, privacy status, and service category ID if set.

The node outputs this data under the json property of the item. There is no binary data output for this operation.

Dependencies

  • Requires an active connection to the Easy!Appointments API.
  • Needs an API authentication credential configured in n8n (referred generically as an API key or token).
  • The base URL of the Easy!Appointments instance must be set in the credentials.

Troubleshooting

  • Missing or invalid Service ID: The node requires a valid service ID to fetch the service. Ensure the ID is correct and exists in your Easy!Appointments system.
  • Authentication errors: If the API key or credentials are incorrect or missing, the node will fail to connect. Verify your API credentials and base URL.
  • API connectivity issues: Network problems or incorrect base URL can cause failures. Confirm that the Easy!Appointments API endpoint is reachable.
  • Unexpected API response: If the service ID does not exist, the API may return an error or empty response. Handle such cases gracefully in your workflow.

Links and References

Discussion