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 the Customer resource and the Get operation, this node retrieves detailed information about a single customer based on their unique Customer ID. This is useful in scenarios where you need to fetch customer details for use in automations, such as sending personalized emails, updating records in other systems, or integrating appointment data with CRM tools.
Example Use Cases:
- Retrieve customer information to personalize follow-up communications.
- Sync customer data from Easy!Appointments to another database or application.
- Validate customer existence before creating new appointments or records.
Properties
| Name | Type | Meaning |
|---|---|---|
| Customer ID | String | The unique identifier of the customer whose details you want to retrieve. This is required. |
Output
The output will be a JSON object containing all available details for the specified customer. The exact structure depends on the Easy!Appointments API, but typically includes fields such as:
{
"id": "123",
"firstName": "John",
"lastName": "Doe",
"email": "john.doe@example.com",
"phone": "+1234567890",
"address": "123 Main St",
"city": "Sample City",
"zip": "12345",
"timezone": "Europe/Berlin",
"language": "en",
"notes": "",
"customField1": "",
"customField2": "",
"customField3": "",
"customField4": "",
"customField5": "",
"ldapDn": ""
}
Note: The actual fields may vary depending on your Easy!Appointments setup.
Dependencies
- External Service: Requires access to an Easy!Appointments instance with its API enabled.
- Credentials: You must configure
easyAppointmentsApicredentials in n8n, including:- Base URL (e.g.,
https://your-easyappointments-instance/api/v1) - Username
- Password
- Base URL (e.g.,
Troubleshooting
Common Issues:
- Missing or Invalid Customer ID: If the provided Customer ID does not exist, the node will return an error message from the API.
- Authentication Errors: Incorrect credentials or missing API access will result in authentication failures.
- Base URL Not Set: If the base URL is not configured in the credentials, the node will throw a "Base URL is required" error.
Error Messages & Resolutions:
"Base URL is required": Ensure the Easy!Appointments API URL is set in your credentials."Request failed with status code 404": The Customer ID does not exist; verify the ID."Unauthorized"or similar: Check your username and password in the credentials.