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 management of various resources such as bookings, customers, agents, services, payments, orders, coupons, locations, and availability. For the Payments - Delete operation, it allows users to delete a specific payment record by its unique identifier.
Typical use cases include:
- Automating the removal of erroneous or obsolete payment records from LatePoint.
- Integrating payment deletion into workflows that handle refunds or cancellations.
- Maintaining clean payment data by programmatically deleting payments based on business logic.
Example: A workflow could trigger when a refund is processed in another system, then call this node to delete the corresponding payment entry in LatePoint using its ID.
Properties
| Name | Meaning |
|---|---|
| Description | Optional text to describe the purpose or context of this API call for AI understanding. |
| ID | The unique identifier of the payment to delete. This is required to specify which payment to remove. |
Output
The output of the node after executing the delete operation will be a JSON object representing the response from the LatePoint API. Typically, this will confirm the deletion or provide details about the deleted payment.
- The
jsonfield contains the API response object. - If multiple items were returned (not typical for delete), each would be an individual JSON object in the output array.
- No binary data is involved in this operation.
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 Bearer token authorization and expects JSON responses.
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 or missing ID
The delete operation requires a valid payment ID. Providing an empty or incorrect ID will cause the API to fail. Verify the ID before execution.API errors
Errors from the LatePoint API (e.g., payment not found, permission denied) will be returned in the response. Enable "Continue On Fail" in the node settings to handle these gracefully.Invalid JSON body
Although delete does not send a body, other operations might require valid JSON. For delete, ensure no unnecessary body is sent.