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 bookings and related entities. Specifically, for the Booking resource with the POST Reservations operation, it allows users to add new reservations to an existing booking by sending reservation details in JSON format. This is useful in scenarios where a user needs to programmatically update or extend a booking with additional reservations, such as adding guests or room allocations after the initial booking creation.
Practical examples include:
- Adding multiple guest reservations to a single booking in a hotel management system.
- Automating reservation updates based on external triggers or workflows.
- Integrating with other systems that generate reservation data requiring synchronization with Apaleo.
Properties
| Name | Meaning |
|---|---|
| Booking ID | The unique identifier of the booking to which reservations will be added. |
| Reservations | The reservations data to add, provided in JSON format. This should contain the details of one or more reservations to append to the booking. |
Output
The node outputs an array of JSON objects corresponding to each input item processed. Each output JSON object contains the response from the Apaleo API after attempting to add the reservations to the specified booking. The structure typically includes confirmation of the added reservations or error information if the operation failed.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Apaleo API via an API authentication token (an API key credential).
- The node expects the Apaleo API base URL
https://api.apaleo.com. - Proper credentials must be configured in n8n to authenticate requests.
Troubleshooting
Common issues:
- Invalid or missing Booking ID: Ensure the Booking ID is correct and exists in Apaleo.
- Malformed Reservations JSON: The reservations property must be valid JSON matching Apaleo's expected schema.
- Authentication errors: Verify that the API token is valid and has sufficient permissions.
- Network or API downtime: Check connectivity and Apaleo service status.
Error messages:
- Errors returned from the API are captured and can be output per item if "Continue On Fail" is enabled.
- Typical errors include 400 Bad Request for invalid data, 401 Unauthorized for auth issues, and 404 Not Found if the booking does not exist.
Resolving these usually involves verifying input data correctness, refreshing credentials, and ensuring the booking exists.