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 data. Specifically, for the Booking resource and the GET Booking operation, it retrieves detailed information about a specific booking by its ID. This is useful in scenarios where you need to fetch current booking details for display, reporting, or further processing within an automation workflow.
Practical examples include:
- Retrieving booking details to confirm reservation status before sending a confirmation email.
- Fetching booking information to update a CRM system.
- Accessing booking data to trigger downstream processes like invoicing or guest communication.
Properties
| Name | Meaning |
|---|---|
| Booking ID | The unique identifier of the booking to retrieve. This is required to specify which booking's details should be fetched. |
Output
The node outputs JSON data representing the booking details retrieved from the Apaleo API. The structure typically includes fields such as booking identifiers, guest information, dates, status, and other relevant booking metadata.
If the node supports binary data output (not indicated here), it would represent attachments or documents related to the booking, but this operation primarily returns structured JSON data.
Dependencies
- Requires an API authentication token credential for the Apaleo API.
- The node uses the base URL
https://api.apaleo.comto make requests. - Proper configuration of the API key/credential in n8n is necessary for successful execution.
Troubleshooting
Common issues:
- Invalid or missing Booking ID will cause the API call to fail.
- Expired or incorrect API credentials will result in authentication errors.
- Network connectivity problems can prevent reaching the Apaleo API endpoint.
Error messages:
"Unauthorized"or similar indicates invalid API credentials; verify and update the API key."Not Found"suggests the Booking ID does not exist; double-check the provided ID.- Timeout or network errors require checking internet connection or proxy settings.