Apaleo icon

Apaleo

Interact with Apaleo API
Join our community

Actions57

Overview

This node integrates with the Apaleo API to perform various actions related to reservations, specifically supporting a "PUT checkout reservation" operation under the "Reservation Action" resource. The primary function of this operation is to check out a guest's reservation, marking the end of their stay in the system.

Common scenarios where this node is beneficial include:

  • Automating the checkout process in hotel management workflows.
  • Integrating Apaleo reservation data with other systems upon guest departure.
  • Triggering downstream processes such as billing or room cleaning after checkout.

For example, a hotel automation workflow could use this node to programmatically check out guests at the end of their stay, ensuring that the reservation status is updated in Apaleo without manual intervention.

Properties

Name Meaning
Reservation ID Filter bookings by reservation ID. This identifies the specific reservation to check out.

Output

The node outputs an array of JSON objects corresponding to each input item processed. Each JSON object contains the response from the Apaleo API for the checkout operation on the specified reservation. The structure typically includes details confirming the successful checkout or error information if the operation failed.

If the node supports binary data output (not indicated explicitly here), it would represent any files or attachments returned by the API, but this operation primarily deals with JSON responses.

Dependencies

  • Requires an active connection to the Apaleo API.
  • Needs an API authentication token (access token) configured in the node credentials.
  • The base URL for API requests is https://api.apaleo.com.
  • Proper permissions on the API key to perform reservation checkout operations.

Troubleshooting

  • Common issues:

    • Invalid or missing Reservation ID will cause the API call to fail.
    • Expired or invalid API access token will result in authentication errors.
    • Network connectivity problems can prevent communication with the Apaleo API.

  • Error messages and resolutions:

    • "Unauthorized" or "Authentication failed": Check and refresh the API credentials.
    • "Reservation not found": Verify the Reservation ID is correct and exists.
    • "Bad Request": Ensure all required parameters are correctly set.
    • If the node throws errors and continueOnFail is disabled, the workflow will stop; enabling it allows processing subsequent items despite failures.

Links and References

Discussion