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
The node provides integration with the LatePoint REST API, specifically enabling management of various booking-related resources such as services, bookings, customers, agents, payments, orders, coupons, and locations. The "Update" operation for the "Services" resource allows users to modify existing service records by sending updated data to the LatePoint API.
This node is beneficial in scenarios where you need to programmatically update service details within a booking system, such as changing the service name, duration, pricing, or visibility without manual intervention. For example, if a service's price changes or its availability status needs updating, this node can automate that process within an n8n workflow.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the service to update. This is required to specify which service record will be modified. |
| Description | A text description or prompt to provide context or purpose for the API call (mainly for AI understanding). |
| Send Body | Boolean flag indicating whether to send a custom JSON body or form data instead of individual fields. |
| Body Content Type | When "Send Body" is true, specifies the format of the request body: either JSON or Form Data. |
| JSON Body | A raw JSON object string to send as the request body when "Send Body" is true and "Body Content Type" is JSON. Allows full control over the update payload. |
| Form Data | Collection of 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 service fields to update when not sending a custom body. These include: |
| - Name | The name of the service. |
| - Short Description | A brief description of the service. |
| - Duration (minutes) | Duration of the service in minutes. Defaults to 60. |
| - Charge Amount | The charge amount for the service, with two decimal precision. |
| - Deposit Amount | The deposit amount required for the service, with two decimal precision. |
| - Category ID | Identifier for the category the service belongs to. |
| - Order Number | Numeric order number for sorting or display purposes. Defaults to 1. |
| - Visibility | Visibility status of the service; options are "Public" or "Private". |
Output
The node outputs the JSON response returned by the LatePoint API after performing the update operation on the service. The output JSON typically contains the updated service object with all its properties reflecting the new state.
If multiple items are returned (though unlikely for an update), each item is output separately. There is no binary data output from this node.
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 header.
- No additional external dependencies beyond the LatePoint API and proper credential setup.
Troubleshooting
No credentials configured!
Error thrown if the API key credential is missing. Ensure the API key is set up correctly in n8n credentials.Invalid JSON in body:
Occurs if the JSON Body property contains malformed JSON. Validate the JSON syntax before running.Invalid JSON in bulk bookings:
Not applicable here but similar error may occur if bulk JSON input is malformed.HTTP errors from API:
Could be due to invalid service ID, insufficient permissions, or incorrect field values. Check the API response message for details.Empty or missing ID:
The update operation requires a valid service ID. Make sure the ID field is populated.
Links and References
This summary covers the "Update" operation for the "Services" resource based on the provided source code and property definitions.