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 retrieve the count of booking blocks filtered by various criteria. It is useful in scenarios where you need to quickly obtain the number of blocks that match specific filters such as property IDs, date ranges, or block status without retrieving full block details.
Practical examples include:
- Getting the total number of tentative blocks for a set of properties within a given date range.
- Counting definite blocks created between two dates to analyze booking trends.
- Filtering blocks by status to monitor cancellations.
Properties
| Name | Meaning |
|---|---|
| Property IDs | Comma-separated list of property IDs to filter the blocks by. |
| From Date | Start date to filter blocks from (inclusive). |
| To Date | End date to filter blocks until (inclusive). |
| Status | Filter blocks by their status. Options: Tentative, Definite, Canceled. |
Output
The node outputs a JSON object containing the count of blocks matching the specified filters. The exact structure typically includes a numeric field representing the count.
Example output JSON:
{
"count": 123
}
No binary data output is expected from this operation.
Dependencies
- Requires an API key credential for authenticating with the Apaleo API.
- The node uses the Apaleo API base URL
https://api.apaleo.com. - Proper configuration of the API authentication token is necessary in n8n credentials.
Troubleshooting
Common issues:
- Invalid or expired API token will cause authentication errors.
- Incorrectly formatted property IDs or date filters may result in empty results or API errors.
- Network connectivity problems can prevent successful API calls.
Error messages and resolutions:
- "Unauthorized" — Check that the API key credential is valid and has not expired.
- "Bad Request" — Verify that the input parameters (property IDs, dates, status) are correctly formatted.
- Timeouts or network errors — Ensure stable internet connection and that the Apaleo API endpoint is reachable.