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 management resources. Specifically, for the Block Action resource and the PUT release block operation, it allows users to release a previously held block in the booking system. This is useful in scenarios where a block of rooms or inventory that was reserved temporarily needs to be freed up, for example, when a tentative hold on rooms is no longer required.
Practical examples include:
- Releasing a block of rooms after a customer cancels a tentative reservation.
- Managing room inventory dynamically by freeing blocks that are no longer needed.
- Automating workflows that adjust availability based on business rules or external triggers.
Properties
| Name | Meaning |
|---|---|
| Block ID | The unique identifier of the block to perform the release action on. This is a required string input. |
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 regarding the release block action. The exact structure depends on the API response but generally includes confirmation of the block being released or details about the updated block status.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Apaleo API via an API key credential (an access token).
- The node expects the base URL
https://api.apaleo.comand uses JSON content type headers. - Proper permissions on the Apaleo account to perform block actions such as releasing blocks.
Troubleshooting
Common issues:
- Invalid or expired API token: Ensure the API credentials are valid and refreshed if necessary.
- Incorrect Block ID: Verify that the Block ID provided exists and is correct.
- Insufficient permissions: The API user must have rights to modify blocks.
- Network or connectivity problems: Check internet connection and Apaleo service status.
Error messages:
"Block not found": The specified Block ID does not exist; verify the ID."Unauthorized"or"Forbidden": Authentication failed or insufficient permissions; check API credentials."Bad Request": Input parameters may be malformed; ensure Block ID is correctly formatted.
Resolving these typically involves verifying credentials, checking input values, and ensuring the Apaleo API service is operational.
Links and References
- Apaleo API Documentation
- Apaleo Block Management Guide
- n8n Documentation on Creating Custom Nodes