Actions38
- Appointment Actions
- Availability Actions
- Category Actions
- Customer Actions
- Provider Actions
- Secretary Actions
- Service Actions
- Settings Actions
- Unavailability Actions
- Working Plan Actions
Overview
The Easy!Appointments n8n node allows you to interact with the Easy!Appointments API, specifically for managing services.
For the Service → Get operation, this node retrieves detailed information about a specific service by its ID from your Easy!Appointments instance.
Common scenarios:
- Fetching details of a particular service to display or use in subsequent workflow steps.
- Validating service existence before booking appointments.
- Integrating service data into other business processes (e.g., reporting, synchronization).
Example use cases:
- Retrieve all properties of a service to show them in an email or notification.
- Use service details as input for another system (e.g., CRM, ERP).
- Check service parameters before creating or updating related records.
Properties
| Name | Type | Meaning |
|---|---|---|
| Service ID | String | The unique identifier of the service to retrieve. This is required and specifies which service's details will be fetched from Easy!Appointments. |
Output
The output will be a JSON object containing all available details about the requested service.
The structure typically includes fields such as:
{
"id": "123",
"name": "Consultation",
"duration": 60,
"price": 100,
"currency": "EUR",
"description": "A one-hour consultation session.",
"location": "Room 101",
"categoryId": "5",
"availabilitiesType": "default",
"attendantsNumber": 1,
// ...other service-specific fields
}
- All fields returned are directly from the Easy!Appointments API for the given service.
- No binary data is produced by this operation.
Dependencies
- External Service: Requires access to an Easy!Appointments server with API enabled.
- API Credentials: You must configure the
easyAppointmentsApicredential in n8n, including:- Base URL (without trailing slash)
- Username
- Password
Troubleshooting
Common issues:
- Missing or incorrect Service ID: If the provided Service ID does not exist, the node will return an error from the API.
- Invalid credentials or base URL: If authentication fails or the URL is wrong, you'll receive an authentication or connection error.
- Network issues: If n8n cannot reach the Easy!Appointments server, a network error will occur.
Error messages and resolutions:
"Base URL is required": Ensure the Easy!Appointments API URL is set correctly in your credentials."401 Unauthorized"or similar: Double-check your username and password in the credentials."404 Not Found": The Service ID does not exist; verify the ID is correct."ECONNREFUSED"or timeout errors: Make sure your n8n instance can reach the Easy!Appointments server (check firewall, VPN, etc.).