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 perform various operations related to hotel reservations and their management. Specifically, for the Reservation Action resource with the operation PUT mark reservation as no-show, it marks a given reservation as a "no-show" — indicating that the guest did not arrive for their booking.
This functionality is useful in hotel management workflows where you need to update the status of reservations automatically or via automation when guests fail to check in. For example, after the scheduled check-in time passes without arrival, this node can be triggered to mark the reservation accordingly, which may then trigger billing or reporting processes.
Properties
| Name | Meaning |
|---|---|
| Reservation ID | The unique identifier of the reservation to mark as no-show. This filters bookings by the specific reservation ID. |
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 confirming the reservation has been marked as no-show. The exact structure depends on the API response but typically includes updated reservation details or status confirmation.
No binary data output is produced by 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 requests is
https://api.apaleo.com. - Proper permissions on the API key are necessary to modify reservation statuses.
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 successful API communication.
- Insufficient permissions on the API token may block the operation.
Error messages:
"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 provided and valid.
Resolutions:
- Confirm the Reservation ID matches an existing booking.
- Re-authenticate or update the API credentials in n8n.
- Check network settings and firewall rules.
- Review API user permissions in Apaleo dashboard.