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 integrates with the Apaleo API to manage reservation-related data. Specifically, for the "Reservation" resource and the "GET reservation services" operation, it retrieves the list of services associated with a particular reservation identified by its ID.
Common scenarios where this node is beneficial include:
- Fetching all ancillary services (e.g., spa, dining, transportation) linked to a guest's reservation.
- Integrating reservation service details into hotel management workflows or reporting tools.
- Automating follow-up actions based on the services booked within a reservation.
For example, a hotel automation workflow might use this node to pull all services tied to a reservation and then trigger notifications or billing processes accordingly.
Properties
| Name | Meaning |
|---|---|
| Reservation ID | The unique identifier of the reservation for which the services are to be retrieved. |
Output
The node outputs an array of JSON objects representing the services linked to the specified reservation. Each object typically contains details about a single service, such as service type, description, pricing, status, and other relevant metadata as defined by the Apaleo API.
If the node supports binary data output (not indicated here), it would represent any associated files or attachments related to the reservation services, but in this case, the output is purely JSON-based.
Dependencies
- Requires an active connection to the Apaleo API via an API authentication token (access token).
- The user must configure the node with valid credentials that provide access to the Apaleo platform.
- Network connectivity to
https://api.apaleo.comis necessary.
Troubleshooting
Common issues:
- Invalid or expired API token leading to authentication errors.
- Providing an incorrect or non-existent Reservation ID resulting in "not found" errors.
- Network connectivity problems causing request timeouts or failures.
Error messages and resolutions:
"Unauthorized"or"Authentication failed": Verify that the API token credential is correctly configured and has not expired."Reservation not found": Confirm that the Reservation ID is correct and exists in the Apaleo system."Request timeout"or"Network error": Check internet connectivity and firewall settings allowing access to the Apaleo API endpoint.