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 interacts with the Apaleo API to perform various actions related to booking management. Specifically, for the Block Action resource and the PUT cancel block operation, it allows users to cancel an existing block by providing the block's ID and a reason for cancellation. This is useful in scenarios where a previously reserved or blocked resource (such as a room or service) needs to be released due to changes in plans or errors.
Practical examples include:
- Automatically cancelling a room block when a guest cancels their reservation.
- Releasing held inventory that is no longer needed.
- Managing blocks programmatically as part of a larger workflow for hotel or property management.
Properties
| Name | Meaning |
|---|---|
| Block ID | The unique identifier of the block to perform the cancellation action on. |
| Reason | The explanation or justification for why the block is being cancelled. |
Output
The node outputs JSON data representing the result of the cancellation request. This typically includes confirmation details from the Apaleo API about the cancelled block, such as status updates or metadata confirming the action was successful.
If the node encounters an error during execution, the output will contain an error message describing the issue.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Apaleo API via an API key credential (an API authentication token).
- The node depends on the Apaleo API endpoint
https://api.apaleo.com. - Proper permissions must be granted to the API key to allow block cancellation operations.
Troubleshooting
Common issues:
- Invalid or missing Block ID: Ensure the Block ID provided exists and is correctly formatted.
- Insufficient permissions: The API key used must have rights to modify or cancel blocks.
- Network or connectivity problems: Verify internet access and API availability.
- Missing or empty Reason field: The cancellation reason is required; provide a meaningful explanation.
Error messages:
"Block not found": The specified Block ID does not exist. Verify the ID."Unauthorized"or"Forbidden": Check API credentials and permissions."Validation error": Likely caused by missing required fields like Reason.
Resolving these usually involves verifying input parameters, checking API credentials, and ensuring the Apaleo service is reachable.
Links and References
- Apaleo API Documentation
- Apaleo Blocks API
- n8n documentation on API Credentials