Actions57
- Booking Actions
- Group Actions
- Offer Actions
- Block Actions
- Block Action Actions
- Reservation Actions
- Reservation Action Actions
- Types Actions
- Folio Actions
- Folio Action Actions
Overview
This node interacts with the Apaleo API to manage reservations and their related services. Specifically, for the "DELETE reservation service" operation under the "Reservation" resource, it deletes a specified service from an existing reservation. This is useful in scenarios where a user needs to modify a booking by removing one or more services previously added, such as canceling a spa appointment or transportation service linked to a hotel reservation.
Practical examples include:
- Removing an unwanted additional service from a guest's reservation.
- Adjusting a booking by deleting optional services before final confirmation.
- Automating cleanup of services when a reservation changes or is partially canceled.
Properties
| Name | Meaning |
|---|---|
| Reservation ID | The unique identifier of the reservation from which a service will be deleted. |
| Service ID | The unique identifier of the specific service to delete from the reservation. |
Output
The node outputs an array of JSON objects corresponding to each input item processed. For the "DELETE reservation service" operation, the output JSON typically contains confirmation details about the deletion or the updated state of the reservation after the service removal. The exact structure depends on the Apaleo API response but generally includes status information and identifiers confirming the successful deletion.
No binary data output is expected for this operation.
Dependencies
- Requires an active connection to the Apaleo API.
- Needs an API authentication token (access token) configured via credentials in n8n.
- The base URL for API requests is
https://api.apaleo.com. - Proper permissions on the API key to perform reservation modifications are necessary.
Troubleshooting
Common issues:
- Invalid or missing Reservation ID or Service ID will cause the API call to fail.
- Insufficient permissions on the API token may result in authorization errors.
- Network connectivity problems can prevent communication with the Apaleo API.
Error messages:
"Reservation not found": Verify that the Reservation ID is correct and exists."Service not found": Confirm the Service ID belongs to the specified reservation."Unauthorized"or"Forbidden": Check API credentials and permissions."Request failed"or timeout errors: Ensure network access to Apaleo API endpoint.
Resolving these usually involves verifying input parameters, checking API credentials, and ensuring network connectivity.