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, enabling automation of booking management and related operations. Specifically, for the Services resource with the Delete operation, it allows users to delete a service by specifying its unique identifier. This is useful in scenarios where services are no longer offered or need to be removed from the system.
Practical examples include:
- Automatically removing discontinued services from your booking platform.
- Cleaning up test or temporary services after a campaign.
- Managing service lifecycle programmatically as part of business workflows.
Properties
| Name | Meaning |
|---|---|
| Description | A text field where you can describe the purpose or context of this API call for AI assistance. |
| ID | The unique identifier of the service to delete. This is required to specify which service to remove. |
Output
The node outputs JSON data representing the response from the LatePoint API after attempting to delete the specified service. Typically, this will confirm whether the deletion was successful or provide error details if it failed.
- The output
jsonfield contains the API response object. - No binary data output is involved in this operation.
Dependencies
- Requires an API key credential configured for the LatePoint REST API.
- The node uses the base URL and API key from these credentials to authenticate requests.
- Network access to the LatePoint API endpoint is necessary.
Troubleshooting
- Missing Credentials Error: If no API credentials are configured, the node throws an error "No credentials configured!". Ensure that a valid API key credential is set up in n8n.
- Invalid ID: Providing an incorrect or non-existent service ID may result in an API error indicating the service could not be found or deleted.
- API Errors: Any errors returned by the LatePoint API (e.g., permission denied, invalid request) will be passed through in the output JSON. Review the message for troubleshooting.
- JSON Parsing Errors: Not applicable for Delete operation since no body JSON is sent.
- Network Issues: Connectivity problems to the LatePoint API will cause request failures.
Links and References
- LatePoint REST API Documentation - Official API docs for authentication and endpoints.
- LatePoint Authentication Guide - Details on how to obtain and use API keys.
This summary focuses exclusively on the Services resource with the Delete operation as requested.