Actions40
- Bookings Actions
- Customers Actions
- Agents Actions
- Services Actions
- Payments Actions
- Orders Actions
- Coupons Actions
- Locations Actions
- Availability Actions
- System Info Actions
- Test Actions
Overview
This node provides integration with the LatePoint REST API, specifically enabling operations on various resources such as bookings, customers, agents, services, payments, orders, coupons, and locations. For the Customers - Update operation, it allows updating an existing customer's information by specifying their unique identifier and the fields to update.
Typical use cases include:
- Modifying customer details like name, email, or phone number in a CRM system.
- Correcting or enriching customer data after initial creation.
- Automating updates to customer records based on external triggers or workflows.
For example, you might update a customer's phone number or add notes about recent interactions.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the customer to update. This is required to specify which customer record will be modified. |
| Description | A text description or prompt explaining the purpose of this API call, helping AI understand the context. |
| Send Body | Whether to send a custom JSON body or form data instead of using individual fields. If enabled, you can provide the entire request body manually. |
| Body Content Type | When sending a custom body, choose between JSON or Form Data format for the request payload. |
| JSON Body | The raw JSON object to send as the request body when "Send Body" is true and "Body Content Type" is JSON. Useful for complex or nested updates. |
| Form Data | Key-value pairs to send as form data when "Send Body" is true and "Body Content Type" is Form Data. |
| Additional Fields | Collection of individual fields to update on the customer record when not sending a custom body. Includes: • First Name — Customer's first name. • Last Name — Customer's last name. • Email — Customer's email address (optional but must be valid and unique if provided). • Phone — Customer's phone number. |
Output
The node outputs the updated customer data in the json field of the output item. The structure corresponds to the response from the LatePoint API for the updated customer resource, typically including all customer properties after the update.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the LatePoint REST API.
- The base URL and API key must be configured in the node credentials.
- The node sends HTTP requests with JSON content type and Bearer token authorization.
Troubleshooting
- Invalid JSON in body: If providing a custom JSON body, ensure it is valid JSON syntax. Errors parsing JSON will cause the node to throw an error.
- Missing or invalid ID: The update operation requires a valid customer ID. Omitting or providing an incorrect ID will result in API errors.
- Authentication errors: Ensure the API key credential is correctly set up and has permissions to update customer records.
- Validation errors: Providing invalid or duplicate email addresses may cause the API to reject the update.
- Network or API errors: Check connectivity and API status if requests fail unexpectedly.