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 operations related to hotel management resources. Specifically, for the Block Action resource and the PUT confirm Block operation, it sends a request to confirm a block identified by its Block ID. This is useful in scenarios where a temporary hold or reservation block on rooms needs to be confirmed to guarantee availability.
Practical examples include:
- Confirming a room block after initial tentative booking.
- Finalizing a group booking block before issuing contracts.
- Automating confirmation workflows in property management systems integrated with Apaleo.
Properties
| Name | Meaning |
|---|---|
| Block ID | The unique identifier of the block to perform the confirm action on. |
Output
The node outputs an array of JSON objects corresponding to each input item processed. Each JSON object contains the response from the Apaleo API confirming the block. The exact structure depends on the API response but typically includes details about the confirmed block status and metadata.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Apaleo API.
- Needs an API authentication token (access token) configured in the node credentials.
- The base URL used is
https://api.apaleo.com. - Proper permissions on the API key to perform block actions are necessary.
Troubleshooting
- Common issues:
- Invalid or expired API token causing authentication failures.
- Incorrect Block ID leading to "not found" errors.
- Insufficient permissions for the API key to confirm blocks.
- Error messages:
"Unauthorized": Check that the API token is valid and has not expired."Block not found": Verify the Block ID is correct and exists."Forbidden": Ensure the API key has rights to perform block confirmations.
- To resolve, verify credentials, check Block ID inputs, and confirm API permissions.