Actions21
Overview
This node integrates with the Easy!Appointments API to manage customer data, specifically allowing you to update existing customer records. It is useful in scenarios where you need to modify customer details such as name, contact information, address, timezone, language preferences, notes, or custom fields within an automated workflow.
For example, you might use this node to update a customer's email and phone number after receiving updated contact info from a form submission or CRM system, ensuring your appointment system always has current customer data.
Properties
| Name | Meaning |
|---|---|
| Customer ID | The unique identifier of the customer to update (required). |
| First Name | The customer's first name. |
| Last Name | The customer's last name. |
| The customer's email address. | |
| Phone | The customer's phone number (may be required depending on Easy!Appointments settings). |
| Additional Fields | A collection of optional fields to further specify customer details: |
| - Address | The customer's physical address. |
| - City | The city where the customer resides. |
| - ZIP | The postal ZIP code of the customer. |
| - Timezone | The customer's timezone (default is "UTC"). |
| - Language | The preferred language of the customer (default is "english"). |
| - Notes | Any additional notes about the customer. |
| - Custom Field 1 | Custom field 1 value for extra customer data. |
| - Custom Field 2 | Custom field 2 value. |
| - Custom Field 3 | Custom field 3 value. |
| - Custom Field 4 | Custom field 4 value. |
| - Custom Field 5 | Custom field 5 value. |
Output
The node outputs JSON data representing the updated customer record as returned by the Easy!Appointments API. This typically includes all customer fields after the update operation, reflecting the new state of the customer in the system.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the Easy!Appointments API.
- Needs an API authentication token or key configured in n8n credentials for Easy!Appointments.
- The base URL of the Easy!Appointments instance must be set in the credentials configuration.
Troubleshooting
- Invalid Customer ID: If the provided Customer ID does not exist, the API will likely return an error indicating the resource was not found. Verify the ID before running the node.
- Missing Required Fields: Although only Customer ID is strictly required for update, some Easy!Appointments configurations may require certain fields like phone or email. Ensure these are provided if needed.
- Invalid JSON in Additional Fields: If any custom fields or notes contain invalid characters or formatting issues, the API might reject the request.
- API Authentication Errors: Ensure that the API key or token is valid and has sufficient permissions to update customer data.
- Network Issues: Connectivity problems to the Easy!Appointments server will cause request failures; check network access and base URL correctness.