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, a platform for property management and booking services. Specifically, for the Block resource with the DELETE block operation, it allows users to delete a specific block by its ID. Blocks in Apaleo typically represent reserved or blocked time slots or inventory units that are temporarily held and not available for booking.
Common scenarios where this node is beneficial include:
- Releasing previously blocked inventory when plans change.
- Managing availability dynamically by removing blocks that are no longer needed.
- Automating cleanup of expired or unused blocks in a property management workflow.
For example, a hotel property manager could use this node to programmatically delete a block of rooms that was reserved for maintenance, making those rooms available again for booking.
Properties
| Name | Meaning |
|---|---|
| Block ID | ID of the block to be deleted. |
The Block ID is a required string input specifying which block should be deleted.
Output
The node outputs an array of JSON objects corresponding to each input item processed. For the DELETE block operation, the output JSON typically contains confirmation of the deletion or relevant metadata returned by the Apaleo API after successfully deleting the block.
No binary data output is expected from this operation.
Dependencies
- Requires an active connection to the Apaleo API.
- Needs an API authentication token (access token) configured in the node credentials to authorize requests.
- The base URL for API requests is
https://api.apaleo.com. - Proper permissions on the API key to perform block deletions are necessary.
Troubleshooting
Common issues:
- Invalid or missing Block ID will cause the API to reject the request.
- Insufficient permissions on the API token may result in authorization errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
"Block not found": The specified Block ID does not exist; verify the ID."Unauthorized"or"Forbidden": Check API credentials and permissions."Invalid input": Ensure the Block ID is correctly formatted and provided.
To resolve errors, confirm the Block ID is correct, ensure the API token has the right scopes, and check network access.
Links and References
- Apaleo API Documentation
- Apaleo Blocks API (for detailed info on block operations)