Actions45
- Block Actions
- Block Action Actions
- Booking Actions
- Group Actions
- Offer Actions
- Reservation Actions
- Folio Actions
- Types Actions
Overview
This node interacts with the Apaleo API to manage various booking-related resources, including reservations. Specifically, for the DELETE reservation service operation, it deletes a particular service associated with a given reservation. This is useful in scenarios where a user needs to remove an unwanted or canceled service from an existing reservation, such as removing a spa treatment or airport transfer that was previously booked.
Practical examples:
- A hotel front desk agent removes a breakfast service from a guest’s reservation.
- An automated workflow cancels an added car rental service when a reservation is modified.
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 JSON data representing the result of the deletion operation. Typically, this would include confirmation that the service was successfully removed or details about the updated reservation state. The exact structure depends on the Apaleo API response but generally confirms the deletion action.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Apaleo API.
- Needs an API authentication token (access token) configured in the node credentials to authorize requests.
- The base URL for API calls is
https://api.apaleo.com. - Proper permissions on the API key are necessary to perform deletion operations on reservation services.
Troubleshooting
Common issues:
- Invalid or missing Reservation ID or Service ID parameters will cause the API call to fail.
- Insufficient API permissions can lead to authorization errors.
- Network connectivity problems may prevent successful API communication.
Common error messages and resolutions:
- "Unauthorized" or "Forbidden": Check that the API token is valid and has the required scopes.
- "Not Found": Verify that both Reservation ID and Service ID exist and are correct.
- "Bad Request": Ensure all required parameters are provided and correctly formatted.
- If the node throws an error but "Continue On Fail" is enabled, the error message will be included in the output JSON under an
errorfield.