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 Update operation, this node enables you to update an existing customer's details in your Easy!Appointments system. This is useful in scenarios where customer information changes (such as contact info, address, or custom fields) and you want to keep your appointment management system up-to-date automatically from other workflows.
Practical examples:
- Automatically updating a customer's email or phone number when it changes in your CRM.
- Syncing address or notes fields after a support interaction.
- Updating custom fields based on external triggers or integrations.
Properties
| Name | Type | Meaning |
|---|---|---|
| Customer ID | String | The unique identifier of the customer to update. |
| Additional Fields | Collection | A set of optional fields to update for the customer. See below. |
Additional Fields options:
| Name | Type | Meaning |
|---|---|---|
| First Name | String | First name of the customer |
| Last Name | String | Last name of the customer |
| String | Email of the customer | |
| Phone | String | Phone number of the customer |
| Address | String | Address of the customer |
| City | String | City of the customer |
| ZIP | String | ZIP code of the customer |
| Timezone | String | Timezone of the customer |
| Language | String | Language of the customer |
| Notes | String | Notes for the customer |
| Custom Field 1 | String | Custom field 1 |
| Custom Field 2 | String | Custom field 2 |
| Custom Field 3 | String | Custom field 3 |
| Custom Field 4 | String | Custom field 4 |
| Custom Field 5 | String | Custom field 5 |
| LDAP DN | String | LDAP DN of the customer |
Output
- The output will be a JSON object representing the updated customer as returned by the Easy!Appointments API.
- The structure typically includes all customer fields, both standard and any custom fields that were updated.
- If an error occurs and "Continue On Fail" is enabled, the output will contain an
errorfield with the error message.
Example output:
{
"id": "123",
"firstName": "John",
"lastName": "Doe",
"email": "john.doe@example.com",
"phone": "+1234567890",
"address": "123 Main St",
"city": "Metropolis",
"zip": "12345",
"timezone": "Europe/Berlin",
"language": "en",
"notes": "VIP customer",
"customField1": "Value1",
"ldapDn": "cn=John Doe,ou=users,dc=example,dc=com"
}
Dependencies
- External Service: Requires access to an Easy!Appointments instance with API enabled.
- API Credentials: You must configure the
easyAppointmentsApicredential in n8n, which includes:- Base URL of your Easy!Appointments installation
- Username
- Password
Troubleshooting
Common issues:
- Missing or incorrect Customer ID: If the provided Customer ID does not exist, the API will return an error.
- Invalid credentials or base URL: If the API credentials are incorrect or the URL is wrong, authentication will fail.
- No fields to update: If no additional fields are provided, the request may succeed but have no effect.
- Network errors: Connectivity issues between n8n and the Easy!Appointments server can cause failures.
Error messages:
"Base URL is required": Ensure the Easy!Appointments API credential is configured with a valid URL."Request failed with status code 401": Check your username and password in the credentials."Customer not found"or similar: Verify the Customer ID exists in your Easy!Appointments system.