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 to retrieve groups of entities (e.g., customers or contacts) based on various filtering criteria. The "GET groups" operation fetches a paginated list of groups, optionally filtered by text search, property IDs, date ranges, and expanded with additional related data.
Common scenarios include:
- Retrieving customer groups matching specific search terms or associated with certain properties.
- Paginating through large sets of groups for reporting or synchronization purposes.
- Including related blocks or actions data to enrich group information in one request.
Practical example:
- A hotel management workflow that pulls all guest groups created within a date range, filtered by company name, and includes their associated booking blocks for further processing.
Properties
| Name | Meaning |
|---|---|
| Text Search | Search text to filter groups by name, lastname, firstname, email, or company name |
| Property IDs | Filter groups by one or more property IDs |
| From | Start date/time to filter groups created or modified after this timestamp |
| To | End date/time to filter groups created or modified before this timestamp |
| Page Number | Page number for pagination (minimum 1) |
| Page Size | Number of items per page (minimum 1) |
| Expand | Additional data to include in the response; options: "Blocks" (related booking blocks), "Actions" (related actions) |
Output
The node outputs an array of JSON objects representing groups retrieved from the Apaleo API. Each group object contains standard group fields such as identifiers, names, contact details, and any filters applied.
If the "Expand" property is used, the output group objects will also include nested arrays for:
- Blocks: Related booking blocks associated with the group.
- Actions: Related actions linked to the group.
No binary data is output by this node.
Dependencies
- Requires an API authentication token credential for Apaleo API access.
- The node uses the base URL
https://api.apaleo.comand expects JSON responses. - Proper API permissions are needed to read group data and related resources.
Troubleshooting
- Authentication errors: Ensure the API token credential is valid and has not expired.
- Empty results: Verify that the filter parameters (text search, property IDs, date range) match existing groups.
- Pagination issues: If no results appear on higher page numbers, check the total number of groups and adjust page size accordingly.
- Invalid expand options: Use only the provided expand values ("blocks", "actions") to avoid API errors.
- API rate limits: Large requests or frequent calls may hit rate limits; implement retries or reduce request frequency.