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 hotel booking-related operations. Specifically, for the Booking resource and the POST bookings operation, it allows users to create new bookings by sending detailed booking information in JSON format. This is useful in scenarios where automated or programmatic creation of hotel bookings is needed, such as integrating a custom booking system, automating reservation workflows, or syncing bookings from other platforms.
Practical examples include:
- Automatically creating a booking when a customer completes a purchase on an external website.
- Syncing bookings from a CRM or ERP system into Apaleo.
- Creating test bookings during development or QA processes.
Properties
| Name | Meaning |
|---|---|
| Booking Details | The booking details in JSON format. This property expects a JSON object describing all necessary booking information according to Apaleo's booking schema. |
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 create a booking. This typically includes details about the newly created booking such as booking ID, status, guest information, and any metadata returned by the API.
If the node encounters errors and is configured to continue on failure, the output will include error messages alongside empty JSON objects for failed items.
No binary data output is produced by this operation.
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 Apaleo’s API.
- Network connectivity to
https://api.apaleo.comis required.
Troubleshooting
Common issues:
- Invalid or incomplete booking details JSON can cause the API to reject the request.
- Expired or invalid API tokens will result in authentication errors.
- Network issues or incorrect base URL configuration may prevent successful API calls.
Error messages:
- Authentication errors typically indicate problems with the provided API token; refreshing or reconfiguring credentials resolves this.
- Validation errors from the API usually specify which booking details are missing or malformed; ensure the JSON matches Apaleo’s expected schema.
- Rate limiting or server errors from Apaleo should be handled by retrying after some delay.
Links and References
- Apaleo API Documentation
- Apaleo Booking API Guide
- n8n documentation on working with JSON properties