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, specifically to check the existence of a block resource using the HTTP HEAD method. The "HEAD block exists" operation allows users to verify whether a block with a given ID exists in the Apaleo system without retrieving the full block details. This is useful for conditional workflows where subsequent actions depend on the presence or absence of a specific block.
Practical examples include:
- Validating if a block exists before attempting to update or delete it.
- Checking block availability as part of booking or reservation automation.
- Integrating with external systems that require confirmation of block existence before proceeding.
Properties
| Name | Meaning |
|---|---|
| Block ID | ID of the block to check for existence |
Output
The node outputs JSON data representing the result of the HEAD request to the Apaleo API for the specified block. Since this is a HEAD operation, the response typically contains metadata headers but no body content. The output JSON will primarily indicate success or failure of the existence check.
If the block exists, the node proceeds without error; if not, an error or empty response may be returned depending on the API behavior and node configuration.
No binary data output is expected from this operation.
Dependencies
- Requires an active connection to the Apaleo API via an API key credential (an API authentication token).
- The node uses the base URL
https://api.apaleo.com. - Proper permissions on the Apaleo account to perform block queries are necessary.
Troubleshooting
Common issues:
- Invalid or missing Block ID: Ensure the Block ID property is correctly set and corresponds to an existing block.
- Authentication errors: Verify that the API key credential is valid and has not expired.
- Network connectivity problems: Confirm that the n8n instance can reach the Apaleo API endpoint.
Common error messages:
- "Unauthorized" or "Authentication failed": Check API credentials and permissions.
- "Block not found" or 404 status: The specified Block ID does not exist; verify the ID.
- Timeouts or network errors: Check internet connection and Apaleo service status.
Links and References
- Apaleo API Documentation
- Apaleo Blocks API (for detailed block operations)